v6.77rc1 - March 1 2023

[Edgemeal]

v6.77rc1 - March 1 2023

+ MIDI editor: improve behavior of toggle all MIDI editor action
+ ReaScript: correct region navigation APIs when used on background projects [t=276610]
+ VST3: make MIDI learn/PC support opt-in for existing project compatibility (right click on I/O button)

Full Changelog - Pre-Releases - Feature Requests - Generated by WhatsNew2

[Wanekk]

mouse wheel in "reaper.get_action_context()"
began to work rough, for example, when slowly scrolling the wheel, I get 0,
or a little faster and get a lot

in version 6.75 everything worked correctly

[Justin]

Originally Posted by Wanekk

mouse wheel in "reaper.get_action_context()"
began to work rough, for example, when slowly scrolling the wheel, I get 0,
or a little faster and get a lot

in version 6.75 everything worked correctly

thanks, fixing!

Worth noting that going forward this number will be a floating point number that may be less than 1.0...

[mccrabney]

this is a longshot, but is this mouse speed stuff going to fix the issue where actions/scripts triggered by rapidly spun mousewheel events sometimes "pile up" and continue triggering even after the wheel has stopped spinning?

[Edgemeal]

With "Maximum Vertical Zoom " set to 220% or higher, the action: "View: Toggle track zoom to maximum height" (ID: 40113) can't be toggled off.

Win10, 1080p display @ default scaling, etc

[Justin]

Originally Posted by Edgemeal

With "Maximum Vertical Zoom " set to 220% or higher, the action: "View: Toggle track zoom to maximum height" (ID: 40113) can't be toggled off.

Win10, 1080p display @ default scaling, etc

thx, fixing!

[Wanekk]

Originally Posted by mccrabney

this is a longshot, but is this mouse speed stuff going to fix the issue where actions/scripts triggered by rapidly spun mousewheel events sometimes "pile up" and continue triggering even after the wheel has stopped spinning?

i use my 2 script which move elements left/right up/down
never seen a script keep running after the wheel stops

[mccrabney]

this can be experienced using a MIDI endless encoder or a free-spinning mousewheel using the action "Transport: Scrub/jog fine control (MIDI CC relative only)"

feed it enough messages fast enough and they start accumulating faster than REAPER can react, to the point that once you stop spinning the device, REAPER will spend a second catching up to the present. not really something that a licecap could show, but i've explained the gist of it. i've seen this in several scripts, as well, but it might be unavoidable as the scripts take time to run.

anyway, if it's not related to the work at hand, we can discuss it another time

[Justin]

Originally Posted by mccrabney

this can be experienced using a MIDI endless encoder or a free-spinning mousewheel using the action "Transport: Scrub/jog fine control (MIDI CC relative only)"

feed it enough messages fast enough and they start accumulating faster than REAPER can react, to the point that once you stop spinning the device, REAPER will spend a second catching up to the present. not really something that a licecap could show, but i've explained the gist of it. i've seen this in several scripts, as well, but it might be unavoidable as the scripts take time to run.

anyway, if it's not related to the work at hand, we can discuss it another time

The MIDI side might be easier since we get a batch of MIDI message and we could coalesce the relative motion into larger events. Mousewheel gets queued by the OS, so we can't really do that. I guess we could buffer them and then every 10ms or so do a batch. Will experiment with that and see how much it ruins responsiveness...

side note -- that OS queueing is probably why some people see it and others don't -- it's driver dependent, I think most mouses I use do the coalescing themselves, because I can never reproduce that issue.

other side note -- on some macOS versions with some input devices I've reproduced it (that previous sentence was a lie apparently), which is why there's that preferences/general/advanced/throttle mouse events option (it's coalescing the events when that is enabled)

[mccrabney]

thanks for giving me some insight into this.

in windows, i've been able to reproduce this with every mouse/rotary controller i've ever used in REAPER since 2007, to the point where i don't use (for example) scrub and a few similar actions. for other actions (mostly my own mousewheel scripts), i either just slow myself down or the issue doesn't present because it only requires a few ticks of the physical device to achieve the desired task.

note that (at least in my experience) the scrub action above can be used to demonstrate the issue pretty reliably, but something like "Edit: Move events left/right (mousewheel/MIDI relative only)" never seems to get bogged down, no matter how exaggerated my scrolling gets. likewise with vertical/horizontal zooming/scrolling with the mousewheel - the action/movement always seems to correspond 1:1 with the movement of the physical object - great!

whereas my script "nudge note, notes under mousewheel if no RE present" can pretty easily get behind the input from the encoder -- in this case, i assume it's due to my as-yet limited ability to optimize ReaScript.

[Buy One]

Originally Posted by Justin

thx, fixing!

Could then an action to always toggle track height to exactly 100% be added to fill in for the behavior which is now gone as far as i understand?