Pitch Correction is great, BUT......
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
- chunkdz
- Posts: 115
- Joined: Fri Feb 04, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Slimy Valley, Ca.
Pitch Correction is great, BUT......
Just tried pitch correction for the first time. AMAZING!
Then I tried it on a track with fades on the soundbites. Uggh. Everytime I tweak the pitch it has to recalculate and redraw the fade. I was cruising along, and then it felt like somebody threw an anchor off the starboard side.
Is this a bug or a feature??
Then I tried it on a track with fades on the soundbites. Uggh. Everytime I tweak the pitch it has to recalculate and redraw the fade. I was cruising along, and then it felt like somebody threw an anchor off the starboard side.
Is this a bug or a feature??
8 Core 2.8
DP 5.1.3
M5 II
DP 5.1.3
M5 II
Fades and cross fades are small pieces of audio. If you make changes to the soundbite in terms of pitch automation, any fades associated with that soundbite will need to be recalculated.
I recommend that you merge the soundbites before you do pitch automation. The merge will print the fades to the soundbites and you won't need any recalculation as you do the pitch automation.
I also merge soundbites after I do any pitch automation, so those changes are also printed to the soundfile.
Dave
I recommend that you merge the soundbites before you do pitch automation. The merge will print the fades to the soundbites and you won't need any recalculation as you do the pitch automation.
I also merge soundbites after I do any pitch automation, so those changes are also printed to the soundfile.
Dave
- toodamnhip
- Posts: 3850
- Joined: Fri Jan 07, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Dave, it has been a long awaiting request that DP somehow be able to handles fade calculation without glitching if one presses play too early.... Do you think DP will ever be able to operate as Pro Tools ..i.e.,,no glitching or delay waiting for fade calculations? Even Pro Tools LE does fades without glitching and waiting for calculations so it has to be a software code issue as LE uses native power just like DP.magicd wrote:Fades and cross fades are small pieces of audio. If you make changes to the soundbite in terms of pitch automation, any fades associated with that soundbite will need to be recalculated.
I recommend that you merge the soundbites before you do pitch automation. The merge will print the fades to the soundbites and you won't need any recalculation as you do the pitch automation.
I also merge soundbites after I do any pitch automation, so those changes are also printed to the soundfile.
Dave
Also, I find myself reluctant to merge pitch edits til the last second for fear of doubling the artifacts of pitch correction should I change my mind later and pitch that area again.
Thus, though your idea of merging is a good one and also avoids the problem of the pitch correction being unstable when processor load gets high,but it is unfortunately not a perfect solution..though a good idea as soon as one is truly confident of their pitch corrections
Last edited by toodamnhip on Wed May 07, 2008 10:26 pm, edited 1 time in total.
Mac Pro (Late 2013
2.7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
Mojave
DP 10.13
MOTU 8pre, MTP AV, 828 mkII
Tons of VIS and plug ins. SSD hard drives etc
2.7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
Mojave
DP 10.13
MOTU 8pre, MTP AV, 828 mkII
Tons of VIS and plug ins. SSD hard drives etc
-
- Posts: 1655
- Joined: Mon Oct 18, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Hong Kong
- Contact:
I didn't realize that merging soundbites also 'merges' the pitch correction. This could definitely be handy.
It would be prudent to duplicate the take before merging the fades, then apply pitch correction, duplicate again, then merge the pitch correction.
It would be prudent to duplicate the take before merging the fades, then apply pitch correction, duplicate again, then merge the pitch correction.
MacBook Pro 2021 (M1 Ultra) with 64 gigs RAM. DP 11.23
if i ever use pitch correction (not often, but it's an insanely robust feature to have in DP. I will never buy Autotune or Melodyne, DP's is more than enough for me) I ALWAYS create a NEW DUPLICATE take of whatever I am working on, Merge the soundbite to print fades, make my pitch corrections and Merge it again. I don't trust the realtime playback of pitch corrected soundbites in DP. Just merge them. If you do it to a duplicate take (call it Take 1-PC or whatever) then you can always go back to the original...
why would i want to skin a cat?
I guess the Fades audio files is something a little dated. I can understand the need to pre-render to a file the fade ins/outs in the first versions of DP, where computers didn't have much computational horse-power, but right now it is just completely unnecessary to do it.toodamnhip wrote:Dave, it has been a long awaiting request that DP somehow be able to handles fade calculation without glitching if one presses play too early.... Do you think DP will ever be able to operate as Pro Tools ..i.e.,,no glitching or delay waiting for fade calculations? Even Pro Tools LE does fades without glitching and waiting for calculations so it has to be a software code issue as LE uses native power just like DP.
If DP doesn't need to pre-render to a file:
- track level automation
- soundbite based automation
- virtual instruments, audio processing, etc...
then I guess it's just a case of implementation priorities and not wanting to update the Audio Fades functionality to make it run in realtime, as it should...
Technically, its just another layer of level attenuation... audio fades, soundbite level, channel level. In my opinion, Motu should have changed the audio fade's behaviour and make it realtime when they introduced the soundbite's level functionality.
- toodamnhip
- Posts: 3850
- Joined: Fri Jan 07, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
There are times when the time it takes to render fades makes working in DP impossible...96khz wrote:I guess the Fades audio files is something a little dated. I can understand the need to pre-render to a file the fade ins/outs in the first versions of DP, where computers didn't have much computational horse-power, but right now it is just completely unnecessary to do it.toodamnhip wrote:Dave, it has been a long awaiting request that DP somehow be able to handles fade calculation without glitching if one presses play too early.... Do you think DP will ever be able to operate as Pro Tools ..i.e.,,no glitching or delay waiting for fade calculations? Even Pro Tools LE does fades without glitching and waiting for calculations so it has to be a software code issue as LE uses native power just like DP.
If DP doesn't need to pre-render to a file:
- track level automation
- soundbite based automation
- virtual instruments, audio processing, etc...
then I guess it's just a case of implementation priorities and not wanting to update the Audio Fades functionality to make it run in realtime, as it should...
Technically, its just another layer of level attenuation... audio fades, soundbite level, channel level. In my opinion, Motu should have changed the audio fade's behaviour and make it realtime when they introduced the soundbite's level functionality.
When I am deep into comping a vocal and need to compare subtle differences in a word..and I have to wait 4-5 sec for the rendering..it really really..I mean REALLY sucks...
2 days ago I had the thought that this lack of ability in DP actually makes DP useless to me in certain circumstances....
I mean..do I have to import the darn vocal into Pro Tools LE to do my comping?
That would be ridiculous! There are so many wonderful DP features..this fade rendering kills it at times..
Magic Dave might say, well, merge the fades as you go..but damn..that's what I am experimenting with..where the fade sounds best, what line it works on etc..I cannot merge it until I know where the heck it sounds best and on what take...but yet i cant figure it out because the merge tales too long to work fast enough to really hear what I need to hear..ouch..help!!
Mac Pro (Late 2013
2.7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
Mojave
DP 10.13
MOTU 8pre, MTP AV, 828 mkII
Tons of VIS and plug ins. SSD hard drives etc
2.7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
Mojave
DP 10.13
MOTU 8pre, MTP AV, 828 mkII
Tons of VIS and plug ins. SSD hard drives etc
Yes, if this isn't fixed in DP6 I'd be surprised. The handling of the fades is related to a lot of crashes too, so as 96khz said, the functionality needs to be brought up to date.toodamnhip wrote: Magic Dave might say, well, merge the fades as you go..but damn..that's what I am experimenting with..where the fade sounds best, what line it works on etc..I cannot merge it until I know where the heck it sounds best and on what take...but yet i cant figure it out because the merge tales too long to work fast enough to really hear what I need to hear..ouch..help!!
MBP i7, OSX 10.7.4