Why You Shouldn’t Write a DAW - David Rowland - ADC23

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Did you watch this talk of the genius lead developer of current Waveform?


While most other talks count about 400 views a month after the conference videos have been published, his reached already 45k views. Obviously, many users are watching it as well. He expresses himself quite understandable to explain the sophisticated challenges having to be faced under the hood of a DAW, headaches which we users do not see when clicking around in the app.

I am quite impressed.
David, Roland, and colleague, You truly earn my respect for your great work!
Last edited by talby on Sat Aug 17, 2024 11:42 pm, edited 1 time in total.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5

Post

He does have a motivation for the speech, and he clarifies during it, that the hard part is writing the engine ('so use ours!')
Which takes nothing away from the guy, he is a genius it seems, and I've heard Jules say as much in interviews. I still think Waveform, the front end, is only a part of their revenue, and therefore time, so I hope their business as a whole goes well and they can dedicate a little bit more time to tidying things up in between releases, like they did with 13.
Waveform still doesn't register in the general thinking when it comes to daws, and it's always so close to being brilliant (I'd say it's brilliant with annoying bits that are only found when the user is trying to make the most of what it offers in a creative way, which I don't think any of the devs/beta testers seem to be into.)

Post

As you mention Julian Storer, yes, also a genius in programming. For us users, taking advantage of their great productions, this comes with a potential downside as well. These highly talented people are always on risk to become bored by their own creations before the product of it is fully cleaned up from bugs, leaving for new challenges and we users feeling uneasy about the future of our beloved tool(s).
To my knowledge he was the original creator of Waveform, some two decades ago, that time Waveform still having been called Tracktion. Then he gave it away into the hands of Mackie and created the JUCE framework, also a success story. Then he rescued phasing-out Tracktion success from Mackie and organized a refresh for it, which David, Roland and colleagues are now establishing, pushing Tracktion Waveform up into the circle of the top contenders again. Meanwhile Jules is busy with a new creation, his Cmajor audio programming framework, which will not allow him no more to spend much time on Waveform, the Tracktion Engine and JUCE.
Well, maybe I should not worry to much about the future of our beloved tool(s). Jules, David, Roland and colleagues can be very proud of their ideas, developments and products, deserve to stay entertained in life by confronting fresh challenges, also by private life of course, and, although occasionally restrained, they never abandoned us users of their tools.
Crossing fingers for the future of all of us, for the developers and for us users!

[EDIT: Above I wrote my impression, which built up over time picking up information from the internet. I am happy to be able to link you to a recently published interview, which I today came across. In this interview David himself explains the true history of all this, and obviously I was wrong on some things! For instance, JUCE was created in parallel to the creation of Waveform with the purpose to facilitate the programming of Waveform. Also, there are some team members involved whom by now I didn't know about. Well, listen to it yourself: ]
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5

Post Reply

Return to “Tracktion”