Hi,
 
I just updated to the latest version of Platinum (Manchester) but that didn't fix Melodyne 4 Studio's sync problem with the scroll bar. My issue is that the scroll bar is about 1 second ahead of the blobs (and sound) when using Mel 4 Studio as either an ARA FX or as a plug-in (where you can do simultaneous multi-track editing, great if it works in sync). Oddly, in the Stand-Alone version, Mel 4 Studio displays perfect synchronization.
 
I also have the older Melodyne Editor 2 which worked perfectly in sync before I downloaded the trial for Studio. I've also tried this on my laptop and the same issues exist so I think it's a Celemony problem.
 
I've had several responses to this problem from Celemony and a call in to Sonar support and they want me to use ASIO drivers, which I do use with my Roland Octa-Capture on my desktop, and I've uninstalled/reinstalled a few times with no improvement in the syncing performance.
 
Is anyone else having similar issues? Does anyone know how to fix it?
 
Thanx, Frederick

I just recently had an email exchange with support at Celemony.  I mentioned the timing problem and he told me that someone was working on it.  I'm going to hold off installing Studio 4 till this get straightened out.
 
Good luck.
 
Paul

As requested by Celemony Support, I sent them a screen capture video showing the sync problem and learned that a new version of Studio was released today. They haven't responded yet but I installed the new version and still have the sync problem. Also, the multitrack doesn't work in ARA, Celemony supoport told me you have to do it as plugins on each track and then "Transfer" the audio like in the old days of Melodyne. Hopefully they get this all worked out as it is a great idea but  it reminds me of the pre-Cakewalk/Celemony partnership when Melodyne seemed to work great about half of the time, and not so much the other half. So close, so close....

Sorry to hear you are having problems with Melodyne. I am using Melodyne Studio 4 in Manchester Platinum, but I am not having any sync problems. Unless others are having the same trouble It could be worth digging a little deeper into trouble-shooting your system rather than waiting for Celemony. Has anyone else confirmed the issue?
 
The multi track editing is working as intended. There is a discussion of its limitations here:
 
http://forum.cakewalk.com/Manchester-not-working-as-advertized-with-Melodyne-Studio-4-m3359138.aspx

Bruce,
 
Thanx for responding. It's good to hear it can work.
 
My system is pretty new. I built it from scratch about a year ago and I just upgraded to a new 1 TB SSD at the beginning of the year and did a fresh install of Windows 10. I have a fast processor (i7) and 16 GB ram, use a Roland Octa-Capture with the newest Windows 10 driver, etc. I even deleted my Cubase light that I had bought to run Waves Tune as it didn't loop in Sonar (no ReWire support) and I liked it's ability to create vibrato from scratch which Melodyne doesn't seem to be able to do. Cubase was deleted because it comes with its' own ASIO driver "generic low latency driver" that was always getting used by Sonar, so I simply deleted it from Program Files (though it can't be found/uninstalled via the normal control panel, Programs section). I suspect that driver may be the culprit and I've read you have to go deep into the registry and find it to delete it, which i haven't attempted yet. I may just do another complete re-installation of Windows 10 and install Sonar and Melodyne Studio 4 as the first program and see if it sync's correctly. I also have lots of other audio/video programs that may be causing the problem, who knows?
 
My Sony VAIO laptop also has an i7 processer and Cubase on it with their driver and I'm seeing the sync problem there as well. So I've spent hours trying to figure this out and these issues should have been resolved by Celemony before they released this version. So close, so close...

i remember the timing problem & the workaround i was told about it: before opening up something in Melodyne, turn off all FX in the project; that seems to "fix" the timing issue

wetdentist
i remember the timing problem & the workaround i was told about it: before opening up something in Melodyne, turn off all FX in the project; that seems to "fix" the timing issue

Have I missed some posts about this problem in Melodyne 4 and Sonar Platinum? I am using projects with many FX and there is no timing issue.

Could be a particular plugin causing it of course. Have you tried a clean project with just an instance of melodyne on a single track Frederick?

Yes, I tried a simple project where I just sung the numbers from one to six, on 1 track with no other FX and the timing was still off. I made a little video of it and sent it to Celemony via DropBox but they haven't responded that they've seen it.
 
In the meantime, I just loaded Melodyne Studio 4 "trial" onto my backup DJ laptop (win10, i5) and have a "Demo" version of an earlier version of Platinum on it and was surprised that the timing was just fine. For the test, I dragged Queen's Bohemian Rhapsody (MP3) onto a track, loaded Studio 4 as a plug-in, transferred the first a-capella 40 seconds of the song, and wow! Studio automatically chose the polyphonic setting, then broke it into the single vocal parts and it played in sync. I was even able to delete some notes to hear just the root melody that seems to be in the key of "G". On this computer, I never installed Cubase and maybe that further points to the Cubase ASIO "generic low latecny driver" as the culprit. It was really nice to be able to break apart the individual vocal parts of Queen's legendary song. Who would-a thunk even a few years ago that this ability would be possible? Amazing.
 
If I reinstall windows and all of my programs on my desktop, that's about a 2 to 3 day task. ugh... but if that is what will make it work, I'll do it because the reward is worth it...

user390096
. Who would-a thunk even a few years ago that this ability would be possible? Amazing.
 
If I reinstall windows and all of my programs on my desktop, that's about a 2 to 3 day task. ugh... but if that is what will make it work, I'll do it because the reward is worth it...

It is pretty awesome isn't it! A full rebuild is a pain - I did my systems a month ago. The rogue asio driver certainly seems to be the consistent factor on the problematic systems. Is sonar actually using the steinberg driver or are you concerned it has somehow messed with sonar and is still causing the delay even though it is inactive? Could you possibly try another type of driver (anything but asio) with Sonar just as a test?

I did go through all of the drivers and a lot of them actually worked OK but no better than the ASIO.
 
I went on the Cubase forums and folks there say the "generic" driver is hidden deep in the registry, so the best I could do safely was simply delete it's folder I found in the Programs file. But, that simple deletion has kept it from occurring in my Sonar list of drivers/devices in the Preferences section - so it is visibly gone but I think it still lives on in my registry as reported on the Cubase forums. I suppose I should go to those forums and ask where exactly it is in the registry and attempt to delete it that way before I do a full reinstall.
 
At any rate, I'm happy to see it work for once, and Bravo to Celemony for inventing this program as it's quite a giant advancement in editing ability. As a singer who likes to double track my vocals and do lots of multi-track background singing, it is a must-have to easily and accurately tighten things up.