Re:Melodyne Crashes - how I envy you other guys who say it works fine...
2011/11/14 09:45:59
(permalink)
I've tried every conceivable alternative setting in Preferences that I thougbt could make a difference. Today I tried disabling my Firewire ports, then using WDM drivers in Sonar instead of ASIO....the lot.
My last DAW ran the old Plugin fine under XP, then I reformatted it to move up to Windows 7 64 bit and I've had this problem ever since.
What was really galling was to spend a lot of money after that on a brand new audio-only PC (spec below), and to find the same issue. When I got the new PC I tried an experiment and installed nothing at all except Sonar and Melodyne. No MS Office, Explorer, printer, zilch. And what do you know - the same problem. Five minutes or so of working with Editor plugin and then freeze, and Sonar crash. The Sonar crash is always so bad I have to cold boot the machine every time it happens.
I've invested in Studio 1 Pro Ver 2 solely to port across a rough mix backing track along with the lead vocal track just to be able to work in a 100% stable environment, porting the bounced Melodyned vocal track back to Sonar afterwards. I found I can also do this with Reaper.
And with both of those I don't even have to change the samples from 128 (Melodyne recommend going to 1024 to use Editor in Sonar.......but that doesn't help anyway).
Melodyne Standalone works fine, but I need a backing track to be able to edit/correct a vocal track in context.
My stuff Intel Sandy Bridge i7 2600 @ 3.4GHz, 4 cores, 8 threads, 16GB RAM.OS & Programs drive: 240GB SSD
Data drives: 1 x 1TB drive RAID mirrored, plus extra 1TB data drive
Windows 10 Home 64 bit
Cakewalk by BandLab 64 bit, Studio One 3, Band In A Box 2016, Ozone 8+ too many other pluginsBandLab page