noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
[SOLVED] Melodyne Studio4 - not backwards compatible with Melodyne Editor2 in Sonar Plat ?
Just upgraded my Melodyne Editor 2 to Melodyne Studio 4 . . . but now when I open my Sonar Platinum projects, I get an immediate Sonar crash on any project containing instances of Melodyne VST3 region FX. If I launch these projects in safe mode without the Melodyne plugin, they open just fine. Hmmm, so what's the deal with this ? I can say that my Melodyne 4 Studio install seems to load as a new VST3 insertion into Sonar, that all works, but it is not backwards compatible with any projects containing the older version of Melodyne Editor 2. Anyone else have this issue that has done the upgrade, or do we need to wait for the Manchester update for this to work ?
post edited by noynekker - 2016/01/24 15:52:28
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
MacFurse
Max Output Level: -84 dBFS
- Total Posts : 324
- Joined: 2013/11/10 07:25:54
- Location: Newcastle - Australia
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 00:45:03
(permalink)
I find leaving any instances of region FX in a project causes me issues, so I try to make sure that I leave none behind, bouncing to clips as I go. Having said that, I will watch this one with interest, because I'm about to the same and upgradge from Editor 2. I'm hoping that Studio 4 will give me the option to leave multiple instances within a project while I keep working, without causes the crash issues of Editor 2.
Glad you brought this up.
Platinum. i7 4771 3.5ghz. ECU H87 mobo with 3 monitor support. 16gb Ripjaws 1600mhz. Focusrite 18i20. 2 x 250gb Samsung EVO SSD's OP/Programs. 2x1TB Seagate Baracuda sata3 data drives. 200gb sata2 bootable drive for online and downloading only. Seagate 2tb USB 3.0 backup drive. 2x27in monitors. Rode K2 valve mic. Sontronics STC-1 pair. Studio Projects B1 condenser. SM58B. SM57B. Presonus Eureka Preamp.
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 01:34:29
(permalink)
Yes, I've never had any issues leaving the Region FX unfrozen or unbounced in the past. I usually wait until the very end of the project phase to do this.
Also, the Melodyne Studio 4 installer automatically removes Melodyne Editor 2, so this may be the root of the problem. Seems they don't want the two to co-exist for some reason ?
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
mettelus
Max Output Level: -22 dBFS
- Total Posts : 5321
- Joined: 2005/08/05 03:19:25
- Location: Maryland, USA
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 01:59:51
(permalink)
Melodyne edits are saved in the cwp, so the backwards compatible issue is a valid one. It seems 4 does overwrite 2, but I seem to recall someone saying they had both.
I still have outstanding emails to Celemony asking specifics on several items, including this one. I almost updated Melodyne on "good faith" even though the demo install went belly up, but have seen enough comments I will not get it without running it first.
Celemony's forum went offline when 4 was released as well, so information is highly scarce and subjective.
ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 05:08:12
(permalink)
☄ Helpfulby noynekker 2016/01/24 12:21:32
When I opened a project with Melodyne 4 Studio and edited a region created with Melodyne 2 Editor, I got a pop-up saying that if I saved the region (with Melodyne 4) I could no longer open the region with Melodyne 2. Not really an issue since Melodyne 4 upgrade replaces Melodyne 2.
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
PeterMc
Max Output Level: -80 dBFS
- Total Posts : 504
- Joined: 2003/11/12 23:46:34
- Location: Tasmania
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 06:00:40
(permalink)
i5 6500, H170M, Intel HD 530, 16GB, Focusrite Scarlett 8i6, Win 10 Pro (1803) (64 bit), Cakewalk by Bandlab
|
mudgel
Max Output Level: 0 dBFS
- Total Posts : 12010
- Joined: 2004/08/13 00:56:05
- Location: Linton Victoria (Near Ballarat)
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 08:27:46
(permalink)
Celemony mention the incompatibility on their website. You can run the 2 versions side by side. At least that's what I understood.
Mike V. (MUDGEL) STUDIO: Win 10 Pro x64, SPlat & CbB x64, PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz. Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2. Monitors: Adam A7X, JBL 10” Sub. Audio I/O & DSP Server: DIGIGRID IOS & IOX. Screen: Raven MTi + 43" HD 4K TV Monitor. Keyboard Controller: Native Instruments Komplete Kontrol S88.
|
Fred Holmes
Max Output Level: -83 dBFS
- Total Posts : 376
- Joined: 2003/11/05 17:17:09
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 10:36:28
(permalink)
AFAIK Melodyne Studio 4 does overwrite and replace editor 2 BUT Melodyne Studio 3 if you have it will run as a stand alone and coexist with Studio 4
Fred
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 11:24:12
(permalink)
microapp
When I opened a project with Melodyne 4 Studio and edited a region created with Melodyne 2 Editor, I got a pop-up saying that if I saved the region (with Melodyne 4) I could no longer open the region with Melodyne 2. Not really an issue since Melodyne 4 upgrade replaces Melodyne 2.
Well, that's promising . . . so you are saying you can open projects containing Editor 2 clips, on my system it's causing Sonar to crash right at the opening these projects.
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 11:30:24
(permalink)
mudgel
Celemony mention the incompatibility on their website. You can run the 2 versions side by side. At least that's what I understood.
Hi Mike, I can't locate this on the Celemony website, and if I re-install Editor 2 won't it just overwrite the Studio 4 VST3 file located in C:\Program Files\Common Files\VST3\Celemony\Melodyne\Melodyne.vst3 ? What I do see on the Celemony website is a chart comparing their various Melodyne editions, and at the bottom of that chart: "Intercompatibility – Open and edit projects created by other editions" . . . so this should work, right ?
post edited by noynekker - 2016/01/24 11:54:47
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 14:29:37
(permalink)
noynekker
microapp
When I opened a project with Melodyne 4 Studio and edited a region created with Melodyne 2 Editor, I got a pop-up saying that if I saved the region (with Melodyne 4) I could no longer open the region with Melodyne 2. Not really an issue since Melodyne 4 upgrade replaces Melodyne 2.
Well, that's promising . . . so you are saying you can open projects containing Editor 2 clips, on my system it's causing Sonar to crash right at the opening these projects.
It did not crash. I could open and edit in Melodyne 4. IIRC, the pop-up warning occurred once I made a change in the Melodyne region. Can you create a new project or edit a project not containing a Melodyne 2 region then edit that with Melodyne 4?
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
rontarrant
Max Output Level: -78 dBFS
- Total Posts : 643
- Joined: 2010/06/21 06:26:09
- Location: Ottawa, Ontario
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 14:48:22
(permalink)
noynekker
Hi Mike, I can't locate this on the Celemony website
I tried to go on their forum just now and they've taken it down. Permanently, apparently. They suggest Facebook or one of their other social feeds for questions, etc.
-Ron T. ---------------------------------------------------------- MSI GE72 2QF-247US, 12 gb, Focusrite 6i6, AT-2020 ---------------------------------------------------------- Windows 10 x64, Sonar Platinum
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/24 15:38:00
(permalink)
Okay, I think I solved my Sonar crashing issue ! . . . thank you to "microapp" who reported that there was a pop up message appearing when editing the Region FX of Melodyne Editor 2 clips using Melodyne Studio 4. This made me realize it is possible, so I had a closer look at my own system and discovered that my Novation Impulse control surface software interface was to blame for this crashing.
Novation uses the Automap software as a VST wrapper, so when the plugin scan happens at Sonar start up it renames the VST3 file. In this case it renamed "Melodyne.vst3" to "!Melodyne (Automap).vst3"
Apparently Melodyne Studio 4 is not compatible with Automap, or at least it doesn't like the renaming of its plugin file name . . . as soon as I removed "!Melodyne (Automap).vst3" from the VST plugin scan path . . . it all works as expected, and I get the pop up message when trying to edit Melodyne Editor 2 clips, saying "warning - - there's no turning back" (basically saying once saved, you can no longer open the Region FX with Melodyne 2)
Thanks to everyone for your inputs. Case dismissed.
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
jassbass
Max Output Level: -90 dBFS
- Total Posts : 6
- Joined: 2015/02/10 18:14:47
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/26 03:17:18
(permalink)
Open Sonar in safe mode and it won't crash.
|
drummaman
Max Output Level: -76 dBFS
- Total Posts : 738
- Joined: 2008/05/30 17:46:53
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/31 20:19:07
(permalink)
FWIW -
When clicking through the upgrade pages at Celemony, on the download
page was a rather convoluted statement suggesting that it's best to do
a clean install...
Which would do away with any conflicts with earlier versions, is my guess.
Sonar Platinum (x64) on Windows 10 Pro (64-bit) running on ADK Pro Audio i7 (12-core), 16GB RAM, 500GB SSD(OS), (2) 2TB drives/(1) 1TB drive for storage, (1) WD Raptor 1TB Audio Drive, (1) UAD-2 OCTO, (2) UAD-2 QUAD, Lynx Aurora 16/AES16
|
dhodgson
Max Output Level: -90 dBFS
- Total Posts : 25
- Joined: 2003/11/26 05:10:14
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/31 22:25:37
(permalink)
Same problem here - opening a project containing Melodyne Editor 2 RFX regions reliably crashes on open. Running on an iLok I had to relinquish my Melodyne Editor 2 key to upgrade to Melodyne 4 - which was a mistake. Downgrading back to Melodyne 2 lets me render at least, but not edit (no key.)
|
Kamikaze
Max Output Level: -45 dBFS
- Total Posts : 3013
- Joined: 2015/01/15 21:38:59
- Location: Da Nang, Vietnam
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/01/31 23:08:32
(permalink)
I'm getting crashes with a project that contains a Melodyne Studio 4 (not 2)region effect, that wasn't bounced. So seems an eliment of it just being a region effect not a mix of creating in version 2 and opening with 4.
It's no biggie, I was experimenting, so nothing I wanted to keep
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/02/01 00:45:58
(permalink)
Since I solved the issue with Melodyne on my system, I've been using Melodyne Studio 4 a lot inside Sonar Platinum, and it's been pretty solid. Though, one issue I've found is with one older project, where I had many V-Vocal and Melodyne Editor 2 clips . . . when trying to edit further with Melodyne Studio 4 . . . bit of a crashfest . . . until I found that overlapping clips seem to be a problem. As long as I "clean up" the clips, so they are not touching, everything seems to work well. Just thought I would mention this, since apparently there are many having problems.
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/02/01 00:49:52
(permalink)
jassbass
Open Sonar in safe mode and it won't crash.
Yes, if I launched in safe mode, and don't load the Melodyne plugins, there is no crashing . . . except, then I won't have Melodyne actually working, which is kinda' the whole point of this thread.
post edited by noynekker - 2016/02/01 01:04:14
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
FittingRoomStudio
Max Output Level: -90 dBFS
- Total Posts : 2
- Joined: 2014/11/21 03:07:16
- Status: offline
Re: Melodyne Studio 4 - not backwards compatible with Melodyne Editor 2 in Sonar Platinum
2016/04/14 17:30:00
(permalink)
I agree with everyone and everything :) How can you put out an "upgrade", charge me $99 (for upgrading to Editor 4) and not thoroughly test it to confirm backwards compatibility let alone the fact that it doesn't work as a region F/X even on a fresh project??? Lesson learned about "upgrading", or in this case, "downgrading" too early in the rev.
|