Hi,
MCompare is fantastic, but I'm having an issue with sample rate conversion. The documentation says that MCompare will resample the comparison file audio automatically, but I'm working on an 88.2KHz session in Pro Tools (mac), and when bringing in a 44.1KHz WAV or AIFF and it plays back at the proper speed, but the playback both from the file in MCompare and the Pro Tools session is severely distorted.
I'm on Mac OS 10.2.2, PT 11.3.1 and using a UAD Apollo.
Thanks!
MCompare and sample rates
-
- KVRer
- 4 posts since 17 Jan, 2010
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hi,
ok, can you send me some clip of the "distortion" to info@meldaproduction.com? This is usually something else. Anyway did you read the documentation about output gain? Meaning that since there is NO LIMITER behind the plugin, you need to ensure the output won't peak (due to ALC for example), so you can use the output gain, try -10dB and check if the distortion persists. Also what is OSX 10.2.2??? I don't think the plugins work on anything older than 10.5.
ok, can you send me some clip of the "distortion" to info@meldaproduction.com? This is usually something else. Anyway did you read the documentation about output gain? Meaning that since there is NO LIMITER behind the plugin, you need to ensure the output won't peak (due to ALC for example), so you can use the output gain, try -10dB and check if the distortion persists. Also what is OSX 10.2.2??? I don't think the plugins work on anything older than 10.5.
-
- KVRer
- Topic Starter
- 4 posts since 17 Jan, 2010
Thank you for the reply!
On the OS, sorry, I meant 10.10.2.
For the sound, it's definitely not an overdrive kind of distortion, it's a digital hash kind of distortion. Unfortunately, when it happens if I try to bounce a clip, the clip is actually fine. So I can't think of a way to send an example.
Another thing that might be related is that on these higher sample rate sessions with a fair number of plug-ins, MCompare seems to aggravate Pro Tools' 11.3.1 tendency to throw AAE -9173 errors. So, if I'm switching back and forth between files and the live tracks in MCompare, it will overload and put up the Pro Tools ran out of CPU power dialog. I've tried deactivating a lot of plug-ins, but MCompare in particular seems to give Pro Tools bit of a fit even when the total power consumption is low (like 20% on the Pro Tools resource meter). But, the digital hash sound that happens with the 44.1KHz files in this 88.2KHz session is that same digital hash that I get after the AAE -9173 error. And, I just discovered that resetting the buffer to any value (basically resetting the audio engine, I guess) clears the digital hash both from the -9173 error and also for the 44.1KHz files.
So, with all that, I do think up sampling is working, but only after changing the buffer setting and resetting the audio engine. So, that will be my workaround for now. And I've also been able to workaround the -9173 error when switching between files and the live tracks by doing my switching slower. There seems to be a CPU spike right at the moment of turning on or off one of the files in MCompare, and it throws my CPU meter up to literally 98%. But, if I wait several seconds for it to calm down and move back to 20-30%, then I can switch without causing the hash. I hope that helps anyone else who might be running into these issues.
This is a weird one. It seems to be that Pro Tools is sensitive and MCompare kind of pushes it in a way that exposes this sensitivity!
-C
On the OS, sorry, I meant 10.10.2.
For the sound, it's definitely not an overdrive kind of distortion, it's a digital hash kind of distortion. Unfortunately, when it happens if I try to bounce a clip, the clip is actually fine. So I can't think of a way to send an example.
Another thing that might be related is that on these higher sample rate sessions with a fair number of plug-ins, MCompare seems to aggravate Pro Tools' 11.3.1 tendency to throw AAE -9173 errors. So, if I'm switching back and forth between files and the live tracks in MCompare, it will overload and put up the Pro Tools ran out of CPU power dialog. I've tried deactivating a lot of plug-ins, but MCompare in particular seems to give Pro Tools bit of a fit even when the total power consumption is low (like 20% on the Pro Tools resource meter). But, the digital hash sound that happens with the 44.1KHz files in this 88.2KHz session is that same digital hash that I get after the AAE -9173 error. And, I just discovered that resetting the buffer to any value (basically resetting the audio engine, I guess) clears the digital hash both from the -9173 error and also for the 44.1KHz files.
So, with all that, I do think up sampling is working, but only after changing the buffer setting and resetting the audio engine. So, that will be my workaround for now. And I've also been able to workaround the -9173 error when switching between files and the live tracks by doing my switching slower. There seems to be a CPU spike right at the moment of turning on or off one of the files in MCompare, and it throws my CPU meter up to literally 98%. But, if I wait several seconds for it to calm down and move back to 20-30%, then I can switch without causing the hash. I hope that helps anyone else who might be running into these issues.
This is a weird one. It seems to be that Pro Tools is sensitive and MCompare kind of pushes it in a way that exposes this sensitivity!
-C
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Thank you for the exhaustive info!
Right now we are finishing the major update, which focuses on the performance a lot. Sadly ProTools is the most fragile host on earth when it comes to the CPU overloads. Besides the message box, which is just idiotic (Logic originally had that too, but you can disable it there at least), PT also tends to do this distortion playback thing. It's 100% ProTools bug (you can verify - if you put some plugin, make it cause overflow, then remove the plugin, PT continue doing it). I reported it multiple times, so I'll do that again, but Avid...
Anyway please wait for the update, hopefully it will fix these things. If not, please just contact me afterwards. A beta should be out in a week or so.
Right now we are finishing the major update, which focuses on the performance a lot. Sadly ProTools is the most fragile host on earth when it comes to the CPU overloads. Besides the message box, which is just idiotic (Logic originally had that too, but you can disable it there at least), PT also tends to do this distortion playback thing. It's 100% ProTools bug (you can verify - if you put some plugin, make it cause overflow, then remove the plugin, PT continue doing it). I reported it multiple times, so I'll do that again, but Avid...
Anyway please wait for the update, hopefully it will fix these things. If not, please just contact me afterwards. A beta should be out in a week or so.
-
- KVRer
- Topic Starter
- 4 posts since 17 Jan, 2010
Sounds good, thank you so much. MCompare has instantly become invaluable to me, so I'm happy to help provide info in any way I can.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Thank you!