dave96
June 16, 2022, 10:24am
1
Tracktion Engine v2.0 is getting close to public testing now.
I’d like to move it on to the develop
branch as there’s a bunch of CI for coverage and benchmarking that only happens on that branch. I’ll move the current develop
branch to the master
branch for now whilst it’s being tested.
Is this ok for everyone? I wanted to give a heads up before just going ahead to avoid confusion and hear any major objections.
7 Likes
bwall
June 16, 2022, 6:49pm
2
That works for me.
Interested to see the Breaking Changes?
Have you seen this, @bwall ?
# Transitioning to Tracktion Engine 2.0
## New Module Division
Tracktion Engine has been split up in to three modules. The idea behind this is that developers can use the primitive base types (**core**) in the framework or the audio playback engine (**graph**) without having to use the engine model. Most applications will still use `tracktion::engine` but if you’re making a lower level app the other modules may be of use to you. N.B. a Tracktion Engine license is required for use of **any** of these modules.
Although these are separate modules, they are contained within nested namespaces so you can access them all with the `tracktion::` specifier. This is the recommended method incase classes/functions move between modules.
### tracktion::core
Contains primitive types that do low level operations like define a time or beat position/duration and convert between them. This library aims to be header only so is simple to include. It is used extensively throughout the rest of the framework.
### tracktion::graph
Contains the low level audio processing library which powers playback inside tracktion::engine. This provides base classes for processing nodes and graph construction, then playing these back using multiple threads in a lock-free way.
### tracktion::engine
Contains the bulk of the framework and the higher level classes required to build an application quickly. This defines the Edit model and the various classes used to interact with the model.
This file has been truncated. show original
dave96
June 17, 2022, 12:33pm
4
2 Likes
bwall
June 17, 2022, 2:30pm
6
Thank you Dave!
I can see a lot of work ahead of me to transition to 2.0, but I can also see how it will be better in the long term.
Thank you for all your hard work!