v5.79pre9 - April 7 2018 + Localization: improve routing window organization [p=1974922] + MIDI: prevent event sorting from sometimes destroying notes [t=205082] + Notation: fix autoscroll issue when opening with out of range zoom levels [p=1976104] # Actions: fix "view FX chain for current track" w/ master track [t=205352] # Fix track selection control surface notifications [p=1975835] # WALTER: clearing anything in tcp.* now disables all legacy sizing logic
Actually that MIDI line was the previous fix (but we did some internal reorganization causing the extra line).. but the notation commit is technically MIDI too.
+ Notation:[/B] fix autoscroll issue when opening with out of range zoom levels [p=1976104]
Hi!
Regarding this [p=1976104]
I downloaded this latest prerelease build and opened that same project.
Here's the results:
If I select the items and open the Notation Editor with the edit cursor at bar 65, the editor opens at bars 36 'till 47, which is still weird and I guess still wrong...
Good thing is that now when pressing play focus gets taken back to the correct position and scrolling behaves as expected, so that's an improvement, thanks!
If I select the items and open the Notation Editor with the edit cursor at bar 65, the editor opens at bars 36 'till 47, which is still weird and I guess still wrong...
It's at least consistent with the piano roll, I think? Maybe it would be nice to run the action "go to edit cursor" implicitly on open (by default that's mapped to the " key)?
It's at least consistent with the piano roll, I think? Maybe it would be nice to run the action "go to edit cursor" implicitly on open (by default that's mapped to the " key)?
Hi Justin,
No, not really...I made a video, here's what happens:
It's weird because because the piano roll opens correctly (with a large zoom on many bars but at least it shows the exact bar 65)...
if I switch to Notation it wrongly goes to bar 36 till 47 with a different/smaller zoom,
THEN if I switch back to piano roll it stays consistent with the Notation but focusing in the wrong part, so from bars 36 till 47.
maybe i am bit too late!... regarding displaying midi CC in tracks
would be very nice too see the Midi CC messages being displayed while being recorded!
Thanks
edit: even better could be to display the last "cc" aka Hardware synth knob being "moved".
If size permits .. the last "N" CC's would be displayed
The batch file/item converter broke in 5.79pre1 when sample rate conversion is enabled and a plugin in the FX Chain has latency and PDC is enabled. It remain stuck at 100% until the offending FX is removed, bypassed or set offline. Sometimes the reported latency keeps increasing. Other times it toggles between the FX's latency and the block size. Tested with VST, VST3 and Audio Units. JS seems unaffected.
The batch file/item converter broke in 5.79pre1 when sample rate conversion is enabled and a plugin in the FX Chain has latency and PDC is enabled. It remain stuck at 100% until the offending FX is removed, bypassed or set offline. Sometimes the reported latency keeps increasing. Other times it toggles between the FX's latency and the block size. Tested with VST, VST3 and Audio Units. JS seems unaffected.