5 ms·
I am working with an heavily collab oriented-project, Cosmoose, which released a remix album one month ago (also active on Indie Music Feedback community). The
by woolion 5y ago
I am working with an heavily collab oriented-project, Cosmoose, which released a remix album one month ago (also active on Indie Music Feedback community).
The problem we have with this is: sharing the stems (one song will usually be some gigabytes of storage), organizing, making splits.
It's a lot of administrative overhead that can suck out the pleasure from music-making itself.
And what people burn out on is that a lot of these collabs go poorly because of artistic differences, or one people being not serious (for good or bad reasons).
So if the collab is off-site, that eliminates the completion rate you have on a platform like skeb. IMF solves this by being more a community and so you get to know people more before working with them.
So I'm not sure it is solving really anything, and the approach does not seem sustainable (one email per new track per user? how long before everything goes to spam). But I'd love to be convinced otherwise :-)
- bartproost 5y agoThank you for the feedback! This is definitely something I have yet to overcome. A few users asked for features that will allow Brew to head in this direction. I'm exploring solutions, and might even introduce a Pioneer.app like program, but for artists. On the scalability: I'm a big fan of not overcomplicating things early on. However, I'm planning to build a feature that lets you select a daily/weekly preference so you simply get a summary of what was added that day/week. I'm also planning on auto-tagging genres based on the track previews using essentia.js, so I don't have to spam metal heads with EDM daily. Lots of room for improvement, but waiting for it to become a problem first.
- 112233 5y agoOn a long tangent: now that Apple is pushing Atmos, is it possible to somehow package quality stems in an Atmos track that sounds mastered?