Hi, I am using Melodyne Editor - latest version 1.2.1 -
Nuendo Ver5.1 build 651 (32bit)
Win 7 64bit (latest SP1)

using Meldyne Editor in a project, as the usage of the plugin grows (more audio processed) the project save time becomes painfully slow. Currently I have project that has 15 minutes of audio (1 track of Melodyne processing a vocal) and the project save time is now nearly 2 minutes!!!! This is not a background save either - the save holds up all activity - ie my DAW goes busy for the whole 'save time' period.

The project file size is only 36Mb

It would appear that Melodyne is causing this huge delay as there is no disk activity for a large period of the save time.

Removing the Melodyne plugin from the project (also takes about 40 seconds to remove the instance) after which the project then takes only around 1 second to save - so it has to be something to do with Melodyne!

This is a real PITA as it greatly disturbs my work flow (and my clients aren't too happy either!)

Please can you look into this ASAP.

Many thanks,

Adam Vanryne.

Hello Adam,

is there a reason why you are running Nuendo in 32-bit on a 64-bit Windows system? Any chance you could try the 64-bit Nuendo with the 64-bit Melodyne? This should certainly decrease saving time due to an improved handling of your system's memory. How much RAM have you got, by the way?

Moreover, the crashes which you described in your other thread might also be related to a lack of memory. Please check if the crashes are gone with the 64-bit version.

If you can't switch to 64-bit, you might benefit from certain strategies to reduce the RAM load. Please see our FAQ > Melodyne and my computer > Can Melodyne open files of any size or is this determined by the amount of available RAM? Do the tips given there help?

Hi Claudio,
Thank you for your reply.

I'm working in 32 bit at the moment as I'm using UAD plugins heavily and bitbridge and jbridge are just not stable enought at the moment in 64bit.

That said, I have a very new DAW system, i7 Extreme (6core) with 12Gb of Corsair ultrafast triple channel memory (nothing is overclocked), Asus P6X58D Premium motherboard.

It's a very fast system with 3x Crucial 'Real' SSD's for OS and audio/video.

That is why it astounds me that a project should take nearly 2 minutes to save out.

The project I'm currently working on is using around 4.5 Gb of RAM so I have plenty of space remaining.

I've been monitoring system activity during a save, and it appears that there is no disc activity for a good minute, also the CPU isn't even showing a slight hit in useage. It's almost Nuendo is waiting for a response from something (Melodyne?) and not getting it for a long time.

I think there needs to be a bit of dialogue with Steinberg developers as I'm hearing similar problems from other Nuendo users.

It's a serious delay in work flow, as I have autosave set to 10 minute intervals, which means I'm loosing around 10 minutes an hour in save time, but it's the interruption/disruption to workflow that's really bugging me.

Hope you can help.

Hey Adam,

depending on what kind of material you save with Melodyne, the file size can grow drastically. On a 32-bit system, saving such a large file will take much longer than on a 64-bit system. Even if you have plenty of RAM, a 32-bit system can't benefit from it as much as a 64-bit system can. Please see our 64-bit video for more details.

Furthermore, a project file of 36 MB size seems to be huge for Nuendo. What else is going on in that project? What if you start with an empty Nuendo project, insert Melodyne and transfer one audio file only. Does it also crash? If it doesn't, the issue is clearly related to memory.

I'll pass this on to our R&D guys. Meanwhile, could you run a test for us with Nuendo in 64-bit and see if it makes a difference? Have you also tried the RAM saving tips I suggested above? Another thing you could try is to reassign the storage location for the Melodyne audio cache in the Melodyne preferences to a different folder or partition.