Melodyne issue

Author
Ozz
Max Output Level: -84 dBFS
  • Total Posts : 332
  • Joined: 2010/01/27 02:41:40
  • Location: Upstate NY
  • Status: offline
2014/07/05 15:25:25 (permalink)

Melodyne issue

I'm running X3 Producer with the upgrade to Melodyne Editor.
 
This has only happened a couple of times on a couple of different projects....but, I'll attempt to adjust the pitch of one "blob", which I do....then I go to adjust another one...and the first one pops back to where it was.
 
So..its like I can only adjust ONE "blob".  This is NOT a typical occurrence, and in some cases it's on a project I've been working on with no issue previously.
 
I've tried leaving and re-entering the project, restarting Sonar, restarting the computer, etc...
 
I'm thinking it's probably a setting that somehow got changed or "borked", but not sure which one.
 
Any ideas?
 
Thanks!

Sonar Platinum, Win 10 Pro 64, Intel i7 4770K, 16GB DDR3 1600, 1 x 250GB SSD, 2 x 2TB SATA, Roland OctaCapture, Roland XP-30 (Controller only), Shure KSM-44, Rode NT-1, Shure SM57, Numerous Guitar Amp sims, Komplete 6/7, Alchemy, Custom built guitar, Carvin Amplifiers.
#1

3 Replies Related Threads

    JayJayVee
    Max Output Level: -87 dBFS
    • Total Posts : 169
    • Joined: 2008/02/13 14:54:26
    • Location: Southern California
    • Status: offline
    Re: Melodyne issue 2014/07/05 19:58:06 (permalink)
    Hi Ozz-
    I have been using Sonar Producer V8.5.3 on a 32-bit XP machine for years....and I have the same unique problem with Melodyne Editor.  I contacted Celemony, and they told me to upgrade my whole system to 64-bit and buy Sonar X2.  I had to LMAO off on that advice because I am not about to junk my whole studio *except for Melodyne* and then start over!  That would take months of work and cost thousands.
     
    I did figure out a workaround though that manages to avoid the problem where you move one blob and the other blobs move back to their original pitch.  The process is a royal PITA, but it works every time without fail.  Here is what you need to do:
    • Open up a *NEW* Sonar project that has the same setup as the project you were working on.
    • Import the first audio track that you want to adjust with Melodyne.  Do this by creating a new audio track and then using the Import Audio command.
    • Next, open up an instance of Melodyne on that new audio track and make your adjustments with it.  If that is the only audio track you are going to work on, then render the Melodyne-adjusted track as a new audio track, and import that newly rendered track back into your original Sonar project.
    • If you are going to adjust more audio tracks with Melodyne, then you have to IMPORT EACH ONE SEPARATELY into the new project, and open an instance of Melodyne on each one.  then make your adjustments and render the tracks to new audio versions, as before.
    Doing it that way will prevent the the blob-reverting problem.  In fact, I just got done editing three vocal tracks 30 minutes ago using that very process.  You may be able to get away with re-importing an audio track into your original X3 Project (i.e., create a new audio track and import the original audio track onto it and then open up Melodyne Editor on that new track) and see if that avoids the blob-reverting problem.  That approach might work, or it might not.
    But now I am highly disappointed to find out that you have a 64-bit machine and Sonar X3.....and you are still having the same problem I am having with Melodyne.  So apparently junking my whole system and starting over will not fix the issue. 
    JV
    San Diego
     
    Visit www.soundrecordingadvice.com
    #2
    Ozz
    Max Output Level: -84 dBFS
    • Total Posts : 332
    • Joined: 2010/01/27 02:41:40
    • Location: Upstate NY
    • Status: offline
    Re: Melodyne issue 2014/07/05 21:06:24 (permalink)
    Hmm...Well, not exactly what I was hoping to hear, but I appreciate the response.
     
    Maybe someone else has another option?
     
    Well, luckily it only seems to do it rarely (so far).  And....I have to say, other than that, I really like Melodyne.
     
    But...Celemony...if you're listening....Maybe take a look at this issue??

    Sonar Platinum, Win 10 Pro 64, Intel i7 4770K, 16GB DDR3 1600, 1 x 250GB SSD, 2 x 2TB SATA, Roland OctaCapture, Roland XP-30 (Controller only), Shure KSM-44, Rode NT-1, Shure SM57, Numerous Guitar Amp sims, Komplete 6/7, Alchemy, Custom built guitar, Carvin Amplifiers.
    #3
    Ozz
    Max Output Level: -84 dBFS
    • Total Posts : 332
    • Joined: 2010/01/27 02:41:40
    • Location: Upstate NY
    • Status: offline
    Re: Melodyne issue 2014/07/16 09:39:45 (permalink)
    Bumping to see if anyone else may have noticed this issue?  I've contacted Celemony, and though their respond time is very good, their suggestions haven't yet helped. (Update to latest Sonar patch (I am)...reinstall everything (um...not until I know that it's not going to just happen again).
     
    If nothing else, I've learned to not use Melodyne on the original track....I now make a copy and work on just one of them.
     
    But someone other than myself and JayJay MUST have had this happen....?

    Sonar Platinum, Win 10 Pro 64, Intel i7 4770K, 16GB DDR3 1600, 1 x 250GB SSD, 2 x 2TB SATA, Roland OctaCapture, Roland XP-30 (Controller only), Shure KSM-44, Rode NT-1, Shure SM57, Numerous Guitar Amp sims, Komplete 6/7, Alchemy, Custom built guitar, Carvin Amplifiers.
    #4
    Jump to:
    © 2024 APG vNext Commercial Version 5.1