v6.37 - October 12 2021

[musicbynumbers]

v6.37 - October 12 2021

• + Actions: duplicate selected items obeys item grouping, creates new groups when originals are grouped [t=257557]
• + Actions: fix quirks with 'Expand selected track height, minimize others' action and mouse mapping [t=257138]
• + Actions: update solo button after MIDI CC solo state action [t=247350]
• + Actions: fix some soft-takeover corner cases for midi CC actions
• + API: improve resolution and remove center-snap logic from CSurf_OnPanChange*() and CSurf_OnWidthChange*()
• + Audio Units: preserve input audio for instrument plugins (same behavior as VST and LV2 instrument plugins)
• + Audio Units: fix creating shortcuts to renamed plug-ins via FX browser
• + Audio Units: support IO menu in pin connector dialog
• + Automation items: fix possible hang on linux/i686 [t=257166]
• + Batch converter: add brickwall limiter option
• + Batch converter: prevent occasional incomplete normalization with very short files [p=2486792]
• + Envelopes: add advanced project preference (default enabled) to prevent bezier envelope segments from being affected by preceding/following non-bezier points
• + Envelopes: correct invalid envelope point shape data when loading project (protect against buggy scripts or extensions)
• + Envelopes: fix potential odd behavior when editing FX parameter envelopes with inverted range [t=257763]
• + FX: support delta solo (difference between dry and wet signal) for VST, LV2, AU, JSFX
• + FX: enable delta solo via alt+click or right-click on wet/dry knob, or I/O menu in pin connector dialog
• + FX: add action to toggle delta solo for last focused fx
• + FX: show FX shortcut actions in action list even when FX is not available
• + FX: fix "only when selected/focused/visible" preference when using controller soft takeover [t=253787]
• + FX browser: display error when FX shortcut creation fails
• + FX browser: improve behavior adding to folders when using search
• + FX browser: scan for new LV2 plug-ins when refreshing list via F5 [t=257658]
• + FX pin connector: change track channel count via dropdown, rather than +/- buttons
• + FX pin connector: support changing plug-in channel count, mulit-mono, multi-stereo configuration for ReaFX that support it
• + FX pin connector: support configuring requested VST3 bus size
• + JSFX: fix loudness meter peak value display for certain channel counts [p=2486807]
• + JSFX: improve Oscilloscope scrolling smoothness
• + JSFX: increase Oscilloscope maximum view length to 5s
• + JSFX: Loudness Meter integrated values (LUFS-I, LRA, RMS-I) only update when playing back
• + JSFX: support regular peak (in addition to true peak) metering in Loudness Meter
• + JSFX: update Flanger preset [t=4908]
• + Linux: allow mousewheel to scroll menus/combobox lists
• + Linux: improve appearance of menus and list/tree views [t=255743]
• + LV2: fix creating shortcuts to plug-ins via FX browser/script [t=258148]
• + LV2: improve support for localized plug-ins, use LANGUAGE environment variable to choose language for plug-in, parameter, and preset names [t=258123]
• + LV2: notify UIs when time:beatsPerMinute or core:freeWheeling parameter changes occur
• + LV2: support pin connector dialog I/O menu option to zero out unmapped channels
• + macOS: fix Big Sur save dialog behavior when exporting to project types other than .RPP [t=257839]
• + Media explorer: inform user if maximum number of user-customized metadata columns has been added [t=258053]
• + Media explorer: localize dialog to add user metadata column
• + Media explorer: remember original playback start position when stopping (not pausing) preview, restart playback from that position
• + Media explorer: when selecting new media, if both autoplay and show peaks for selected media are disabled, previous playback will continue
• + MIDI: reset CC/pitch on playback stop is now enabled by default
• + MIDI: fix processing sysex messages when the terminating byte is a standalone packet [t=257456]
• + MIDI editor: add custom note order/visiblity mode (ctrl+drag note key in named notes view)
• + MIDI editor: do not quantize behavior of "drawing or selecting a note sets new note length" preference [t=257819]
• + MIDI editor: import/export of note names includes custom-view ordering information if set
• + MIDI editor: obey option for Preferences/Keyboard/alt key to main menu on Windows
• + Pan: improve rounding behavior when adjusted via control surfaces/actions
• + Project bay: read source file attributes from cache if possible, to improve loading time for bays that contain many retained files
• + Razor edit: allow pressing copy modifier key after mousedown, but before initial mouse move [p=2478084]
• + Razor edits: fix envelope edits affecting automation items incorrectly [t=258064]
• + ReaComp: support up to 64 channels, optional multi-mono and multi-stereo modes
• + ReaEQ: support various channel metering options
• + ReaEQ: support up to 64 channels
• + ReaEQ: update display after resizing when not processing audio
• + ReaFIR: support up to 64 channels, optional multi-mono and multi-stereo modes
• + ReaFIR: support various channel metering options
• + ReaGate: support up to 64 channels, optional multi-mono and multi-stereo modes
• + ReaLimit: add new program-dependent brickwall limiter plugin
• + ReaLimit: support embedded UI
• + ReaLimit: support up to 64 channels, optional multi-mono and multi-stereo modes
• + ReaScript: add MIDIEditor_EnumTakes()
• + ReaScript: add TakeFX/TrackFX_GetParamIdent/GetParamFromIdent
• + ReaScript: ensure envelope point shape input is valid
• + ReaScript: for Lua, make final string parameter to various Get functions that return strings optional
• + ReaScript: MIDIEditor_GetTake and MIDIEditor_EnumTakes return nil if the MIDI editor is empty
• + ReaScript: Track/TakeFX_GetNamedConfigParm() can retrieve fx_name, fx_type, fx_ident
• + ReaSurround: update I/O size immediately when changing speaker configurations while bypassed
• + ReaVerb: add Channel Tool to allow combining multiple files by channel
• + ReaVerb: support up to 64 channel impulses
• + ReaVerb: load channel count configuration from presets
• + ReaVerb: reverse impulse modifier can apply to all channels or single channel
• + ReaXcomp: support up to 64 channels, optional multi-mono and multi-stereo modes
• + Recording: improve recording behavior with time selection autopunch and PDC [t=242924]
• + Render: add brickwall limiter option
• + Render: add support for renaming render presets
• + Render: display gain reduction in render peaks display when limiting
  

Generated by X-Raym's REAPER ChangeLog to BBCode

[musicbynumbers]

• + Render: fix peaks display with very short files
• + Render: report rendered file length, full file path in HTML render statistics
• + Theme: fix display of 200% layouts on retina displays
• + Track panels: improve behavior of FX parameter knobs for toggle parameters
• + Transport: fix issues with docked/undocked transport and screensets [t=258026]
• + Video: fix gfx_deltablit documentation [p=2479952]
• + VST: fix initializing pin connector when plugin I/O increases
• + VST: improve hard-reset behavior when used with plugins that only support soft-reset
• + VST: improve naming of unnamed programs
• + VST: improve program handling when loading state for plugins that support chunks (e.g. Maize Sample Player)
• + VST: improve support for VST2 plug-ins that do not support effGetProgramNameIndexed
• + VST: run preset loading synchronously with audio processing
• + VU meters: don't show clip indicators for not-soloed tracks [p=2485497]
• + VU meters: consistent rounding and clip indicator behavior across all peak metering
• + VU meters: display overs if record-input signal is >= +0dB, or playback signal is > +0dB
• + VU meters: improve appearance when using DPI-mapping [t=257953]
• + VU meters: fix RMS calculation with certain sample rates [t=257633]

[Edgemeal]

Awesome update! Thank You!

[ovnis]

"+ Media explorer: remember original playback start position when stopping (not pausing) preview, restart playback from that position"

Thx you.

When we click on a media would it be possible to replay the media from the beginning? It can be very useful when we make the preview of drums, for example.

[mtk]

fx containers in 6.38?

[mschnell]

Originally Posted by mtk

fx containers in 6.38?

AFAIR it's not in the list of feature branches that were in 6.36+, but not in 6.37rc. But "Media Item lanes" is .
-Michael

[mschnell]

How to find the ReaVerb Channel Tool ?

Thanks,
-Michael

[IXix]

Thanks Devs!

[Phazma]

Thanks devs, great update! Super happy about the VU meter changes and render limiting

[Phazma]

Originally Posted by ovnis

When we click on a media would it be possible to replay the media from the beginning? It can be very useful when we make the preview of drums, for example.

There definitely should be some behavior option for the second click on a playing file in the MX, rather than just nothing.

I personally would most love it to stop preview, which would be helpful to as quickly as possible interrupt playback of an unexpectedly loud sound. But your suggestion of triggering samples can definitely also be useful.

[nappies]

Thank you for huge update!

[mawi]

Where can I find ReaLimit?

[Justin]

Originally Posted by mschnell

How to find the ReaVerb Channel Tool ?

Thanks,
-Michael

Click the "Add" button in ReaVerb, should be first in the list. If not -- what OS/build is this?

[MetalSmurf]

Originally Posted by mawi

Where can I find ReaLimit?

Inside Reaper just search ReaLimit in the plugin window.

I just tried it and it seemed great. Easy, intuitive and does what it says on the tin. Can't get better than that

[Justin]

Originally Posted by mawi

Where can I find ReaLimit?

In the FX browser

[mawi]

Thanks, after scanning again (F5) it showed up in the FX browser!

[matt_t]

• + VU meters: consistent rounding and clip indicator behavior across all peak metering

Here's hoping this has fixed this https://forum.cockos.com/showthread.php?t=223980 en passant. Soon find out ...

[dylan.w]

great update, Thank you! Appreciating the improved menus on linux.

[Breeder]

Originally Posted by musicbynumbers

v6.37 - October 12 2021

• + Actions: fix quirks with 'Expand selected track height, minimize others' action and mouse mapping [t=257138]
  

For a moment there I thought this fixed this very irritating bug: https://forum.cockos.com/showthread.php?t=246060

[mschnell]

Originally Posted by Justin

Click the "Add" button in ReaVerb, should be first in the list. If not -- what OS/build is this?

Yep. There it is. Silly me expecting some extra button

Now exploring the possibilities later this day ...
-Michael

[bFooz]

Originally Posted by musicbynumbers

+ ReaLimit: add new program-dependent brickwall limiter plugin

From first tries I actually like how this is done!

One thing that might be missing is a vertical zoom of the waveform. With maybe a scale on side - just scale, no horizontal scale lines.

[bFooz]

+ ReaScript: add MIDIEditor_EnumTakes()

This finally came, thanks!

For the feature to be complete, setting the active context would be useful. See here if not already https://forum.cockos.com/showthread.php?t=168563

[bFooz]

Originally Posted by musicbynumbers

+ MIDI: reset CC/pitch on playback stop is now enabled by default

What would be useful ehre is that CCs are not reset immediately but in a slower fashion, like 200..1000ms or so.

A lot of VSTis play a bit after the playback is stopped. When the playback went at lower CC1, at the moment of hitting the stop button the CC1 is hard-reset but the sound continues a bit longer. The result is a short burst of louder sound.

If the reset was more gradual, this could be eliminated.

[AZpercussion]

Oh! I really love this update! Especially multichannel reaplugs, delta-solo and limiting in render. Good catch with timeselection auto punch and PDC. Hope, that auto monitoring behavior will be optimized too.

[Javier Robledo]

Great thanks a lot

[Thunderfinger]

Originally Posted by musicbynumbers

[*]+ JSFX: Loudness Meter integrated values (LUFS-I, LRA, RMS-I) only update when playing back

Is there any chance this could be a toggle in the loudness meter options? I have my loudness meter in the Monitor FX, and I use it to measure the LUFS-I and LRA of files in the Media Explorer. With this update, I can't measure files in the Media Explorer anymore.

[schwa]

Originally Posted by Thunderfinger

Is there any chance this could be a toggle in the loudness meter options? I have my loudness meter in the Monitor FX, and I use it to measure the LUFS-I and LRA of files in the Media Explorer. With this update, I can't measure files in the Media Explorer anymore.

Hmm, that's a bit of a specialized use so would it work for you to edit the jsfx to do what you want?

In the Add FX dialog, right click the loudness meter and choose Duplicate JS FX, give it a new name, then insert the duplicated plugin and click Edit. You'll need to change three lines as follows.

line 377 from

  (play_state&1) ? (

to

  1 ? (

line 399 from

a = (play_state&1) ? ((lufs_m_db+70)*BINS_PER_DB)|0 : -1;

to

a = ((lufs_m_db+70)*BINS_PER_DB)|0;

line 429 from

    b = (play_state&1) ? ((lufs_s_db+70)*BINS_PER_DB)|0 : -1;

to

    b = ((lufs_s_db+70)*BINS_PER_DB)|0;

[ramses]

The new limiter is brilliant and sounds and works great! Thanks for including it.

[Thunderfinger]

Originally Posted by schwa

Hmm, that's a bit of a specialized use so would it work for you to edit the jsfx to do what you want?

In the Add FX dialog, right click the loudness meter and choose Duplicate JS FX, give it a new name, then insert the duplicated plugin and click Edit. You'll need to change three lines as follows.

Yes, that worked for me. Thank you very much for the quick workaround.

[CraigD]

Thanks, you all are the best programmers on the planet. All these features and still only 15 Meg to download.

[mschnell]

Originally Posted by mschnell

Now exploring the possibilities later this day ...

I think I found a bug.

Using just a single IR file, no channel tool, just two channels, when activating ZL (which is active by default) I get very weird output - a kind of feedback supposedly with the full FFT size - when sending a signal in the right channel input channel (2), while sending into the left channel (1) works fine. With ZL deactivated, initially the output is OK, but after some time the problem gets prominent.

When using the Reverb generator with large Room size, the problem persists even when ZL is deactivated, but without ZL it's a bit less obvious.

Easily testable with the "Click source" sound and just adding ReaVerb and then Reverb generator with large Room size. The problem should show when either using a balance plugin before ReaVerb or turning on/off the channels by pin Routing. I in fact used a second track with the clock source glued and routed same to the ReaVerb track so that I could use the click's balance dial.

-Michael

[mschnell]

Regarding the Channel Tool, I also can't get it to work.

In the pin routing window, I set ReaVerb to 4 in channels and four out channels.
I send a mono signal to both channels 3+4, (silence to channels 1+2)

Out channels are connected straight (3->3, 4->4).
Nothing activated in ReaVerb.
In the track meters I see that the signal does come out on 3+4.
When in the pin routing I temporarily set the output to 3->1, 3->2, the signal goes to 1+2, and can be heard via the Master track.
But back to 3->3, 4->4...

I tried 1 the Channel Tool as well as "swap" (2 channels, as well source = 1 and dest = 3, as source = 3 and dest = 1), as as "add" (2 channels, source = 3, dest = 1), but this does not send anything to channels 1+2.

-Michael

[mschnell]

I then also tried a purely internal use of the Channel Tool in ReaVerb. In a simple 2 channel track I send a signal to channel 2 and silence to channel 1. Now I tried both "copy to" and "swap", with channel count 1 and destination channel 1, but never got any output on channel 1 of the track.

BTW.: this is on Win 64.

-Michael

[schwa]

The ReaVerb channel tool affects the impulse response, not the input signal.

For example, if you have a single-channel impulse response and stereo input, by default the impulse will be applied to both channels.

You could then add a channel tool with source=1, count=1, action=copy, destination=2, which will duplicate the impulse response into channel 2. The output will be the same but now you have the impulse on separate channels for further manipulation.

You could then add another channel tool with source=1, count=1, action=addto, destination=2, which will add the impulse to itself on channel 2, so the effect is doubled on channel 2. If you set action=subtractfrom instead, the impulse will be subtracted from itself, resulting in no reverb on channel 2.

[creal]

+ FX pin connector: support changing plug-in channel count, mulit-mono, multi-stereo configuration for ReaFX that support it

Now this feature is implemented, I think it could be interesting to choose which channel a ReaEQ band is processing (L = channel 1, R = channel 2, channel 3, channel 4, LR = stéréo, channels 3-4, etc.).

[mschnell]

Originally Posted by schwa

The ReaVerb channel tool affects the impulse response, not the input signal.

Your example does not demonstrate "free" channels e.g. 3+4, if the plugin is defined a 2 in 2 out.

IMHO, not intuitive and not a good idea whatsoever.

If only the "elements" are concerned, I don't see how to verify what is happening, as the elements have no meters nor can their channels directly be auditioned.

IMHO ReaVerb internally should handle the channels in a compatible way to pin routing. I.e. if the pin routing is 1->, 2->2, 3->3, ... on input and output, the rack channels should be reproduced and available for assigning to the inputs and outputs of the Elements and to the ReaVerb output "pins" (e.g. via "swap")
(Don't know if another implementation would be (easily) doable...)

What I tried to do as an example was a full stereo Reverb created by two stereo impulse files "in parallel", that are fed by the left (1) and the right (2) input channel respectively, and their outputs (channel 1+2 with with of them) mixed together.
Here obviously the "file" elements have mono inputs (AFAIK mixing together input channels 1+2) and stero outputs on channels 1+2, hence the Channel Tool elements are necessary.

My idea was (e.g.) to
- copy channel 2 to channel 3
- copy channel 2 to channel 4
- copy channel 1 to channel 2
- "left" reverb impulse file to create stereo output for left source
- swap channel 1+2 with 3+4 for allow for bypassing left reverb and have right signal be worked on
- "right" reverb impulse file to create stereo output for right source
- add channels 3+4 to channels 1+2 for full stereo reverb in "pins" 1+2.

Maybe this even does work, but I don't know how I am supposed to definitively check it.

-Michael

[Justin]

ReaVerb in X channel mode applies one channel of impulse response to each input channel, and produces output on that same channel.

The Channel Tool can be used to combine multiple stereo impulse responses into a 4 channel impulse response, for example. You could do File, then swap those channels to 3/4, then add another File (which then goes to 1/2), thus producing 4 channels of impulses responses from two stereo files. How you map these 4 channels to the I/O is up to you and done via the pin mapper.

[mschnell]

Originally Posted by Justin

ReaVerb in X channel mode applies one channel of impulse response to each input channel, and produces output on that same channel.

Sorry for being a bit dense

Originally Posted by Justin

The Channel Tool can be used to combine multiple stereo impulse responses into a 4 channel impulse response, for example. You could do File, then swap those channels to 3/4, then add another File (which then goes to 1/2), thus producing 4 channels of impulses responses from two stereo files.

I still don't see how to feed different signals to the file elements (which I understand add channels 1+2 to be used as a mono input to the dual convolution, at least with the impulse files I know and love <called "M-to-S", while - obviously mono-input "L" and "R" files also are available>, and/or with the previous version of ReaVerb <which did not feature the "right input channel bug" I mentioned in the message above, and hence might have been purely "mono-input">).

Originally Posted by Justin

How you map these 4 channels to the I/O is up to you and done via the pin mapper.

I certainly can do this.

Nonetheless it would be nice to be able to create a full stereo (or even more complex) configuration internally in (a 2 channel) ReaVerb, so that this preset could be easily reused.

-Michael

[mschnell]

Originally Posted by mschnell

I think I found a bug. ,,,

I additionally installed the old version of ReaVerb, and it features the same quirk.

I reproduced it simply using a clicj source item, the "Reverb Generator" (room size 65, every thing else = default) and pin routing:

Very different output with ZL enabled with input "pin" channel 1 vs channel 2 connected to the sound source (bad with channel 2).

Very weird: if I additionally connect the input to channel 1 pin, the problem with channel2 seems to vanish ?!?!?!?

Am I doing something wrong ? Can anybody verify this ?
-Michael

[Justin]

Originally Posted by mschnell

I additionally installed the old version of ReaVerb, and it features the same quirk.

I reproduced it simply using a clicj source item, the "Reverb Generator" (room size 65, every thing else = default) and pin routing:

Very different output with ZL enabled with input "pin" channel 1 vs channel 2 connected to the sound source (bad with channel 2).

Very weird: if I additionally connect the input to channel 1 pin, the problem with channel2 seems to vanish ?!?!?!?

Am I doing something wrong ? Can anybody verify this ?
-Michael

Thanks, looking into this! (edit: an old bug, now fixed in convoengine and will be fixed in the next builds)