This is deeply impressive, and of course the first thing I'm doing is sharing it with some mates. The technical completeness of this, the fact that you can do this sort of thing in the browser at all - that to me is mindblowing (I'm 52 and remember when marquee tags were a bit of a stretch...).
But... like other commenters - there it stops, and I'm just not quite sure why.
The audience is probably me. I'm an avid Ableton user - I pay a bloody fortune for it, I upgrade it every year, I am happy to support their development because it's an insanely - insanely - good piece of software that does everything I need it to do. I'm also now completely embedded in the clip view, so going back to a linear view just isn't a possibility for me.
More to the point though - this clearly isn't aimed at people who know nothing about what they're doing. It's very non-amateur and clearly very, very powerful. But at the same time it isn't aimed at me, either - as someone who does know what they're doing, I'm thinking "um, VSTs?" or "clip view?" or "live performance / latency issues?" or whatever.
So... who is the audience? Maybe there is a middle ground of people who don't have the means to fork out for a good desktop DAW. Maybe teenagers who are wanting to learn the principles without the spend. Maybe because it'd be very cool for collaborating? I just don't know.
Nonetheless, it's an insane demonstration of what can be done in a browser these days and for that I massively doff my cap - amazing work!
Can't agree more. Might be the most crazy thing I have ever seen done in the browser.
It actually demotivates me to work on music and motivates me to work on some web app ideas.
I am not sure who the audience is though either. Reaper works wonderfully on Linux.
The issue is any DAW or really any musical instrument is massive investment in time to learn to be good. The money isn't really the bottleneck. I can easily get a reasonably priced flute on ebay. The reason I don't play the flute is because the amount of time involved to learn to play it.
My question is why not just have a desktop daw implement rpc on their daemon to work collaboratively natively instead of being sandboxed in a browser? Or does this already exist?
I would be down for a browser ableton suite that had all the stock devices and didn't have vst support. I think over time people learn that you can do 90% of what you need to do with just stock devices (although max4live support would be amazing)
But... like other commenters - there it stops, and I'm just not quite sure why.
The audience is probably me. I'm an avid Ableton user - I pay a bloody fortune for it, I upgrade it every year, I am happy to support their development because it's an insanely - insanely - good piece of software that does everything I need it to do. I'm also now completely embedded in the clip view, so going back to a linear view just isn't a possibility for me.
More to the point though - this clearly isn't aimed at people who know nothing about what they're doing. It's very non-amateur and clearly very, very powerful. But at the same time it isn't aimed at me, either - as someone who does know what they're doing, I'm thinking "um, VSTs?" or "clip view?" or "live performance / latency issues?" or whatever.
So... who is the audience? Maybe there is a middle ground of people who don't have the means to fork out for a good desktop DAW. Maybe teenagers who are wanting to learn the principles without the spend. Maybe because it'd be very cool for collaborating? I just don't know.
Nonetheless, it's an insane demonstration of what can be done in a browser these days and for that I massively doff my cap - amazing work!