Hello!
Not much to say in the heat of the season: consider the update as a refreshment. Though please, if still running any pre-v0.5 installment, an upgrade is mandatory, immediately, better say now!
Hi again!
On the next day comes a fiery hot-fix: again, everyone is strongly advised to update ASAP! Especially if using any of the previous ill-fated v0.4.x series (or yesterday's v0.5.0, which should be promptly ditched to the trash bin :)).
Fixed segfault on initialization that was affecting Qt5 builds.
Completely refactored the internal PipeWire node registry logic, just to have unique node names, as seen fit to purpose to solve an old undefined behavior to positioning and Patchbay persistence of multiple nodes with the very same and exact name.
Fixed the main PipeWire registry thread-safety, into a two-level critical section, hopefully preventing the race-conditions that are the suspected cause to some rare crashes.
Fixed the snap-to-beat of new notes entry on the MIDI clip editor (aka. piano-roll) due on time signature changes.
Start JACK transport rolling only when metronome Count-in ends.
Fixed an allegedly old and incorrect 0dBfs notch position on MIDI track/buses audio meter sidekicks.
Send/return and Aux-send inserts now show the proper name and the target output bus name on the properties editor title respectively.
Fixed a zero-day blunder that was keeping the real-time process cycle from having the uniform block-size of 64 frames per period; (thus, probably ineffective since v0.9.30).
Multiple MIDI clip tools may now be applied simultaneously, in a single shot, in the following priority order: quantize, transpose, normalize, resize, rescale and timeshift.
Plugin inventory scan now slightly optimized to an allegedly lesser aggressive cache-invalidation algorithm.
Do not send/Preview notes on the MIDI clip editor (aka. piano-roll) when playback is currently rolling.
Send all pending MIDI Note-Off events when playback stops/shuts-off (and/or the Panic! button is hit).
Fixed the internal MIDI file player queue to the highest resolution possible (PPQN aka ticks-per-beat).
Prepping into the next development cycle (with Qt >= 6.5).
Recent comments
8 hours 45 min ago
1 day 2 hours ago
1 day 8 hours ago
2 days 2 hours ago
1 week 1 day ago
1 week 2 days ago
1 week 2 days ago
1 week 2 days ago
1 week 2 days ago
1 week 2 days ago