v6.09+dev0428 - April 28 2020

[mschnell]

Originally Posted by Joe90

... CPU heavy projects with lots of heavy latent plugins at high buffer sizes...

The improvement only will be noticed, when stacking multiple plugins with non zero but low PDC in a row.

-Michael

[JamesPeters]

Originally Posted by AtmanActive

I agree with White Tie here, this new feature:

+ Appearance: add Options / User Interface Color Controls

has nothing to do with themes and colors.
It is like your monitor controls built into the software.
You set it once you buy a new monitor and forget about it.

That being said: you may want to adjust it differently for different themes, since each theme can vary significantly in terms of contrast/brightness/saturation (etc.) I've already noticed this and I only had a couple different themes installed. I like the fact this new option works "per theme" now.

[dupont]

Originally Posted by Reflected

Here is a video showing a real aweful REAPER midi bug:

https://youtu.be/IY4HQjF1qHg

Reported many times in the bug section. I faced that yesterday with Spire VST, I had to put a reacontrol midi in the track to stop stuck note happens again.

[Reflected]

Originally Posted by dupont

Reported many times in the bug section. I faced that yesterday with Spire VST, I had to put a reacontrol midi in the track to stop stuck note happens again.

reacontrol midi doesn't help here.

[Mercado_Negro]

Originally Posted by vitalker

v6.09+dev0428 - April 28 2020

+ Delay compensation: FX chains can be set to compensate delay Per-FX, Per-chain, or not at all
+ Delay compensation: in record input FX and monitoring FX, when not in ignore delay compensation mode, dry signal is now kept synchronized to wet signal (change from previous behavior)
+ Delay compensation:master FX chain can be set to compensate delay at the hardware-send level

I'd like to understand one thing: my buffer size is set to 2048 and I can add all plugins I want to a chain and it never goes above of 2048 but if I add a UAD plugin it does go above of 2048. Why?

[schwa]

Originally Posted by svijayrathinam

Media Explorer doesn't read metadata from these FLAC Files. These files have metadata. I can see these in sound miner. But Media Explorer won't read this.

Just to close this, Soundminer does indeed store metadata in a proprietary format that is intentionally not readable by other applications. If you want to see this metadata in any software other than their paid products, you have to use their paid products to export the files with metadata embedded in a non-proprietary format.

[Justin]

Originally Posted by Mercado_Negro

I'd like to understand one thing: my buffer size is set to 2048 and I can add all plugins I want to a chain and it never goes above of 2048 but if I add a UAD plugin it does go above of 2048. Why?

Hmm, UAD plug-ins are always set to 1 block of latency, right? It's been a while since I've used them...

[Mercado_Negro]

Originally Posted by Justin

Hmm, UAD plug-ins are always set to 1 block of latency, right? It's been a while since I've used them...

The latency of most UAD plugins is 2167 samples at 96kHz/2048.

[schwa]

So that's why it needs more than one buffer block of 2048 samples, right?

[Mercado_Negro]

Originally Posted by schwa

So that's why it needs more than one buffer block of 2048 samples, right?

Probably?

The UAD plugins have a LiveTrack mode (it's a little mic icon that you can turn on/off per plugin). In that mode they don't seem to add that extra block (chain latency remains at 2048). The problem with that mode is CPU load, it's like 3 or 4 times more when enabled.

The question now is, is this a "live with it" thing or the work you're doing now can do something about it?

[schwa]

Originally Posted by Mercado_Negro

The question now is, is this a "live with it" thing or the work you're doing now can do something about it?

If a plugin needs 2167 samples of latency, that will be more than one buffer block of 2048 samples no matter whether the buffering is per-plugin or per-chain, so this is a live with it thing. On the positive side, with the new pre-chain PDC, you can add additional plugins to that same chain and as long as the total latency doesn't go beyond 4096 samples, you'll have the same total latency, rather than two blocks for the UAD plugin plus at least one more block of latency per additional PDC-adding plugin.

[Mercado_Negro]

Originally Posted by schwa

If a plugin needs 2167 samples of latency, that will be more than one buffer block of 2048 samples no matter whether the buffering is per-plugin or per-chain, so this is a live with it thing. On the positive side, with the new pre-chain PDC, you can add additional plugins to that same chain and as long as the total latency doesn't go beyond 4096 samples, you'll have the same total latency, rather than one block of latency per plugin.

Cool! Thanks, Schwa. Understood. Makes sense now. That's good news indeed.

[pepe44]

+ Delay compensation: FX chains can be set to compensate delay Per-FX, Per-chain, or not at all
+ Delay compensation: in record input FX and monitoring FX, when not in ignore delay compensation mode, dry signal is now kept synchronized to wet signal (change from previous behavior)
+ Delay compensation: master FX chain can be set to compensate delay at the hardware-send level

YES

[nikolalkc]

Originally Posted by vitalker

[*]+ ReaScript: add RENDER_TARGETS, to retrieve the list of files that would be written given current project render settings

YES, THANK YOU FOR THIS, OMG )))

[vitalker]

Originally Posted by PhelixK

+ Appearance: add Options / User Interface Color Controls

I do welcome the new UI color feature and the good ideas of ​​collecting everything related in a single place.

At the same time, I also think these settings should be made available with a giant "caution" sign, especially if the advanced Tweaker is included. Then the user will know the risk of messing up things.

You should firstly check last versions, cause it already is in a one place. These settings don't change anything, so you can't mess anything up. The button "Reset" reverts everything to defaults. Are you sure you get the meaning of this feature?

[PhelixK]

Originally Posted by vitalker

You should firstly check last versions, cause it already is in a one place. These settings don't change anything, so you can't mess anything up. The button "Reset" reverts everything to defaults. Are you sure you get the meaning of this feature?

haha, thanks for your kind help vitalker. I just realize I was replying to an older pre-release, I will of course check out the latest release and discussion. As for my other suggestions, I'm sure they have already been answered as well. rgds /f.

[vitalker]

Originally Posted by PhelixK

haha, thanks for your kind help vitalker. I just realize I was replying to an older pre-release, I will of course check out the latest release and discussion.

Now it is theme-dependent and when you change the theme, the settings are also changing. And it doesn't change anything in a theme code, so nothing will be affected. Stay healthy.

[PhelixK]

Originally Posted by vitalker

Now it is theme-dependent and when you change the theme, the settings are also changing. And it doesn't change anything in a theme code, so nothing will be affected. Stay healthy.

Yes, I will check it out of properly of course. I’ve been following and testing the work from amagalma and his Adjust Theme Colors script, and this native implementation looks to be a great feature as well, but I haven’t yet tried it.

In concern of my suggestions about the Tweaker, font management and Theme Adjuster, I will wait for another time.

good w/e to you!

[pepe44]

Trying the PDC modes, works great for the simple tests i did.
What i noticed is that tracks get a lower PDC but CPU on those tracks increase by a reasonable amount. what was 0.3% now gets to 1.7% for example. But like Justin said , it all will need a lot of testing.
I´ll do some more tests with outboard, printing tracks and so on.

Thanks devs , this is promising

[X-Raym]

RENDER_TARGETS

Many thanks for that !


Here is code snippet for those interested: https://github.com/ReaTeam/ReaScript...%20targets.lua

[Mordi]

Originally Posted by vitalker

[*]+ Appearance: add Options / User Interface Color Controls

Ah, I thought this was a way to make unthemable colors darker/lighter - but this is pretty rad too!