v6.36+dev0917 - September 17 2021

[musicbynumbers]

v6.36+dev0917 - September 17 2021

• * Includes feature branch: ReaLimit and render limiting
• * Includes feature branch: MIDI editor note reordering
• * Includes feature branch: media item lanes
• * Includes feature branch: multichannel, multi-mono, multi-stereo ReaPlugs
• + Media explorer: add configurable crossfade
• + ReaFIR: configurable channel count from 1-64 channels in multi-mono and multi-stereo configurations, metering options

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[BartR]

That's excellent. It's taking the good heading

[heda]

ReaLimit waveform is drawn a bit outside the window, it crops part of the bottom. bottom red line disappear outside the window at the bottom while adjusting the ceiling.

(on old machine with windows 7, font display scaling set to 125%)

changing windows font scaling to 100% fixes it.

[blumpy]

I set a true peak of -1 on the brickwall limiter with Normalize Mix Master and Common Gain to Stems. The output stems are an exact match with the mix except during overages. The limited stems sum to +1.5 db where as the mix file is correct at -1db peak. The stems should sum to exactly to the mix and peak with the limiter at -1 just like the mix.

[chuckwood]

Originally Posted by musicbynumbers

v6.36+dev0917 - September 17 2021
[*] * Includes feature branch: multichannel, multi-mono, multi-stereo ReaPlugs

Very cool, thanks. Will this have any impact on Reaverb's ability to handle multichannel files or is that something completely separate?

[chmaha]

Originally Posted by chuckwood

Very cool, thanks. Will this have any impact on Reaverb's ability to handle multichannel files or is that something completely separate?

Being able to directly load up Quad IRs would be great!

[mabian]

Is it normal that moving an envelope node (with a square shape on the previous node) also influences earlier envelope segment shapes?



I'm not sure this is right...

Thanks,
Mario

[svijayrathinam]

* Includes feature branch: multichannel, multi-mono, multi-stereo ReaPlugs


This is awesome ! Pls Support 3rd party AU and VST plugins pls...And Reaverb too. Being able to load a 5.0 Impulse or using a stereo impulse and use that as multi mono (with volume slider controls in the plugin pin configuration window for each channel) will be very useful

[nofish]

Originally Posted by mabian

Is it normal that moving an envelope node (with a square shape on the previous node) also influences earlier envelope segment shapes?

I'm not sure if it's right or wrong in this particular case, but generally, moving envelope points can influence neighbour segments, that has been so for a while and also mentioned by schwa:

https://forum.cockos.com/showthread....73#post1691673
https://forum.cockos.com/showthread.php?p=430875

[Vagelis]

Originally Posted by nofish

I'm not sure if it's right or wrong in this particular case, but generally, moving envelope points can influence neighbour segments, that has been so for a while and also mentioned by schwa:

https://forum.cockos.com/showthread....73#post1691673
https://forum.cockos.com/showthread.php?p=430875

But it shouldn't happen because it affects something else while you edit a different segment. This bezier implementation is also weird in general, when you have linear shape and bend the curve it automatically change to bezier, i get that the curves are based on bezier shape, but this is also not correct to me. It should go back to linear when at 0 curve.

[mabian]

Indeed, I'm moving values after a square node. This should not affect in my opinion earlier nodes, even bezier, because there's no curve in a square node...

- Mario

[ashcat_lt]

Originally Posted by blumpy

The stems should sum to exactly to the mix and peak with the limiter at -1 just like the mix.

That makes absolutely no sense because if you mix the stems any other way, the limited wouldn’t necessarily want to do the same things, but they’d already have that limiting from the original mix (which is now inappropriate) baked in.

That said, it’s commonly requested nonsense. I wouldn’t expect the limiter in the render window to do it, but it IS one of the things the new multichannel capabilities of ReaLimjt could handle, if you route things correctly.

[Arthur McArthur]

I have a few FRs related to this round of updates:

1: an option for the media explorer where every single click on a file starts playback from the start. This would allow us to jam with the media explorer more like an instrument, trying out sounds in context repeatedly.

2: the ability to multichannel render up to 64 channels

3: this might be out of scope, but an upgraded RS5K with more robust Volume Envelopes AHDSR with curve edit would be so useful

[Berg]

Originally Posted by svijayrathinam

* Includes feature branch: multichannel, multi-mono, multi-stereo ReaPlugs


This is awesome ! Pls Support 3rd party AU and VST plugins pls...And Reaverb too. Being able to load a 5.0 Impulse or using a stereo impulse and use that as multi mono (with volume slider controls in the plugin pin configuration window for each channel) will be very useful

Thanx for those multichannel developments ! Yes, if you could give support with 3rd party AU and VST for multi-mono and give the possibility to configure the parameters for each channel it would be very useful !

[Kewl]

Originally Posted by Arthur McArthur

2: the ability to multichannel render up to 64 channels

Just type in the number of channels you want in the Channels field

[schwa]

Originally Posted by blumpy

I set a true peak of -1 on the brickwall limiter with Normalize Mix Master and Common Gain to Stems. The output stems are an exact match with the mix except during overages. The limited stems sum to +1.5 db where as the mix file is correct at -1db peak. The stems should sum to exactly to the mix and peak with the limiter at -1 just like the mix.

Hm, yes I think "common gain to stems" does imply common gain reduction to stems if you are limiting. But it also seems a little weird to bake the dynamic processing on the master track back into the stems this way.

[deeb]

Originally Posted by nofish

I'm not sure if it's right or wrong in this particular case, but generally, moving envelope points can influence neighbour segments, that has been so for a while and also mentioned by schwa:

https://forum.cockos.com/showthread....73#post1691673
https://forum.cockos.com/showthread.php?p=430875

Im my point of view is wrong and makes no sense in common user perspective.

edit: editing should be simple if this is not achieved is because the solution did not nail it.

[BartR]

Originally Posted by deeb

Im my point of view is wrong and makes no sense in common user perspective.

edit: editing should be simple if this is not achieved is because the solution did not nail it.

Always from a user perspective, I do agree with you.
Moving a segment and having influences on adjacent segments, is something I would avoid.
Because if I choose for a certain envelope into one segment, is because I needed that one, and not any other one. The same for the second segment I'm editing.

If something like in the animated GIF is occurring, will constrain me to switch to a more clunky workflow, perhaps splitting the item, and working them separately. Which it's not always the case to do so.

As secondary consequence,I will be always cautious on any action with the fear to edit one part that's influencing what I already did and it worked. To work with uncertainties in the tool behaviour, is a no-go.

[blumpy]

Originally Posted by schwa

Hm, yes I think "common gain to stems" does imply common gain reduction to stems if you are limiting. But it also seems a little weird to bake the dynamic processing on the master track back into the stems this way.

I know... having dynamics processing on stems is generally a bad idea, but in a pinch this would be an extremely helpful tool.