LUNA lag when working in Melodyne

[jnTracks]

When working in Melodyne on a track almost every click --an edit, or just a selection change-- there's this lag for as much as a second before the whole DAW and melodyne catch up.
First I suppose I should make sure this is happening to everyone and not just me. It's worse with more full mix sessions, but even blank sessions have some lag.
Is it just me?

I have presumed this was an artifact of how Luna is "always saved" with it's active database savefile system. (or however I should refer to it)
I'm thinking that because the Luna project is always saved, every time I click Melodyne also updates this save file, and that's where the lag is coming from. From experience, I get the same lag in other DAWs when I do the CMD+S while working in Melodyne.

So how are we dealing with this? It's a real headache and slows me down a ton in Melodyne. UA must be aware of this, right? Is some fix in the works?
I figured if I'm right about what's causing it then it would be something that development is working around, but it's been months and months since I've been using Luna and I waited a long time... Are other Melodyne users just dealing with it, or is there some workaround?
(or am I just having a personal bug that I can fix?)

Thanks, everybody!

 

[UniversalAudio]

Yeah, I see no difference when using Melodyne here.

 

[ScottyC]

Lately I’ve been exporting files and tuning them in Melodyne as a standalone app. Pretty great that you can import all of your BGVS into a single instance of the app, tune them individually and then be able check them against each other before bringing them back into LUNA. Saves loads of processing vs having multiple instances of the plugin running in a session.

 

[jnTracks]

Yeah, I see no difference when using Melodyne here.

Oh so I'm experiencing a bug? Actually sort of good news maybe.
But what could I be doing wrong?

 

[UniversalAudio]

Oh so I'm experiencing a bug? Actually sort of good news maybe.
But what could I be doing wrong?

Bugs are reproducible. Does it do it to all sessions?

Feel free to open a ticket with Support and include the session.

Post the # here and I will monitor and test it here.

 

[jnTracks]

yes, it's always happened every time I used melodyne in Luna. That's why I always presumed it was a side effect of Luna being "always saved"
I'll get a ticket going....

Actually, I just opened up the project I was working on from yesterday, unfroze one of my melodyne instances, and started dragging notes around and they're moving freely with no lag.

Now I'm thinking that there's something about the way I track the audio in there and then work right away. I did all my tuning and never closed and reopened the project.

So what I did (and what I usually do) is put instances of melodyne on the first slot of each track that needs it, open them all and put them into transfer, and play the song back.
Then I close all but one and get to tuning, work my way through them, bounce around a little, until done.

Maybe it's transferring them all at once like that causes some problem? I guess Next time I can try to do this and just close and reopen the project, maybe fully reboot luna, and see if that gets the performance to be normal. All that would still be faster than working through the lag that I figured I didn't have a choice about.

 

[UniversalAudio]

yes, it's always happened every time I used melodyne in Luna. That's why I always presumed it was a side effect of Luna being "always saved"
I'll get a ticket going....

Actually, I just opened up the project I was working on from yesterday, unfroze one of my melodyne instances, and started dragging notes around and they're moving freely with no lag.

Now I'm thinking that there's something about the way I track the audio in there and then work right away. I did all my tuning and never closed and reopened the project.

So what I did (and what I usually do) is put instances of melodyne on the first slot of each track that needs it, open them all and put them into transfer, and play the song back.
Then I close all but one and get to tuning, work my way through them, bounce around a little, until done.

Maybe it's transferring them all at once like that causes some problem? I guess Next time I can try to do this and just close and reopen the project, maybe fully reboot luna, and see if that gets the performance to be normal. All that would still be faster than working through the lag that I figured I didn't have a choice about.

Sounds like a plan on on fronts. Keep us posted.

 

[wiremic]

When working in Melodyne on a track almost every click --an edit, or just a selection change-- there's this lag for as much as a second before the whole DAW and melodyne catch up.
First I suppose I should make sure this is happening to everyone and not just me. It's worse with more full mix sessions, but even blank sessions have some lag.
Is it just me?

I have presumed this was an artifact of how Luna is "always saved" with it's active database savefile system. (or however I should refer to it)
I'm thinking that because the Luna project is always saved, every time I click Melodyne also updates this save file, and that's where the lag is coming from. From experience, I get the same lag in other DAWs when I do the CMD+S while working in Melodyne.

So how are we dealing with this? It's a real headache and slows me down a ton in Melodyne. UA must be aware of this, right? Is some fix in the works?
I figured if I'm right about what's causing it then it would be something that development is working around, but it's been months and months since I've been using Luna and I waited a long time... Are other Melodyne users just dealing with it, or is there some workaround?
(or am I just having a personal bug that I can fix?)

Thanks, everybody!

I am experiencing the same issue. It never used to work this horribly, and getting to the point of utter aggravation. I have put in a bug report. I see this thread is a few weeks old. It seems to be getting worse for me. The pin wheel of death happens with almost every move in Melodyne, when in the past, it has not. Drastically slows down workflow. UA? Drew? Can someone please look into this? I will be happy to assist with any information necessary. Anyone? I have attempted to attach a screen grab but can't for some reason. It isn't even that large a file. Here's a link to see it: