Nostr

yeah we need both stems for a single note & a tree view (tag ability) to reference where samples came from

You would upload the bounced two channel for demos which would be showcased on top,

But also have the acapella which is what one actually contributed

Or let’s say you upload a 8 bar loop that consists of drums, lead, and bass, you would upload a two channel bounce of the whole thing showcased on top, but also have the ability to upload the parts separate

I could also use this to upload different speeds or keys of a single sample (if I didn’t want it time stretched) instead of spamming the timeline with the same idea 8-12 different times

Reply to this note

Please Login to reply.

Discussion

#[6] what do you mean by a two channel bounce?

so like, you have a mono accapella channel in ableton and a stereo beat in ableton… you export that into a stereo or two channel bounce.

Take a drum loop for example #[5] . I can use it as a stereo track and just loop it. Or, I could get snare, kick, hh, all separately mute and chop as I wish, the stems.

#[6] makes a valid point with tempos and keys. Producers are usually looking for inspiration, here you deliver inspiration they can interact with while keeping track of everyone’s contribution for the split.

I just love it, they will love it.

Imagine, piano player drops a lil loop.

Producer likes it but key is not quite right for vocalist in mind, wait, right key is already there.

Producer starts shaping, search database finds drums loop, gets stems, starts chopping.

Producers contacts piano player and says « I need a little bridge here, listen to what I got so far »

Piano player sends 3 versions, producers validates one.

Producer adds base. Thinks, meh, not soulful enough, me want live base. Broadcast call for base player.

Base player replies, sends 3 versions, producer replies with note, base player sends 3 more. Producer validates.

And so on…

Producer is happy. Producer presses magic button « pull for mix » all stems and xml are made available to download.

Producer send to mixing engineer, mix, back and forth, master.

Producer can press magic « pull for release » button… what comes after this depends on what standards could be built with NIPs but with zap split and the possibility to attach a zap tag to media the only question remaining is what % to who…

If you want to get fancy, I saw someone testing OGG files

which does have the ability to package multitracks into one file, but not many daws support creating these, but might get fancy and package them up for storage that way…

But realistically just have a dominate audio file and a way to upload a folder of other files attached to the same note

As far as the tree of referencing is concerned… I think you just have a field to mention the notes you found the samples you used, like a quote note.

Starting in on the concept here https://github.com/stemstr/Design/issues/13#issuecomment-1518455112

nothenry 2y ago

Live look at stemstr engineering team

😂 #[5] breathe!!!!! 💜 💜 💜 💜

nothenry 2y ago

🤣

Rijndael 2y ago

🫂

Did I do something wrong? The pitch was the GitHub of a track. Might as well be ambitious… no?

Do I need to feel guilty here?

nothenry 2y ago

No lol we love a challenge 💪

💪💪💪🫂

No!!! You’re vibing with it, excited and that’s awesome! I’m rocking with you here! #[4] has a lot of responsibility leading the client engineering team (and managing other open source contributors), so he’s got his plate full!

We’re all still figuring out what this thing is and how it can reshape music making and collaboration, so there’s lots of green-field for us to concept in. We’re a really small team rn, who all have days jobs, so this will take time to realize, but hang in there and keep the ideas coming!

It’s a referencing clusterfuck for sure, but I am convinced it can be done. It’s about linking notes together, signing uploads, and validating key steps, encouraging users to do it through stemstr for easy or use and creative ambiance allows to keep track of the whole human chain, packaging a Nostr release straight within stemstr, with built in zap split.

Can be done in 3 years? While releasing functions slowly?

that’s all possible, but you still have to get people to upload individual isolated tracks for that to be of any use… else the only thing isolated you would get is the root of the tree.

https://github.com/stemstr/Design/issues/13#issuecomment-1518457962

See my comment here

See my reply