Unload Melodyne

[gabo]

I have a very long "live" recording, about 3 hours long. I loaded melodyne onto a track to fix one small issue, after modifying it with melodyne I bounced the track (ctrl-B). So Melodyne is no longer used. However, when I exit Studio Pro of when I open the file, it loads melodyne and due to the length of the file, it takes forever.

In previous versions, there was an icon in the console view (don't recall which one) where you could see that melodyne was loaded and you could remove it. However I no longer can find that in the latest version. Is there still a way to completely remove melodyne from my session?

 

[madFloyd]

If you click on the audio event and have the inspector open (F4), you should see a 'Render' option. Instead of using that, expand the event to see the plugins associated with the event. You should see Melodyne and you can then remove it.

 

[gabo]

If you click on the audio event and have the inspector open (F4), you should see a 'Render' option. Instead of using that, expand the event to see the plugins associated with the event. You should see Melodyne and you can then remove it.

I didn't see a "render" on any of the tracks in the inspector. On a hunch, I inserted melodyne again, and then saw the render and the instance of melodyne. For what you're talking about, the more common way to remove an actual used instance of melodyne is to just right click the event and select "remove melodyne."

That's not the problem. The track has already been rendered, that happens when you bounce the track with a ctrl-b. So there is no event FX inserted on the track.

The problem is that the instance of melodyne, even though the track has been rendered and it's no longer on the track, is still loaded in the session. I have never understood why this happens. But in the older versions of Studio Pro, there was a window you could open in the console that would show it there. Similar to the instrument rack that's down there. Maybe melodyne was previously included in the instrument rack, I'm not sure as I no longer have any older version loaded on my machine. But there was a way to remove it there.

UPDATE: It's very frustrating, melodyne doesn't even show up in the performance monitor when I show all devices. Yet when I open the file, it starts loading melodyne, 1%... 5%.... hangs at 45% for a while.. eventually loads and works fine. I put a stopwatch on it, it takes 8 minutes 28 seconds to load the file!!

 

[tpittman]

I have a very long "live" recording, about 3 hours long. I loaded melodyne onto a track to fix one small issue

I wonder if you loaded melodyne on a 3 hr track, if that could be an issue? I only do small
areas at a time these days. Maybe try inserting melodyne around immediate surrounding
area(s) and see if changes the way melodyne is behaving. It may be worth a try...

 

[gabo]

I wonder if you loaded melodyne on a 3 hr track, if that could be an issue? I only do small
areas at a time these days. Maybe try inserting melodyne around immediate surrounding
area(s) and see if changes the way melodyne is behaving. It may be worth a try...

Thanks. Yea I tried that. Didn't work due to the fact that melodyne isn't really loaded on anything at this point. Except it's attached to the file some how and just creates a problem when opening. Oh well, I'll be done with this thing soon anyway. I can just open it, go get coffee, and come back in 9 minutes!

 

[tpittman]

Thanks. Yea I tried that. Didn't work due to the fact that melodyne isn't really loaded on anything at this point. Except it's attached to the file some how and just creates a problem when opening. Oh well, I'll be done with this thing soon anyway. I can just open it, go get coffee, and come back in 9 minutes!

I'm curious now. Is this happening only on this file? The reason I ask is because
some years ago I had big issues with melodyne. Long story short melodyne had to
be removed completely from my system (presonus support was great) then
re-installed. Not trying to say what's wrong of course, just sayin' weird stuff happens.
Hope ya get it sorted

 

[SwitchBack]

Two things to try:

1. Open Melodyne itself (it should have installed a launcher for standalone use) and see if you can clear recent items or something like that.
2. Rename that 3hr audio file before opening the song. It will flag an error when you open the song next but Melodyne won't be able to find it either and, more importantly, it may give a clue on how to stop Melodyne opening when the file is renamed back.

For next time don't use Melodyne on events from very long sessions as it will load the entire underlying file. Bounce the track first to create a new trimmed file

 

[madFloyd]

What about opening the Performance Monitor, ensuring Show Devices is selected, then right clicking on Melodyne and removing it that way?

 

[gabo]

What about opening the Performance Monitor, ensuring Show Devices is selected, then right clicking on Melodyne and removing it that way?

As per my previous note... I did that, except melodyne is not listed anywhere in the list of devices. It actually shouldn't be because, also as I've previously stated, it's not loaded on any track.

 

[gabo]

I'm curious now. Is this happening only on this file? The reason I ask is because
some years ago I had big issues with melodyne. Long story short melodyne had to
be removed completely from my system (presonus support was great) then
re-installed. Not trying to say what's wrong of course, just sayin' weird stuff happens.
Hope ya get it sorted

it happens on very song. It's just that it's not a problem on most songs as they are generally <5 min long, so it loads relatively quickly.

 

[madFloyd]

it happens on very song. It's just that it's not a problem on most songs as they are generally <5 min long, so it loads relatively quickly.

I feel I've experienced this in the past, when my PC was getting a little long in the tooth and songs opened slowly. I would be annoyed at melodyne when I felt I had removed it; I just don't remember the details.

 

[gabo]

Two things to try:

1. Open Melodyne itself (it should have installed a launcher for standalone use) and see if you can clear recent items or something like that.
2. Rename that 3hr audio file before opening the song. It will flag an error when you open the song next but Melodyne won't be able to find it either and, more importantly, it may give a clue on how to stop Melodyne opening when the file is renamed back.

For next time don't use Melodyne on events from very long sessions as it will load the entire underlying file. Bounce the track first to create a new trimmed file

Nothing in Melodyne, so standalone has no reference to it.

Yes, it's easy to say "bounce the track first" to create a trimmed file. But that comes with it's own nuanced issues.

 

[gabo]

I feel I've experienced this in the past, when my PC was getting a little long in the tooth and songs opened slowly. I would be annoyed at melodyne when I felt I had removed it; I just don't remember the details.

Yes, that's why I know there was a way to unload it, but I'm not sure what version that was, maybe 6? Since then I've had top performing computers and didn't really need it... until now. I thought it was just a question that someone would answer definitively very quickly, as I figured they just moved it some where. But apparently it's not that simple.

Oh well, I'll survive.