Very nice indeed. Is this code from before the name change and all the value tree stuff went in? Or perhaps I’m thinking of another DAW?
Nope, it’s the most up to date version of the engine which we are currently developing Waveform 10 on.
A few years ago we changed the name of the DAW from “Tracktion” to “Waveform” in part to disambiguate from the company and to allow us to do things like this.
You can think of it as “Waveform, built on the Tracktion Engine” if that helps?
Wow OK, there’s so much work gone into this. It will be interesting to understand the value tree usage a bit better.
Thank-you very much!
Yep, it’s been a 15 year project so far
Can I ask, does it use Juce’s rendering engine?
What do you mean by “rendering engine”? GUI/audio/file etc.
What does it use for lines/polygons/boxes/waveforms/text etc
The Engine doesn’t really have any UI, it’s a data model and audio engine. You need to build your own UIs on top of it.
Obviously our DAW uses JUCE for the UI and the examples in the Engine use JUCE but there’s no reason you couldn’t use another UI toolkit.
I understand. Thanks again.
@dave96 Thanks for publishing this incredible piece of work. Aside from being a solid audio engine, I think it’s super-valuable as a learning resource.
One question: the license pricing… I’m assuming that’s $35 per developer per month (JUCE style pricing)? Not per user as stated, which could potentially work out insanely expensive!
Thanks! Yes, we hope it serves as some good examples for people.
Yes, that’s correct, it’s per “developer seat”. I’ll get that updated for clarification.
This is great! You guys are awesome for doing this, there are a lot of devs that are talented but just don’t have time to write a full audio engine and/skill level.
But there are a lot of devs with dreams and this is fantastic! Going to try some android stuff.
Glad it’s getting a good response!
Dave deserves the vast majority of the credit for this, but I’ve also been pretty deeply involved in the slash-and-burn job of cleaning up and refactoring the code to the point where it’s safe to reveal to the public.
If you like it, please share the news around on your “socials”, and help get us some github stars!
Did you guys have plans of integrating some type of extension system in the DAW itself that could load “modules” that were apps as well but maybe not VSTs?
This would be great, since it would be more of a compromise for some that don’t want to release VST but do mobile/desktop.
This is a brilliant initiative. Thanks Dave and Jules.
Trying to build the step sequencer sample I get an error in VS2017
Severity Code Description Project File Line Suppression State Error C1128 number of sections exceeded object file format limit: compile with /bigobj StepSequencerDemo_App X:\dev\audio\tracktion_engine\examples\projects\StepSequencerDemo\JuceLibraryCode\include_tracktion_engine_model.cpp 1
Are you compiling a 64-bit app?
Yes, it’s the only build target, I am on Windows 10 Pro/64.
Have you got something specific in mind?
I do have a plan to make the Modifiers modular, and you can always provide your own bits of an app via custom ValueTree properties (we do this in Waveform for things that are specific to our DAW).
But I’m wondering what other “modules” you’d need. That would essentially mean creating an API for the “module” and that means it would need a spec/use case
How much RAM have you got?