v5.96pre1 - September 11 2018

[Edgemeal]

v5.96pre1 - September 11 2018
+ API: [Take|Track]FX_SetParamNormalized() always sets touch state, even if value did not change
+ API: fix [Take|Track]FX_EndParamEdit() when called immediately following parameter set
+ Actions: add meta-action to toggle following action armed (rather than always arm)
+ Automation items: improve selection tracking in undo state
+ MIDI: fix glitches when editing the left edges of looped MIDI items
+ MIDI: fix negative start offset peak drawing issue around tempo changes
+ MIDI: fix peak drawing bug with non-1.0 takerate, looping, tempo changes
+ Notation: set armed cursor when using armed toolbar action
+ OSC: fix FX parameter change notifications for last track in bank
+ OSC: send FX parameter state for new plug-ins/loaded project
+ OSC: send an integer value of -1 to fx/@/param in order to end touch state
+ OSC: setting FX parameters always sets touch state, even if value did not change
+ Video: allowing bypassing DirectShow video output on Windows

Full changelog - Latest pre-releases

Other additions...
+ API: add get_config_var_string() for ReaScript
+ ARA: ask plugins to respect tempo when stretching only if the project/track/item timebase is set to beats/position/length
+ ARA: don't commit suicide when user preference enabled to set media items offline when application is not active
+ ARA: fix importing notes and tempo at once
+ ARA: fix model updates from plugin
+ ARA: fix rendering short fades with large buffer sizes
+ ARA: if one instance of an ARA FX UI is already open, focus that UI when inserting a new instance of the same type of FX
+ ARA: load copied tracks even if the ARA plugin context is no longer available [p=2022675]
+ ARA: mirror edits in looped media
+ ARA: support for ARA2-compatible plugins (note: there are no publicly available ARA2-compatible plugins)
+ ASIO: permit buffer sizes that are not a power of 2 if the device does not very specifically request otherwise [t=200746]
+ Elastique: improve timing of timestretch ramps [t=204269]
+ Fade editor: fixed an obscure possible bug
+ MIDI editor: 14-bit registered parameter/non-registered parameter CC editing
+ Misc: fixed a few minor memory leaks
+ Rubberband: improve timing of timestretch ramps [t=204269]
+ Stretch markers: add new "transient-optimized" and "no pre-echo reduction" stretch marker modes
+ Stretch markers: add project setting for stretch marker mode
+ Tempo map: fix importing initial time signature from MIDI tempo map
+ Track wiring diagram view
+ VST: inform plugins of project loop selection regardless of playback state
+ VST3: always apply latent VST3 parameter changes before saving state
+ VST3: do not deactivate plugin before changing IO buffer information
+ VST3: flush buffers on stop without resetting other plugin state
+ WALTER: support complex rules for mcp.size and mcp.master.size

[ivansc]

They are on fire, apparently!

[mccrabney]

+ Stretch markers: add project setting for stretch marker mode

nice.

i often wish there were quicker ways to apply stretch marker param presets to different tracks. this will let us set more a more appropriate baseline.

[_Stevie_]

@Justin since OSC got some love with this pre:
could we have a mute send command for OSC that gives feedback about the mute send status, similar to the insert fx bypass?

[Arthur]

Also it would be useful to have such a function:
Add stretch markers to items at time selection on selected tracks (at grid divisions).

[X-Raym]

@Arthur
This sounds more like a request for the ReaScript forum.


I personally already did Script: X-Raym_Add stretch markers to selected items at grid divisions.eel you could use in a custom action.

[FnA]

Originally Posted by Edgemeal

+ MIDI: fix glitches when editing the left edges of looped MIDI items
+ MIDI: fix negative start offset peak drawing issue around tempo changes
+ MIDI: fix peak drawing bug with non-1.0 takerate, looping, tempo changes

Thanks for working on this area!

A bug.
Seems dependent on where the source start is.

If the tempo changes in the following gif were lower in value, the stuff will move left, rather than right:

[FnA]

Something I noticed during testing all this. It may not be new. It is NOT new between 5.95(RCs) and 5.96pre1.

MIDI note off snapped to same grid as left trim of item is visible, selectable, and editable. I cut the notes at 0:04.



I actually managed before making the gif to draw a small note before the left trim/ending on it, but this seems very hard to reproduce.

[Justin]

Originally Posted by FnA

Thanks for working on this area!

A bug.
Seems dependent on where the source start is.

Thanks, fixing

[FnA]

Thank you, Justin.

Weird split and time selection cut of looped item:



Split doesn't have to be on tempo change point exactly, for similar things to happen.

[Justin]

Originally Posted by FnA

Thank you, Justin.

Weird split and time selection cut of looped item:



Split doesn't have to be on tempo change point exactly, for similar things to happen.

Yep, got that one too (it was related to the previous). I don't quite follow the one you mentioned as "MIDI note off snapped to same grid as left trim of item is visible, selectable, and editable. I cut the notes at 0:04."

[FnA]

I don't know if it is viewed as proper...

The second orange item is a copy of time selection area of first orange item on track. Done with mouse drag copy. Everything was made with snap to grid turned on.

In the beginning of gif, I circle the note off with the mouse. Then I marquee select all visible notes in item and that note that ends at the left trim gets included too, while others concealed by the trimmed edge do not. I personally think it should not get selected. And probably not be visible even. It stays the same apparent size at max zoom, but it's hard to tell how much of note is exposed (none, really, except note off) when at normal zoom level until you zoom in, but you can see a little line there.

The cut of notes was just to emphasize that that note would be affected too. Maybe I should have just left them all selected without cutting them.

This is not as big of an issue as the other things I suppose.

[Justin]

Originally Posted by FnA

I don't know if it is viewed as proper...

The second orange item is a copy of time selection area of first orange item on track. Done with mouse drag copy. Everything was made with snap to grid turned on.

In the beginning of gif, I circle the note off with the mouse. Then I marquee select all visible notes in item and that note that ends at the left trim gets included too, while others concealed by the trimmed edge do not. I personally think it should not get selected. And probably not be visible even. It stays the same apparent size at max zoom, but it's hard to tell how much of note is exposed (none, really, except note off) when at normal zoom level until you zoom in, but you can see a little line there.

The cut of notes was just to emphasize that that note would be affected too. Maybe I should have just left them all selected without cutting them.

This is not as big of an issue as the other things I suppose.

Got it, thanks.

[FnA]

Now looking at it on iPhone. Clarity is much higher than on my computer monitor. (what kind of monitor shows things so sharply?) I see:

The note off line is actually drawn to the left of the grid line.
(Edit. My point being not that it’s on the left, but that it’s drawn at all)

Upbeat notes are drawn longer than those that start on quarter note grid lines. At least at this zoom level.

[Robert Randolph]

Originally Posted by mccrabney

nice.

This was in release builds for at least one version already, and it was removed.

[Edgemeal]

Originally Posted by Robert Randolph

This was in release builds for at least one version already, and it was removed.

I don't think so, AFAIK all those other additions were only available in pre-releases, and were removed from RCs and final releases.

BTW, that feature was originally added in v5.79pre3 - March 29 2018.