v5.93pre4 - July 1 2018 - Page 2

bogo · 07-04-2018, 10:14 AM

Quote:

Originally Posted by Justin

Yeah that would be nice...

Yes please.

schwa · 07-05-2018, 10:35 AM

Quote:

Originally Posted by Mercado_Negro

Since REAPER now doesn't store any data from Melodyne in its undo history the use of Ctrl+Z to revert a change in Melodyne doesn't work as expected. We have to use the menu inside Melodyne to undo/redo. This is a big problem and I understand it must hard to solve but I hope you'll find a solution because working on something for a while and hitting Ctrl+Z to undo something you just did (just because you're used to that command... I bet most people just hit it without even thinking about it) and all of a sudden you find yourself tuning everything again from scratch is madness

[EDIT] I must say that now Melodyne works so fast that it is a breeze to use. That trick of not storing any data really did it but now we face that other problem

Melodyne is working on a major overhaul of their API with respect to handling undo/redo, for exactly this reason. That is probably months away from being done on their side, and then there would be work on our side to integrate it.

Until then, it may be the best we can do to just have an option for whether or not to include Melodyne in REAPER's undo history.

vanhaze · 07-05-2018, 11:27 AM

Until then, it may be the best we can do to just have an option for whether or not to include Melodyne in REAPER's undo history.

Yes, Please !

Mercado_Negro · 07-06-2018, 04:04 AM

Quote:

Originally Posted by schwa

Melodyne is working on a major overhaul of their API with respect to handling undo/redo, for exactly this reason. That is probably months away from being done on their side, and then there would be work on our side to integrate it.

Until then, it may be the best we can do to just have an option for whether or not to include Melodyne in REAPER's undo history.

That option wouldn't make sense because having it enabled would just slow down editing in Melodyne. I think it would be better to have Melodyne catch all keyboard input by default for now.

EvilDragon · 07-06-2018, 05:13 AM

Better yet, allow any plugin to have all keyboard input sent to them by default in FX browser's right-click context menu when you right-click a plugin. That'd be more consistent

deeb · 07-06-2018, 04:03 PM

Quote:

Originally Posted by EvilDragon

Better yet, allow any plugin to have all keyboard input sent to them by default in FX browser's right-click context menu when you right-click a plugin. That'd be more consistent

This should bé per plugin? Plugins that i want input sent are exceptions

EvilDragon · 07-06-2018, 11:09 PM

Yes, which is why we should be able to set which ones are the exceptions ourselves. Just like with all the other per-plugin options that we already have.

mschnell · 07-07-2018, 03:52 AM

Talking about Melody in this episode of pre-releases that much, a question of somebody who does not have any experience with Melodyne and does not (yet) own a license for same due to no need for the audio-editing Melodyne is mostly used for.

I once read that Melody is a great tool for creating tempo maps on non-click-enabled musical content.

Does the ARA2 integration of Melodyne provide an easy way to create tempo-maps for multi-track recordings done in Reaper (e.g. using the drum tracks as a timing master source) ? Did anybody test this ?

Thanks a lot,
-Michael

EvilDragon · 07-07-2018, 04:39 AM

Yes, you can import tempo map that Melodyne detects into a Reaper project.

mschnell · 07-07-2018, 06:56 AM

I read about this possibility already a long time ago, but have no info how this is done (did not do a decent research as I don't have Melodyne).

But with Melodyne as a plugin in Reaper, it should be automatic, or just a single action, to transfer the tempo map from Melodyne to the Reaper project hat hosts it.

-Michael

EvilDragon · 07-07-2018, 08:44 AM

There's an option for importing tempo map if you click the "+" button in Reaper's preset header, somewhere in a submenu, IIRC. Can't find the post now. But only if you have Melodyne 4.2 beta that uses ARA2.

mschnell · 07-07-2018, 03:17 PM

Quote:

Originally Posted by EvilDragon

But only if you have Melodyne 4.2 beta that uses ARA2.

Obviously

Thanks,
-Michael

semiquaver · 07-07-2018, 08:53 PM

Inserting Melodyne Edtor 4.1 VST3 I'm not seeing ARA - plugin displays the transfer button - am I doing something wrong? High Sierra. First time trying ARA. "use ARA for VST3 plugins ..." is checked

EvilDragon · 07-08-2018, 01:16 AM

4.1 still uses ARA1. Reaper only supports ARA2, and Melodyne 4.2 is still in beta.

semiquaver · 07-08-2018, 08:50 AM

thanks ED - that explains it... grrrr...