MOTUnation.com

jlaudon wrote:I remember a thread where Magic Dave also mentioned that if you have added fades/crossfades and also pitch correction to a track, then merge, there will be artifacts/pops in the merged track. He advised to bounce, which I have been doing without problems. However, I often do this last, sometimes disabling all the other tracks to make the bounces go faster (lighten CPU).

I'm surprised that bouncing has given people problems.

macguy wrote:

jlaudon wrote:I remember a thread where Magic Dave also mentioned that if you have added fades/crossfades and also pitch correction to a track, then merge, there will be artifacts/pops in the merged track. He advised to bounce, which I have been doing without problems. However, I often do this last, sometimes disabling all the other tracks to make the bounces go faster (lighten CPU).

I'm surprised that bouncing has given people problems.

Never had any issue when merging after processing the pitch... strange, or my ears are shot!
I think it depends on how fast your machine is (in RG's case I can't see that because she has the fastest single process Mac you can get) so if there's tons of CF's and edits, maybe merging as much as possible to keep those BG processes @ a minimum should be implemented.

FMiguelez wrote:Hi, RG.

So if I understand correctly, when you use Pitch correction with DP on your tracks, they sound fine in real time when you are mixing (with no artifacts). You get pops and clicks ONLY when you bounce or merge, is this correct?

Sometimes I get pops and clicks when everything is playing in realtime, but that may be something different.

If I got you right, I will use your tip next time. Thanks for sharing

Radiogal wrote:I posted this in the TURTORIAL section but I believe this insight might be of good value to all of us. So I feel the need to put it right here too as DP ppl mostly hang out here and not in the tutorial department as we all do

So here we go:

I recently read somewhere about Melodyne that it´s not recommended to merge nor bounce offline coz it will give artifacts like clicks and pops in Melodyne processed tracks..

Hmmmm.... thinking.

That made me think about DP pitch as I´m having issues with pops, clicks and variable pitching results after merging pitched tracks in DP. These artifacts aren´t there before I´m printing/merging the track(s).

So when reading this about Melodyne it made perfectly sence to me.
As DP PITCH is done In Real Time it can differe a lill bit each time you play it. It´s all CPU based and together with everything else that needs processing it seems to be hard for the processor to do this identical every time, especially when printing using merge or offline bounce.

So now I´ve changed my way of "bouncing" the pitched tracks to avoid these CPU based artifacts that occur during the offline printing.
My solution to this is to RERECORD the pitched track to BUS O/P to a new Audio Track I/P and record IN REAL TIME while this track is SOLOED!

This way all CPU is used for the pitching process.
You can monitor the process and detect problems immediately.

Since I´ve started using this procedure i haven´t yet had any problems with these artifacts anymore

The process might take some extra time but is totally worth it.
A/B check and you´ll hear the difference.

Just my 2 cents

Radiogal wrote:(s).

So when reading this about Melodyne it made perfectly sence to me.
As DP PITCH is done In Real Time it can differe a lill bit each time you play it. It´s all CPU based and together with everything else that needs processing it seems to be hard for the processor to do this identical every time, especially when printing using merge or offline bounce.

waterstrum wrote:You didn't mention freeze.
I always thought that would render a perfect copy of the selected audio.
Or is freeze the equivalent of bounce?
Yes?
No?

How can I render one track of audio with some DP pitch correction for absolutely accurate export?
Thanks.