v6.73+dev0124a - January 24 2023

[sockmonkey72]

v6.73+dev0124a - January 24 2023

• * Includes feature branch: mouse modifier small ID action binding fix
• * Includes feature branch: fixed lane comping
• * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections
• * Includes feature branch: improve samplerate change behavior when loading projects
• * Includes feature branch: VST3 re-map of parameter IDs due to restartComponent
• * Includes feature branch: AU parameter list change notification support
• * Includes feature branch: MIDI editor screenset improvements
• * Includes feature branch: routing matrix/track wiring input activity indicators
• * Includes feature branch: preview item selection for grouped tracks
• * Includes feature branch: VST3 per-channel silence reporting compatibility option
• * Includes feature branch: better .RfxChain media explorer and clipboard integration
• * Includes feature branch: ReaReaRea timestretch mode
• * Includes feature branch: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: JSFX new features and EEL2 preprocessor
• * Includes feature branch: render dialog statistics display improvements
• * Includes feature branch: media item fixed lanes
• + API: improve performance of SetMouseModifier()
• + ARA: Old projects may not load correctly! If the project contains separate ARA edits to multiple media items that use the same media source
• + ARA: associate edits more persistently with the source audio file
• + IDEs: suggest list does not respond to mouse movement when inactive [t=275197]
• + Notation editor: improve layout when resizing in continuous scroll view [p=2032295]
• + Tooltips: prevent tooltips from occuring when window is inactive [t=233380]
• # API: optimize performance of SetMouseModifier() reset of single section to defaults
• # Actions window: add menu item to copy main section keyboard shortcuts to alternate section
• # Media item lanes: improve behavior when a short comp area moves through a longer comp area
• # Media item lanes: internal changes
• # Media item lanes: support automatic crossfade between comp areas (not yet editable or configurable)
• # ReaReaRea: add dotted and triplet modes
• # ReaReaRea: change tempo sync range from 1/128 to whole notes

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

[sockmonkey72]

• + API: improve performance of SetMouseModifier()
• # API: optimize performance of SetMouseModifier() reset of single section to defaults

Thanks for these. Dare I ask, is the scope of the performance improvements in the first entry limited to the single-section reset of the second entry, or are there more general improvements to the speed (esp on Windows/Linux)? I won't have access to a real WIndows system until sometime tomorrow to check...

[Mercado_Negro]

+ ARA: Old projects may not load correctly! If the project contains separate ARA edits to multiple media items that use the same media source

Does this apply to multiple Melodyne instances inserted on different items on the same track?

[schwa]

Originally Posted by Mercado_Negro

Does this apply to multiple Melodyne instances inserted on different items on the same track?

In this build, if you have an old project with ARA edits to different media items that use the same media source, whether the FX is on items or tracks, then they won't all be loaded. For example if you split or copied a media item and applied corrections separately to each item, only one set of edits would be loaded.

[Justin]

Originally Posted by sockmonkey72

Thanks for these. Dare I ask, is the scope of the performance improvements in the first entry limited to the single-section reset of the second entry, or are there more general improvements to the speed (esp on Windows/Linux)? I won't have access to a real WIndows system until sometime tomorrow to check...

it should be faster on all platforms in all modes - the single section optimizations may go to a release before the other optimizations, so they are both listed.

[sockmonkey72]

Originally Posted by Justin

it should be faster on all platforms in all modes - the single section optimizations may go to a release before the other optimizations, so they are both listed.

Great news, I'm looking forward to checking it out. Thanks for taking the time.

[Meo-Ada Mespotine]

Thnx for the IDE and tooltip fixes 🙂

[Mercado_Negro]

Originally Posted by schwa

In this build, if you have an old project with ARA edits to different media items that use the same media source, whether the FX is on items or tracks, then they won't all be loaded. For example if you split or copied a media item and applied corrections separately to each item, only one set of edits would be loaded.

Yes, that's what I thought. Bad news then. I think I've always committed my Melodyne edits on items (apply FX) but only time will tell

[musicbynumbers]

Fantastic about the crossfades.

Please consider when you get round to lengths to have a CC/osc action for that too. Thanks!

[Vagelis]

Originally Posted by sockmonkey72

v6.73+dev0124a - January 24 2023
[*]# ReaReaRea: add dotted and triplet modes
[*]# ReaReaRea: change tempo sync range from 1/128 to whole notes

Awesome, thanks a lot

Originally Posted by sockmonkey72

Great news, I'm looking forward to checking it out. Thanks for taking the time.

Great, looking forward as well.

[Jae.Thomas]

Originally Posted by schwa

In this build, if you have an old project with ARA edits to different media items that use the same media source, whether the FX is on items or tracks, then they won't all be loaded. For example if you split or copied a media item and applied corrections separately to each item, only one set of edits would be loaded.

and there would be no like warning or window telling you this happened, right?

I think the only way I've used melodyne so far is like working over a vocal track that has different takes/splits in it. Not sure if that use scenario would do it.

Various splits over time would reference that one item, however.

[souk21]

Originally Posted by sockmonkey72

[*]+ Tooltips: prevent tooltips from occuring when window is inactive [t=233380]

Thanks! can confirm it's working on OSX

[schwa]

Originally Posted by Jae.Thomas

and there would be no like warning or window telling you this happened, right?

We're working on the backwards compatibility part, but the change is worth the trouble IMO. ARA edits should be much more persistent now.

[Jae.Thomas]

Originally Posted by schwa

We're working on the backwards compatibility part, but the change is worth the trouble IMO. ARA edits should be much more persistent now.

no, this sounds awesome!!!! Don't get me wrong

thank you for continuing to work on ARA

But yeah, maybe even just a warning for users who may have projects that fit the criteria that breaks things.

[Jae.Thomas]

ok so I opened an older project that I've worked on recently.

I went to various places in the file, before and after the split you see. Not even sure why this split is here?!?! Probably injected too much of the pot

but anyway,

I selected all and restored pitch centers and drifts, and there was movement (aka, the blobs moved back to their original position, hence showing they were edited previous)! So that means it retained the edits in my scenario. Again, not 100 percent sure what might fit in this case.

and ofc, if I ever notice something is "off" I can always load in an older version, right? Or does it mess with some other data?

[Kenny Gioia]

# Actions window: add menu item to copy main section keyboard shortcuts to alternate section

Thank you.

I believe this will help those who have changed their keyboard shortcuts (who doesn't?) so that the alternates can start from that point.

[ferropop]

Originally Posted by schwa

In this build, if you have an old project with ARA edits to different media items that use the same media source, whether the FX is on items or tracks, then they won't all be loaded. For example if you split or copied a media item and applied corrections separately to each item, only one set of edits would be loaded.

Thanks for the heads up schwa.

Curious what this sets in motion going forwards?

In the common scenario of Razor-Duplicating the 1st chorus to the 2nd chorus, does this mean if you make changes to the 2nd Chorus they'll be reflected in the 1st (and vice versa)?

[ferropop]

^^i understand the update refers to Previous Projects saved being affected, I'm just wondering if anything functionally changes going forward?

for instance, the behaviour of "pooling" the edits with shared media (what I'm afraid this is) is specifically undesirable in most cases.

For sound design especially (chopping items, Melodyne-stretch manipulations) it would be really bad if you chopped something from the Verse vocal and mangled it in Melodyne for a FX moment, and the original source also getting mangled.

...The way it has been working is perfect - Duplication preserving edits is of course super desirable, and no pooling.

[ferropop]

hooboy...(maybe?)



like if I go about chopping that duplicate in some crazy way (or making an alternate melody!), it's going to completely warp the original take as it's "following" all the edits.

is there some way to retain both behaviours? I'd say this is opting for the less desirable of the two options - while also being retroactively-destructive.

[ferropop]

Super common to duplicate the lead and create a fake harmony -- you now can't because the lead will follow the re-tuning :

[sockmonkey72]

Originally Posted by Justin

it should be faster on all platforms in all modes - the single section optimizations may go to a release before the other optimizations, so they are both listed.

Confirmed that this fixes the issue on my PC, thank you so much!

[bFooz]

Originally Posted by sockmonkey72

+ Notation editor: improve layout when resizing in continuous scroll view [p=2032295]

This seems to be working fine in the continuous view, thanks! Now the maximum number of measures that can be displayed depends on a window width as should be.

The non-continuous view is still problematic though. The max number of horizontal measures is 12 (in 4/4) regardless of the window size.

[tohubohu]

Originally Posted by bFooz

This seems to be working fine in the continuous view, thanks! Now the maximum number of measures that can be displayed depends on a window width as should be.

The non-continuous view is still problematic though. The max number of horizontal measures is 12 (in 4/4) regardless of the window size.

it also depends on the speed at which you resize the window. If, for example, you quickly shrink the window, it will not keep all twelve bars, but will display four.

[bFooz]

Originally Posted by tohubohu

it also depends on the speed at which you resize the window. If, for example, you quickly shrink the window, it will not keep all twelve bars, but will display four.

Yes, I've noticed this as well. Maybe related to this: https://forum.cockos.com/showthread....54#post2036254

[Phazma]

Originally Posted by sockmonkey72

[*]# ReaReaRea: add dotted and triplet modes[*]# ReaReaRea: change tempo sync range from 1/128 to whole notes

Thanks for these! ReaReaRea is getting more and more awesome