I mean, I don't see the point of having multiple people sitting at the mixing console working on the sound. That's something I wouldn't want, like too many cooks in the kitchen. One person should do the mix and then release it. There's only one DJ per party, after all.
Discussion
Any large scale project requires multiple engineers. nostr:npub1updmknky86nsph84rstlh0yymqpeg9l9f62qgxwvd6a75f3pvzxqxv83nv is trying to build tools for studio (enterprise) level content where multiple projects are running simultaneously. We'd rather have this all sync on nostr rather than every creator needing to run their own DAW and manually load in project files between edits.
If I have 4 engineers working 12 different projects in rotating shifts you'd normally want everyone in the same studio on the same equipment. With a distributed team, you have to make sure everyone is on the same DAW for compatibility and use cloud dropboxes for file storage/sharing. What I'd like to see is using nostr relays to replace the cloud storage and then a DAW client for project based editing and colab.
Creatives will be wanting this for visual content too but we are focusing on cracking audio production first before scaling up to that.
nostr:npub12yqn2f5z3wkx5x8q0w22pd8nc0fn0jtqf76u677fk06yftaujmsscfkjum would love to hear your thoughts on this. It's looking more and more like we will need to build a client for this.
I agree with Alp on this. Better investment of our collective but limited time and resources would be to create a halal and family-safe general purpose FOSS nostr app and perhaps caching service, to make it easier for normal people to join.
We have a start with that in nostr:npub1h8lhed2da096g2wcsh2crmyvenune046rqkejc8f8pcaag8qj25qqadp5p for the relay service. Once we hit a sustainable subscriber count there building out a client would be fine. Open to entertaining any project proposals there.
I don't know, something just feels off about this idea. Besides the super limited potential user base. I get your example with the engineers, but sound editors? Are your projects really as big as Hollywood movies that you actually need multiple sound engineers? How long is one of these podcasts anyway? 1-2 hours? That's a one-person job for a sound editor.
So the DAW would literally run on Nostr?
That would be the dream 😅
Doesn't need to be specked out, just something simple like Audacity would do. I think if you had a git repo for your audio files a DAW client could pull from there and due edits. Session would be saved as a new branch. Teams could work on an auth relay for colab. Clients should also be able to handle distribution (rss).
Can be useful when working collaboratively. For example I’m currently sharing an Ableton project (another music app) with a video tech we’re tasked with designing a live show together.
There have been other attempts at this type of thing… although we’re just sending a project folder back and forth.
Q: If the system was Nostr native, who hosts the media? Or would each user still maintain a copy of the media folder?
My guess is the relay server would probably host during production but blossom provides some flexibility. Self hosting is probably preferable for distribution but if it is a group project then a multi-sig npub would be nice (I don't think we have those yet either).
Good example! Video is almost always collab and most audio project are too from my experience.