|
|
|
|
|
|
by thr0wawayf00
1429 days ago
|
|
|
It's also such an obvious question though, isn't it? You think that the developer pouring so much of their free time into a browser-based DAW wouldn't have considered the idea of supporting plug-ins at all? People far too often approach projects like this with "this app is only useful for me if it does x..." and I think that framing is poor when someone is just exercising their passion on a project. I'd personally respond with "great, go build your own that supports your plug-ins. Have fun." |
|
|
Is it? I’m genuinely asking as someone who works in audio production. Plenty of people create tools for us in the podcast space, AI transcriptions for spoken word (premiere has a good one), new ways to automate typically manual processes for mastering, you name it. The thing is it is not a given that the person creating a solution has an audio production background and properly weighs the needs.
Plenty of engineers do work for or work directly for hospitals. Are you going to tell me that they might not overlook something a nurse or doctor might need? Because I assure you it happens in every industry when people come up with new tools and solutions, often because many actually don’t come from a strong background in the industry they’re making tools for. I value an outside perspective, don’t get me wrong. But it has its issues too.
It’s not uncommon and it’s fair for us technicians, the people these solutions are designed for, to ask questions.