Bug when rendering or flattening a Melodyne'd clip
-
- KVRAF
- 1602 posts since 9 Jan, 2018
You have to render the track with Melodyne, which is what saves your data. So do your comping, edits, fixes, etc., first...then pop in Melodyne. Make your Melodyne edits across the whole track, and then render that track. You can then remove Melodyne and any rendered plugins. Incidentally, if you're adding effects to the track *after* Melodyne, you'll want to disable those unless you want them rendered in!
If you're not committed to your Melodyne edits, don't flatten or render the track until you are. That's not a Waveform issue; it's just the way Melodyne works...it's an app within an app.
If you're not committed to your Melodyne edits, don't flatten or render the track until you are. That's not a Waveform issue; it's just the way Melodyne works...it's an app within an app.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRAF
- 1602 posts since 9 Jan, 2018
If you have a bunch of clips, though, doesn't that kill your CPU? I don't know--I've never tried that. Melodyne seems a bit beefy, so I always use it as a track effect.
Melodyne is different. You can even delete the original clips--and the vocals redone in Melodyne still sound on playback! I think that's was was giving pmn a hard time.
Melodyne is different. You can even delete the original clips--and the vocals redone in Melodyne still sound on playback! I think that's was was giving pmn a hard time.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
