Version 3.0 Alpha
Note ! This version is very unstable, only for the most adventurous testers. Plenty of basic things do crash. Use 2.5.2 if you have to make a show.
Old save files do not work so use it only for testing as things are still pretty rough !
Linux version will come in a few days.
New features
- Tempo and musical metrics support !
- With possibility to change time signature of course :)
- And magnetism !
- Each interval can optionally have its own signature which enables polyrythmy.
- Processes are being converted to support quantification based on their parent's metrics, e.g. LFO and arpeggiator.
- Triggers can also be quantized - once the trigger condition becomes true, the trigger will then wait until the next quantification date (e.g. start of next bar). This can be changed in the trigger inspector.
- Multiple time stretch modes are available, thanks to the Rubberband and libsamplerate library which allow both pitch-shift and time-stretch like behaviours.
- A Metronome process has been introduced (which requires the current user library for its provided metronome sounds).
- A better metronome sound would be welcome.
- Likewise, a Tempo curve process has been introduced. It is more precise than setting the speed of an interval
through the local tree - and child processes of its parent interval will be able to leverage its tempo (e.g. for audio plug-ins...). - Basic tempo detection through sound files filenames and ACID tags.
- With possibility to change time signature of course :)
-
Video and shader support !
- See https://twitter.com/jcelerie/status/1211354889873510400 for a simple example.
- Thanks to the new Qt RHI (https://www.qt.io/blog/qt-quick-on-vulkan-metal-direct3d) a shader graph has been introduced.
- Shaders and video nodes are like all other processes in the UI.
- Shaders are written in the Vulkan GLSL dialect - execution is then translated to Vulkan, OpenGL, Metal, D3D11 to be extremely efficient. Please help us write a neat shader library :)
- A video node which does as much as possible on the GPU has been implemented - for now only YUV420 and RGB formats (HAP and most H.264) are supported - more to come.
- It is possible to apply video filters, etc...
- Multi-viewports are possible. Viewports (windows) are devices (Gfx for now, Spout, Syphon & others are to come). To send a texture to a window just add a Gfx device and use its address in the process's output (e.g.
gfx:/
).
-
Every interval can now loop directly from the inspector.
- This is not for interactive loops, only for looping e.g. a sound file like you would in other daws.
But it works for all the processes of the interval. - Likewise, a start offset and a loop duration can be defined.
- This is not for interactive loops, only for looping e.g. a sound file like you would in other daws.
-
Nodal view for intervals.
- Every interval can now also be edited in a patch-like manner, with all the processes
visible in a 2D grid instead of the vertical layout. - Switching between those two views can be done at any time with the button at the bottom left of the score.
- Every interval can now also be edited in a patch-like manner, with all the processes
-
Ports can now have child ports.
- In particular every audio output now can have a gain and pan control.
- In the future processes such as Automation will have their min/max moved to these controls.
-
Intervals can now be mixing busses.
- Actually they were since 2.0 but there was no UI to change it.
- To use that feature, mark an interval as a bus in its inspector.
- The Audio panel then allows to change its volume / pan.
- Things with more than 2 channels will be available once we figure a proper UI for it - designers welcome as the code already supports it !
-
New simple pattern sequencer process, useful for quick rhythmic tests. Very WIP for now.
-
New simple signal display process, useful for debugging.
-
New icons for LFO signal kinds (sin / square / etc...) -- thanks @aklevy !
-
New fiery splash screen -- also thanks @aklevy !
-
MIDI processes can now write to a specific channel.
-
Velocity of MIDI notes can now be changed with shift-click.
-
JS processes can now modify the score through the same API than the console (very WIP).
-
A new node has been added to the local tree to allow sending JS commands to modify the score from the outside. Yes this is extremely dangerous, we love it :-).
-
Audio files in the inspector can now be listened to, but is still very buggy :-)
A few more things got in since the last release, but were forgotten :-)
## Bug fixes
-
Allow to change "propagate" on the fly.
-
LFO output is now between [0; 1] by default instead of [-1; 1].
-
It was not possible to remove the trigger of a loop with the keyboard.
-
Tons of many small bug fixes, but a ton has also been introduced in the new features ;p