v6.36+dev0904a - September 4 2021

[vitalker]

v6.36+dev0904a - September 4 2021

• * Includes feature branch: ReaLimit
• * Includes feature branch: MIDI editor note reordering
• * Includes feature branch: media item lanes
• + Actions: fix quirks with 'Expand selected track height, minimize others' action/TCP doubleclick mouse mapping [t=257138]
• + Batch converter: add brickwall limiter option
• + ReaLimit: add new program-dependent brickwall limiter plugin
• + ReaLimit: support embedded UI
• + Render: add brickwall limiter option
• + Render: display gain reduction in render peaks display when limiting
• + Render: fix peaks display with very short files
• + VST: improve hard-reset mode to reset soft-reset-only plug-ins
• # Project bay: speed up loading of project bays with many retained media items [p=2477382]

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

[vitalker]

Originally Posted by vitalker

* Includes feature branch: ReaLimit

This color combination doesn't look good for my eyes and not much readable.

[schwa]

It’s true that the display is not optimized for 24 dB of gain reduction.

[airon]

HoHooo. This I am testing ASAP on my rig.

What‘s the latency if any ?

[vitalker]

Originally Posted by schwa

It’s true that the display is not optimized for 24 dB of gain reduction.

Sorry schwa, I rather mean intensive yellow. At least on the left it could be red like in ReaComp. On the right less intensive yellow would look better. And maybe a bit lighter black.

[Coachz]

Originally Posted by vitalker

Sorry schwa, I rather mean intensive yellow. At least on the left it could be red like in ReaComp. On the right less intensive yellow would look better. And maybe a bit lighter black.

Yeah, that's ugly

[Freiin]

Oh yeah! New plugin. Thanks Justin and John.

[citizenkeith]

Originally Posted by vitalker

v6.36+dev0904a - September 4 2021

• * Includes feature branch: ReaLimit

Fantastic! I gave it a spin and I like what I hear.


Can we have attack and release as well?

[AZpercussion]

Originally Posted by vitalker

Sorry schwa, I rather mean intensive yellow. At least on the left it could be red like in ReaComp. On the right less intensive yellow would look better. And maybe a bit lighter black.

I'm agree! So strong contrast by color and brightness... too much.
And yellow line unvisible on the white.
Would be better with less saturation and may be with gradient in top section. Also treshold lines could be red for more visibility and sense, because yellow is just background in the top section, right?

[mb945]

Originally Posted by airon

What‘s the latency if any ?

It looks like it has 480 samples of PDC latency (at 48k sample rate).

[Breeder]

Originally Posted by vitalker

v6.36+dev0904a - September 4 2021

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

These two bugs might be related:

Originally Posted by Breeder

If the option 'Preferences->Audio->Recording->Always show full track control panel on armed tracks' is on and tracks are set to auto-record arm - something becomes not right when selecting items with mouse:

[mschnell]

Real Limit:

What is the advantage over using the stock plugin ?

-Michael

[vitalker]

Originally Posted by mschnell

What is the advantage over using the stock plugin ?

Read the release notes and you'll understand immediately.

[Phazma]

Originally Posted by vitalker

v6.36+dev0904a - September 4 2021[*]+ Render: add brickwall limiter option

Wait.. does this mean we can now specify both lufs normalization and true peak limiting in the render dialog and Reaper creates the file with the right specs for delivery in one go without re-importing and re-rendering?

Can test only tomorrow but if what I said is the case it is awesome! Then the only thing missing would be the possibility to render video when normalization and limiting are active.

[javiramallo]

Originally Posted by Phazma

Wait.. does this mean we can now specify both lufs normalization and true peak limiting in the render dialog and Reaper creates the file with the right specs for delivery in one go without re-importing and re-rendering?

I would bet that this is the end point that it want (and should) get to.

And I am think the same,is fantastic.
Thanks Devs.

[mustgroove]

Originally Posted by vitalker

[*]+ Render: add brickwall limiter option

This is cool - on a related note, what about a "Post-limiter" option for when resampling is happening during? The RX 8 manual explains:

This option is important when resampling signals that are very close to 0 dB, because filtering during resampling can change peak levels of a signal.
Engage the Post-limiter option in order to limit the output levels of your signal to prevent any clipping from occurring.

[Paul Eye]

Originally Posted by vitalker

v6.36+dev0904a - September 4 2021

• * Includes feature branch: ReaLimit
• + ReaLimit: add new program-dependent brickwall limiter plugin

Whoa. I need to test this against LoudMax concerning ISP/True Peak limiting.

[EvilDragon]

Please no yellow. Sincerely, everyone's eyes.

[USR]

It can be yellow. Maybe not #ffff00, but something easier on the eyes.

[Vagalume]

Yep, that yellow-black combination is a little better.

[schwa]

If we could just take the yellow-hating as heard and move on please?

Originally Posted by mschnell

What is the advantage over using the stock plugin ?

If you mean ReaComp, it's not a limiter. If you mean why use the render limit option rather than the ReaLimit plugin, it's the same DSP, the only difference is that the render limiting is applied after sample rate conversion and normalization.

Originally Posted by Phazma

does this mean we can now specify both lufs normalization and true peak limiting in the render dialog and Reaper creates the file with the right specs for delivery in one go without re-importing and re-rendering?

Almost. You can specify loudness normalization and true peak limiting, but the limiting is applied after the normalization, so if you're doing a lot of limiting, the final loudness may end up lower than your target. You can do a dry run render with your loudness and peak settings to see what the final loudness is, and if the limiting is reducing the final loudness too much, you can either adjust the render loudness target upwards to compensate, or (maybe more appropriately) make some other adjustment to your mix to avoid having to apply so much limiting during the render process.

[Valle]

* Includes feature branch: ReaLimit

Oh, really! Wow!

I remember maaany years ago when a small handful of expert users (not devs) didn't see any point or use in feature-requesting or developing a (Rea)Limiter ("ReaComp is a also limiter", "waste of resources", etc), which was made loudly clear to us lesser expert users who had the nerve to make such suggestions ... I, myself, was pretty much taught a lesson in this thread

ReaLimit is nice to see, and it will be usefull! (Although, I think I've gotten too used to my FabFilter Pro-L over the years)

[Daodan]

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

Thanks!

[benf]

[*] * Includes feature branch: ReaLimit

is a very fine and appreciated addition. I tested it and found it very user friendly to use instead of the JS Master Limiter which is my common limiter until now. So, many thanks for this !
I suppose this developpement is also related to same code part as all the recent versions with render metering and so on.

But.

On each new Pre-Release until months, we see the

[*] * Includes feature branch: MIDI editor note reordering

feature appearing and disappearing constantly when arriving on RC version. My only question is will it happen one day ?

[Phazma]

Originally Posted by schwa

Almost. You can specify loudness normalization and true peak limiting, but the limiting is applied after the normalization, so if you're doing a lot of limiting, the final loudness may end up lower than your target. You can do a dry run render with your loudness and peak settings to see what the final loudness is, and if the limiting is reducing the final loudness too much, you can either adjust the render loudness target upwards to compensate, or (maybe more appropriately) make some other adjustment to your mix to avoid having to apply so much limiting during the render process.

Thanks for the thorough explanation, can’t wait to try it out tomorrow. Actually to my knowledge in the situations where this workflow is needed the specs are usually such to allow ample headroom and the tp limiting is only for safety to catch some stray peaks. So I think the deviation would be negligible and the implementation perfectly suitable for this type of work.

[musicbynumbers]

Thanks devs!

The limiter is going to be massively helpful for so many things as I tend to put the limiter on each track so this is a massive thing! Thanks!

[svijayrathinam]

Can you pls make this limiter to support Multi Channel with just one plugin ? In fact can you pls make all reaper stock plugins multi channel ? Pls

[Soli Deo Gloria]

Originally Posted by vitalker

+ ReaLimit: add new program-dependent brickwall limiter plugin

Immense thanks, devs! A good limiter with true peak detection was missing in Reaper. It seems to work just fine, as far as I can briefly test (I'm comparing it mainly with the x42 Digital Peak Limiter, which is a nice one, too). This will be routinely used here, I see.



Thanks again!!!

[vsgrt]

Impressed by this limiter. Thanks a lot.

[musicbynumbers]

Multichannel would be very useful for sure!

Both linked and unlinked limiting if possible.

[fakemaxwell]

Did some testing of ReaLimit, comparing it to FabFilter Pro-L 2. Sounds a lot like the "Safe" mode in Pro-L. Very useful but it does smush the transients a lot, so if you use a lot of limiting in a very punchy mix it'll take the edge off.

I don't think the many modes of something like Pro-L are necessary at all, but down the line adding just a few more parameters to be able to tame the overprotective nature would be helpful.

[MrTsonts]

Originally Posted by vitalker

This color combination doesn't look good for my eyes and not much readable.

If it's a dark theme, it's okay.

[Delucci]

Originally Posted by benf

is a very fine and appreciated addition. I tested it and found it very user friendly to use instead of the JS Master Limiter which is my common limiter until now. So, many thanks for this !
I suppose this developpement is also related to same code part as all the recent versions with render metering and so on.

But.

On each new Pre-Release until months, we see the

feature appearing and disappearing constantly when arriving on RC version. My only question is will it happen one day ?

Exactly my thoughts. Midi note reorder has been in the pres in a while now. Every new RC I pray for this to be available. Even tho I'm used to the midi editor now, I dont even use drum maps anymore. I just know that the Kick is 36, Snr 38, toms 47,45.. I guess I spent a lot time using Guitar Pro to program drums.

[MrTsonts]

Originally Posted by fakemaxwell

I don't think the many modes of something like Pro-L are necessary at all, but down the line adding just a few more parameters to be able to tame the overprotective nature would be helpful.

I think so too.

[MrTsonts]

Originally Posted by Delucci

Exactly my thoughts. Midi note reorder has been in the pres in a while now. Every new RC I pray for this to be available. Even tho I'm used to the midi editor now, I dont even use drum maps anymore. I just know that the Kick is 36, Snr 38, toms 47,45.. I guess I spent a lot time using Guitar Pro to program drums.

I agree. For example, I cannot return to the normal version due to the fact that there are no item lanes ))))))

[chmaha]

Originally Posted by schwa

If you mean ReaComp, it's not a limiter. If you mean why use the render limit option rather than the ReaLimit plugin, it's the same DSP, the only difference is that the render limiting is applied after sample rate conversion and normalization.

If a user normalizes and limits as part of the render, when is dither applied if selected? i.e. is the process order: SR conv --> normalization --> limiting --> dither?

[Triode]

Originally Posted by BethHarmon

If a user normalizes and limits as part of the render, when is dither applied if selected? i.e. is the process order: SR conv --> normalization --> limiting --> dither?

Also would it be a viable workflow to render the file that's generated from the sample rate conversion higher bit depth to allow greater headroom (to accommodate inter-sample overs). If that's mathematically viable that would solve guessing how much to reduce the gain for SR conv and make the limiter really handy in that scenario too.

[schwa]

Originally Posted by BethHarmon

If a user normalizes and limits as part of the render, when is dither applied if selected? i.e. is the process order: SR conv --> normalization --> limiting --> dither?

Yes. .

[RobinGShore]

# Project bay: speed up loading of project bays with many retained media items [p=2477382]

Much better now! Thank you