• SONAR
  • not solved: Melodyne Essentials; problem saving changes to new clip
2015/01/09 00:01:22
Chevy
Hi, been trying to get some support from Melodyne, but the person there just doesn't seem to be of much help at all. Very frustrating. 
Anyways....  The problem is, when I take a bass guitar 2-bar clip and correct the timing with Melodyne, Region FX, then do a "save" on the file, then try to paste the same clip into the next 2 bars on the same track, the Melodyne changes do not appear in the newly pasted clip. The newly pasted clip header does indeed say <Melodyne> on it, but the changes are not carried over to it.  This is exasperating, as it means I have to alter every single clip in the song, can't just copy them over. Anyone experience this ?  
2015/01/09 00:41:48
mettelus
Melodyne can have some flaky behavior to it, and getting too heavy-handed with edits can cause issues as well. Are you trying to repeat a 2-bar pattern for a longer duration? If so, I would be more apt to do the edits to taste, then "Bounce to Clip(s)" to embed the edits (right click the clip), next I would enable "Groove-Clip Looping" (also right click) and can drag the right edge to repeat as many times as you want. You can also Bounce to Clip(s) after you have the desired duration to create one clip from this.
 
Melodyne is best-suited for surgical functions on small regions where an edit is made and then bounced. Excessive editing can be problematic, but I am not sure about copying Region FX specifically.
2015/01/09 02:54:16
Anderton
I think you need to bounce to clip before copying. Melodyne is meant to work within a specific region, hence, Region FX. If you change where the clip resides, that changes the region. I don't know for sure if this is your issue, but there are other limitations to clips that are open in Melodyne...for example, you can't split the clip. 
 
When working with Melodyne I generally make my changes, then bounce. Once the clip is fixed, I don't see any reason to keep Melodyne open. If I think I may want to re-visit the changes, I work on a copy and archive the copy...but I very rarely do that.
2015/01/09 12:23:47
Chevy
OK, thanks for the tips and sorry to exhibit the newbie frustration...   my thinking on the whole thing was that every time you bounce a clip, the audio quality level reduces, and that's not a good thing. 
2015/01/09 12:37:00
Anderton
Chevy
OK, thanks for the tips and sorry to exhibit the newbie frustration...   my thinking on the whole thing was that every time you bounce a clip, the audio quality level reduces, and that's not a good thing. 



No worries, even though you are the first person ever to exhibit newbie frustration   But seriously, bouncing with a 64-bit audio engine is not like bouncing with tape. You can bounce all week and there's enough resolution to maintain the original sound quality. I sometimes bounce a Melodyne clip, then go in and do additional edits and re-bounce.
2015/01/10 13:36:30
Chevy
Hi again,
Thanks for the tips again, but have new problem...   when I right click on and bounce the Melodyne'd clip, the audio waveform comes back as a flat line.  When I remove the Region FX, then bounce it, it comes back properly as an audio waveform...  what is happening here, any ideas ?  I also tried to bounce it onto a new track, and the audio came back as a flat line as well....???????
 
Also, I tried to bounce a drum clip just for fun in a different project, and it came back visually altered from the original...   so this again has me worried about bouncing and degrading audio quality.  My Sonar is set up as 64 bit engine, 32 bit record/playback. 
2015/01/10 18:01:54
mettelus
Pay close attention to the pop-up that comes up with options for bouncing to clip(s) (there are many options on that pop-up you really need to read through and understand), as the checked items get embedded into the bounce. If you have Track mute/solo checked and that track is muted, the bounce will be a flat line (only time I have seen this).
 
Sometimes SONAR does not show the wave form, and there is an option to redraw that (not sure where off the top of my head), but it is just a visual indicator (the audio will still play). It is more probable that you have embedded things you did not intend to into the audio bounce - but as always with music - trust your ears, not your eyes.
 
As Craig said, digital rendering does not degrade audio as analog does, which is a massive advantage to using a DAW. I have also bounced a track multiple times, and the difference is in the processing precision of plugins used in most cases, which is incredibly accurate compared to analog (because they are working with "just numbers").
2015/01/10 19:05:59
Anderton
Also note that it might be in a Take Lane and muted within that lane.
2015/01/11 13:29:08
Chevy
Hmmm...  no joy.  I'm testing this in as simple as possible a configuration:  I have a new project with only one unmuted track, containing a couple of clips that have been Melodyne'd.  I select one clip by right-clicking, and get the option to bounce it or edit or convert to stereo, etc.  on the pop-up.  When I click on Bounce to Clip(s), it just goes and bounces to clip, no options at all.  And the audio comes back flat-line, and no sound. When I remove Region FX, it bounces it just fine.  ...................??????????????????????  
Not using Take Lanes.
2015/01/11 14:27:05
Anderton
Try shift-dragging it into a new track and see what happens. I've had the same thing happen, but it was always something I wasn't taking into account, like what I mentioned above.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account