Melodyne unable to process

Author
Post
Essentials Only Full Version
fooman
Max Output Level: -63 dBFS
  • Total Posts : 1382
  • Joined: 2006/06/26 14:47:44
  • Location: Ontario, Canada
  • Status: offline
2012/04/05 00:54:47 (permalink)

Melodyne unable to process

I've been using Melodyne with Sonar for years, and only in the past few weeks (since mixing with X1d I assume), I'm unable to apply Melodyne to any clips or tracks. I've done it both ways. 1. Adding to clip fx bin then bounce to clip. 2. Adding to track fx bin and freezing track. I even tried bouncing to a new track. No luck. I hear the fixed vocal when Melodyne is open, but the original is the result after bouncing/freezing. Any words of wisdom??
#1

6 Replies Related Threads
    Skyline_UK
    Max Output Level: -54 dBFS
    • Total Posts : 2133
    • Joined: 2004/04/15 17:55:09
    • Location: Midlands, UK
    • Status: offline
    Re:Melodyne unable to process 2012/04/05 02:58:32 (permalink)
    In 1. above are you bouncing to a new clip?  That's what I do.  And I don't use freezing.
    I keep the original track and open underneath it a 'treated' track, in case I want to revisit what I've done.  I chop the original track up into small bits as I've always had lockups then crashes with Melodyne versions after the good old (obsolete) Plugin version.  I insert Melodyne as an FX on the original track, muting any other FX if there.  Make sure the velocity is what you want as it will be bounced at that.  I work on the first clip and when done I highlight (i.e. select) that clip and then use the bounce to track function to bounce the clip to the treated track.  Until Melodyne's resource leak is fixed I then have to save the project, delete the Melodyne plugin, close and re-open Melodyne (yes, exactly...)  I then do the next clip and so on.
     
    NB: Melodyne acknowledged the resource leak after CW told them about it in January following crash dumps I (and others I assume) submitted to CW via Expanded's new problem reporter.  Melodyne have promised a fix but in the next Editor V2 update.

    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 plugins
    BandLab page
    #2
    Guitarhacker
    Max Output Level: 0 dBFS
    • Total Posts : 24398
    • Joined: 2007/12/07 12:51:18
    • Location: NC
    • Status: offline
    Re:Melodyne unable to process 2012/04/05 07:59:48 (permalink)
    when processing or bouncing.... this might be a dumb question but are you selecting and highlighting the track material? 

    You must select the track and it will change color to indicate it is selected. Then the bounce or processing will work. 

    My website & music: www.herbhartley.com

    MC4/5/6/X1e.c, on a Custom DAW   
    Focusrite Firewire Saffire Interface


    BMI/NSAI

    "Just as the blade chooses the warrior, so too, the song chooses the writer " 
    #3
    fooman
    Max Output Level: -63 dBFS
    • Total Posts : 1382
    • Joined: 2006/06/26 14:47:44
    • Location: Ontario, Canada
    • Status: offline
    Re:Melodyne unable to process 2012/04/05 10:12:56 (permalink)

    I have the bounce-to-clip function bound to a key.  It's been the same forever and has worked until recently.  I definitely am bouncing the clip because it's visual when it does so.

    I use the version of Melodyne that was right before the new 2.0 version.  They came out with the direct-note DNA thing, and I got that upgrade for free and haven't upgraded since because it's been working for me.  I don't upgrade unless I either have to or want a new feature haha

    Anywho, I will try out the 'proccess effects' command I've read about.
    I will also think about paying the $100 and upgrading to the latest version, although it seems a bit dumb to upgrade only to deal with a memory leak that causes everyone problems :S
    #4
    fwrend
    Max Output Level: -76 dBFS
    • Total Posts : 709
    • Joined: 2006/09/19 16:02:52
    • Location: Garden City, KS
    • Status: offline
    Re:Melodyne unable to process 2012/04/05 10:22:13 (permalink)
    foo - there have been a few of the same threads recently including one by myself.  Someone commented that this is new to X1d but related to Melodyne.

    However, if you select the clip and then go to Track/Bounce to Track and make sure that you tick Track FX, it will render the clip and apply the changes you made in Melodyne.  If you choose to apply it to the original track, it will replace the original clip.
    #5
    Blogman
    Max Output Level: -81 dBFS
    • Total Posts : 481
    • Joined: 2011/02/08 02:32:48
    • Status: offline
    Re:Melodyne unable to process 2012/04/05 10:25:14 (permalink)
    Yes the time code based effects have been broken in X1D. However you can use a real time bounce to work around this. Or use 8.53. Melodyne worked great for me until X1D. Antares is not working properly either. It process just not what you want it to. This is since X1D. Cakewalk is aware and working on it.
    #6
    fooman
    Max Output Level: -63 dBFS
    • Total Posts : 1382
    • Joined: 2006/06/26 14:47:44
    • Location: Ontario, Canada
    • Status: offline
    Re:Melodyne unable to process 2012/04/05 10:34:22 (permalink)
    I 100% understand that Cakewalk isn't forced to tell anyone these types of things, but if this is true about there being a known issue, an email should go out so people like myself that do this on real deadlines don't waste 2 hrs of their day trying to figure out why something isn't working the same as it did from Sonar 8 to X1c.

    Kinda peeved.  The 'workarounds' are a real setback in workflow IMO.
    #7
    Jump to:
    © 2025 APG vNext Commercial Version 5.1