v6.63+dev0705 - July 5 2022

[sockmonkey72]

v6.63+dev0705 - July 5 2022

• * Includes feature branch: render fade-in/fade-out
• * Includes feature branch: pan law/function improvements
• * Includes feature branch: media explorer loudness calculation
• * Includes feature branch: render statistics improvements
• * Includes feature branch: fixed lane play markers
• * Includes feature branch: improve experimental silent-track CPU reduction option to include FX tail length
• * Includes feature branch: media item fixed lanes
• * Includes feature branch: internal pin management overhaul for future extension
• + GIF: fix memory leak when decoding files that have per-frame color maps
• + GIF: fix reduce memory use when decoding gif files with many frames
• + Help menu: sort documentation menu by filename [t=268485]
• + JSFX: set undo point after calling set_pinmapper_flags()
• + JSFX: support automating and undo for user mix volume sliders in channel mapper [t=266268]
• + Normalization: respect take channel mode when normalizing media items to target loudness [t=268290]
• + Project bay: add option to disable similar FX grouping in FX tab
• + Region manager: support selecting marker/region by name by typing in list view [t=268219]
• + Render: re-enable bounds dropdown if needed after loading render preset [t=268430]
• + Theme: improve rounding for knob stacks [p=2575187]
• + VST3: IContextInfoProvider3 support
• + VST3: fix return value for IContextInfoProvider::setContextInfoValue
• + VST: support IComponentHandler2::setDirty [t=268392]
  

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

[kindafishy]

Oh Justin or Schwa,

Since you guys are in the project bay, would it be possible (if it makes sense) to keep the line highlighted after selecting an FX and clicking bypass, so we can click unbypass again without going back up and selecting the line again? Maybe this only works if the number of instances of the plugins that were bypassed or unbypassed stays the same, but if this is pretty easy to do, it would make life much nicer for comparing the song with a whole set of plugins enabled or disabled at the same time (I know there are scripts and SWS things that help with this, but being able to do this from the project bay would be cool.

Cool if yes, cool if no .

[PhelixK]

+ Theme: improve rounding for knob stacks [p=2575187]

By default it's better for symmetric knob stacks.

Unfortunately I'll need to update a lot of knobs since they will now have an offset from using this new rounding. Hopefully I'm the only one who has taken account of the old behavior in order to have more accurate knob position versus the actual value.


Another thing related to knobs behavior and usability:
I've seen examples where the coded knob pointers could benefit from having a stronger marking. 1px thickness is almost invisible when drawn in Hi-DPI. This line thickness should really be scaled up accordingly, and perhaps even possible to define for themes. I hope it will be considered, thanks.

[Mercado_Negro]

Originally Posted by kindafishy

Oh Justin or Schwa,

Since you guys are in the project bay, would it be possible (if it makes sense) to keep the line highlighted after selecting an FX and clicking bypass, so we can click unbypass again without going back up and selecting the line again? Maybe this only works if the number of instances of the plugins that were bypassed or unbypassed stays the same, but if this is pretty easy to do, it would make life much nicer for comparing the song with a whole set of plugins enabled or disabled at the same time (I know there are scripts and SWS things that help with this, but being able to do this from the project bay would be cool.

Cool if yes, cool if no .

Yes, please!

[musicbynumbers]

Thanks devs!

Something else in the project bay that might be useful is a track number column so we can order the plugins grouped and listed by track order (unless I missed it?)

We can do track name but it would be nice sometimes to see them in order so that say all my plugins for drums are in the same area of the project bay.

No worries if not!

[AZpercussion]

+ JSFX: set undo point after calling set_pinmapper_flags()
Don't know about this, but there was an undo/redo ability for pin mapping of any plugin in earlier versions.
And now in Channel Mapper's window there is only undo ability, but not redo.

Also checkmarks like "user mix", "zero out" don't included in undo.
But if I change pins or zero out/pass through mode via standart plug-in dropdow menu all works well.


+ JSFX: support automating and undo for user mix volume sliders in channel mapper [t=266268]

Thanks for this!

Please, take a look at linking also.
Mostly we works with stereo signals and for this common case would be better to write only 1 volume automation for both channels.
So if I have only one active envelope (or one modulated parameter) of two linked channels, the second channel should follow the first.

And auto-resizing plugin window bounds would be really appreciated.
Honestly, if I increase channels number, I really whant to see all pins to manage them.

[rncwalker]

Originally Posted by sockmonkey72

v6.63+dev0705 - July 5 2022

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

I Really amazed at how 'many "DO NOT" obey the posting requirements.
We have:

Thanks for this!

Please, take a look at linking also......

and

Thanks devs!

Something else in the project bay that might be useful.....

and

Since you guys are in the project bay, would it be possible....

All Request!

Robert

[Klangfarben]

Originally Posted by rncwalker

I Really amazed at how 'many "DO NOT" obey the posting requirements.
We have:

Thanks for this!

Please, take a look at linking also......

and

Thanks devs!

Something else in the project bay that might be useful.....

and

Since you guys are in the project bay, would it be possible....

All Request!

Robert

And perhaps you think your post causes less noise and distractions to the thread? As you yourself "DID NOT" obey the posting requirements maybe you can give others a pass for thanking the devs for their efforts. Just a thought.

[AZpercussion]

Originally Posted by rncwalker

Please, take a look at linking also......

I said this just because of link on my bug report, where I shown this problem. To not miss this point.

But honestly it's rather constructive to suggest something "in fhase" with development. How much suggestions are congruent - let devs decide.

If I'm wrong, correct me, devs.

[ovnis]

"+ Theme: improve rounding for knob stacks [p=2575187]"
Don't know if it's related but now, my pan knob is not on the good state.

What I have:


What I should have:

[Justin]

Originally Posted by ovnis

"+ Theme: improve rounding for knob stacks [p=2575187]"
Don't know if it's related but now, my pan knob is not on the good state.

What I have:


What I should have:

Ah do you have an even number of knob slices? Perhaps we'll use the old logic for those

[ovnis]

Originally Posted by Justin

Ah do you have an even number of knob slices? Perhaps we'll use the old logic for those

Hello. It's good. I have tweaked my png to solve the issue.

[Justin]

Originally Posted by ovnis

Hello. It's good. I have tweaked my png to solve the issue.

For my future reference, did you previously have an even number of slices?

[ovnis]

I'm not sur to understand well the question.

To solve the issue I have deleted one slice.

[PhelixK]

Originally Posted by Justin

For my future reference, did you previously have an even number of slices?

As far as I can see when running v664rc1, the buttons are centered correctly, regardless of whether even or odd number of slices are used in total, that's good! Using an odd number is now preferable in relation to the changed rounding.

[ovnis]

Originally Posted by Justin

For my future reference, did you previously have an even number of slices?

Yes!