• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Undo not affecting Melodyne but main program after "Cmd+M"

Rambler

Member
Dear S1/SP community!

This is my first post here. I am working on a project right now (SO7 and SP8 is the same) where I need to do lots of Take Comping and pitch correction with Melodyne.

My workflow is to do the comp and then - if I need to correct the intonation - select a clip and press "CMD+M". Then I do my edits in Melodyne.

Now heres the problem: Very often, after pressing CMD+M, the undo/redo commands (CMD+Z, CMD+SHIFT+Z) are not being applied to Melodyne but rather to the main program - even though the Melodyne window is in focus and the main program is in the background. Instead CMD+Z reverts the last step in the main program which in this case was CMD+M, so Melodyne is being removed from the clip again which is very annoying.

Unfortunately this behavior is a bit unpredictable. Sometimes it works as it should and CMD+Z is being applied to the Melodyne window (as it should), other times it doesn't. In all cases the Melodyne window is in focus, but in the cases where the problem arises the focus does not seem to be recognized internally.

The workaround: focusing the SP main window again by clicking on it, and then focusing Melodyne again. Then the undo actions are being applied to Melodyne.

Doing this dozens of times per day and always experiencing the same problem is quite annoying.

I wanted to ask if others can confirm this behavior and if so, if the problem could be reported to Fender/Presonus.

For me the problem arises in SP8 and SO7 just the same. It only seems to occur after a take comp. If I didn't do a comp and pressing CMD+M on any other event, is seems to work as it should.
 
I have experienced exactly this behavior in Melodyne and my other ARA plugin (SpectraLayers) in whatever DAW or ARA host I have used them in for long enough (years) now that I have broken my habit of using the Undo shortcut when using them and am forcing myself to us the Edit - Undo command in the plugin's toolbar menu.
So it seems pretty systemic.
 
I have experienced exactly this behavior in Melodyne and my other ARA plugin (SpectraLayers) in whatever DAW or ARA host I have used them in for long enough (years) now that I have broken my habit of using the Undo shortcut when using them and am forcing myself to us the Edit - Undo command in the plugin's toolbar menu.
So it seems pretty systemic.
Interesting. So for you this happens independently of the DAW and ARA plugin?

I have Reaper as my second DAW but never experienced this problem there.
 
Interesting. So for you this happens independently of the DAW and ARA plugin?

I have Reaper as my second DAW but never experienced this problem there.
Well.... NOW I have to say that this had been the default behavior that I had come to take for granted, but testing just now with this latest Fender Studio Pro 8, both with Melodyne (for me, Studio version 5) and SpectraLayers (version 11), I find it to be gone. In other words, using the Undo shortcut works as desired within both plugins. However, a quick check back in Cakewalk (latest version, now Sonar) where I had also experienced the problem that you are having, and it is only in SpectraLayers that this unwanted behavior (Undo shortcut removing the plugin and whatever time consuming work you had just done) is happening. Melodyne behaves as desired. So, for me, something has changed in the latest versions.
It is likely, I guess, that the recent updates fixed it since I last had chance to experience the problem. Sorry. That doesn't help you.
But in short, as long as Melodyne has the focus when using the Undo shortcut, it is working as desired for me now in FSP
 
Well.... NOW I have to say that this had been the default behavior that I had come to take for granted, but testing just now with this latest Fender Studio Pro 8, both with Melodyne (for me, Studio version 5) and SpectraLayers (version 11), I find it to be gone. In other words, using the Undo shortcut works as desired within both plugins. However, a quick check back in Cakewalk (latest version, now Sonar) where I had also experienced the problem that you are having, and it is only in SpectraLayers that this unwanted behavior (Undo shortcut removing the plugin and whatever time consuming work you had just done) is happening. Melodyne behaves as desired. So, for me, something has changed in the latest versions.
It is likely, I guess, that the recent updates fixed it since I last had chance to experience the problem. Sorry. That doesn't help you.
But in short, as long as Melodyne has the focus when using the Undo shortcut, it is working as desired for me now in FSP
Did you do it after comping? Somehow the problem mostly occurs when I comp and then press cmd+m. And also not every time but like every second time.
 
Did you do it after comping? Somehow the problem mostly occurs when I comp and then press cmd+m. And also not every time but like every second time.
Haven't tried after comping. But when I had the problem it was consistent whenever I used an Undo shortcut. I could have performed 1 or 50 editing operations in the ARA plugin over however much editing time and, wanting to just undo the last operation, pressing ctrl/cmd+Z would simply undo everything I had just done by virtue of just removing the plugin. And Redo simply added it back fresh with all the edits gone.
 
Haven't tried after comping. But when I had the problem it was consistent whenever I used an Undo shortcut. I could have performed 1 or 50 editing operations in the ARA plugin over however much editing time and, wanting to just undo the last operation, pressing ctrl/cmd+Z would simply undo everything I had just done by virtue of just removing the plugin. And Redo simply added it back fresh with all the edits gone.
Interesting! Undo affecting Melodyne is definitely the default state now, however it often does not work as intended.
 
Since this had been confirmed by others - any chance of reporting this to Fender? (If I have understood it right, Ari and Lukas are involved with / part of Fender)
 
Easy to miss: Cmd-M after selecting an event opens the Melodyne window (and gives the Melodyne app access to the event's audio file) but it doesn't select the Melodyne window/app yet. Hitting Cmd-Z now is an undo in S1/SP, not in Melodyne. After selecting the Melodyne window (clicking it or using its tools) it becomes the app in focus an Cmd-Z becomes an undo in Melodyne. So make double sure which app is in focus before using Cmd-Z/Shift-Cmd-Z. :)
 
Easy to miss: Cmd-M after selecting an event opens the Melodyne window (and gives the Melodyne app access to the event's audio file) but it doesn't select the Melodyne window/app yet. Hitting Cmd-Z now is an undo in S1/SP, not in Melodyne. After selecting the Melodyne window (clicking it or using its tools) it becomes the app in focus an Cmd-Z becomes an undo in Melodyne. So make double sure which app is in focus before using Cmd-Z/Shift-Cmd-Z. :)
I do fully understand that the Melodyne window needs to be in focus for CMD+Z to have an effect but this is not the issue here!

As I said - the Melodyne Window IS in focus after pressing CMD+M. The problem is that it is not being recognized internally as being in focus. For it to be recognized as being in focus you have to get the main window in focus again and then get Meldoyne in focus again.

Also this behavior is not always appearing consistently
 
Back
Top