Hi,
There is a project I have been working on lately in which everything I mixdown has nasty distortion which reminds me of aliasing and misaligned DAT machine mechanisms. The mixdowns are of mixed variety - many of them at the 24/96 project sampling rate, some "knocked down" to 16/44, like takes. Mixing down in real time sometimes works. Generating takes for clients with real time mixdown enabled is not practical, though. Has anyone else experienced this? What other troubleshooting steps should I try?
Cheers,
-Charlie
Mixdown distortion
Forum rules
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
To ensure that your support issue or bug report is dealt with properly and in good time, please use the link to the tech support request form page on the Merging website.
Make sure to let us know what version you are using when you send your mail. THANKS!
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
To ensure that your support issue or bug report is dealt with properly and in good time, please use the link to the tech support request form page on the Merging website.
Make sure to let us know what version you are using when you send your mail. THANKS!
-
charlienyc
- Posts: 397
- Joined: Wed Aug 16, 2006 22:40
- Location: chicago, il
- Contact:
Mixdown distortion
MassCore v14.0.5 Win10/64 i9-10900 & i9-11900K, Avid S3
3x Horus = 80 In/24 Out @PCM
Native V14 Win10/64 i7-12700K miniDSP UDIO-8, Avid S1 & nob controller
Native V14 Win10/64 ThinkPad P51 i7-7700HQ w/Hapi
3x Horus = 80 In/24 Out @PCM
Native V14 Win10/64 i7-12700K miniDSP UDIO-8, Avid S1 & nob controller
Native V14 Win10/64 ThinkPad P51 i7-7700HQ w/Hapi
Re: Mixdown distortion
The usual suspects? Latency set too low, network connection compromised, a recent system update that can be identified as the start of the issue, some miscreant plug-in process set to an unstable oversampling rate...
Of course none of these answer why a non-realtime mixdown doesn't simply take the amount of time it requires to provide glitch-free audio.
Of course none of these answer why a non-realtime mixdown doesn't simply take the amount of time it requires to provide glitch-free audio.
Frank Lockwood, Toronto, ON, Canada
• Pyramix Native 11.1.6
• Mac Mini 6.2 (3rd Gen. Quadcore i7) - Bootcamp 6.0.6136 - Win10 Pro SP1 64 v1809
• RME Fireface 800 ASIO driver 3.125 or ASIO4All 2.15
• Pyramix Native 11.1.6
• Mac Mini 6.2 (3rd Gen. Quadcore i7) - Bootcamp 6.0.6136 - Win10 Pro SP1 64 v1809
• RME Fireface 800 ASIO driver 3.125 or ASIO4All 2.15