Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

CC 2019 48K audio glitching

Community Beginner ,
Dec 18, 2018 Dec 18, 2018

Just upgraded from AA3 to AA CC 2019 and now Audition creates audible glitching on all 48K files. This is what it sounds like ..

http://dannycox.dyndns.org:8080/share.cgi?ssid=0XDRvUx

Interestingly, if I record, a 48K WAV and play it back through Window Media Player it sounds fine, but AA doesn't seem to be able to cope with it.

To give a bit more clarity ;

If the file is recorded as a 44.1 Waveform it plays fine

If I convert it to 48k it glitches

If I record a file at 48k it glitches

If that file is dropped into a 48k Multitrack it glitches

If the file is dropped into a 44.1 multitrack  (it offers to to convert it to 44.1) then it's fine

If I try and open any previous files/mulitracks which sounded OK at 48K, they now glitch.

It appears to be a playback issue with AA CC 2019 not coping with 48K files for some reason, as other programs playback the same files and they sound totally clean. Nothing else has changed on my PC other than an upgrade from AA V3 to CC 2019.

Has anyone else come across this and found a fix for it ?

Danny

2.5K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 19, 2018 Dec 19, 2018

Possibly due to incorrect audio hardware drivers or settings. What Operating System are you running on? What audio interface are you using for playing back these files in Audition and how is your Audition Audio Hardware preferences set up?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 19, 2018 Dec 19, 2018

That's it !

I'd checked and both in & out device settings in the PC were correctly set to 48K, but changing from 16Bit depth to 24Bit depth cleared the glitching !

Now all audio plays back perfectly. Thanks for the tip - and the encouragement to dig deeper.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 19, 2018 Dec 19, 2018

Don't really see why that should have fixed it but if it's successfully fixed then it's fixed.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 21, 2018 Dec 21, 2018

Actually my excitement peaked a  little too soon, it turns out this didn't solve the issue.

  • Right now, PC device properties are set to 48K 24bit for both input and output,
  • My Soundcraft USB control panel shows it's set to 48K 24bit
  • When I start a new recording at 48K 24Bit in CC 2019 I get the glitching
  • ...which disappears when I 'Convert Sample Type' to 44.1K

Like to think I know what I'm doing with sound and PCs but this has me baffled. As I said earlier, AA V3 worked perfectly and this issue only arose when I moved to CC 2019.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 21, 2018 Dec 21, 2018

What do you have selected in the Device Class box in Audition's Audio Hardware preferences? If Soundcraft provide ASIO drivers for their device you should use that as it completely bypasses Windows and therefore the Windows Sound settings shouldn't have any effect. it could be that you have the Buffer size or Latency set too low. Again check those in Auditon's Audio Hardware prefs.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 21, 2018 Dec 21, 2018

Thanks for the suggestion, already set to ASIO...

Audio Hardware Device Class.png

Soundcraft USB control panel set to defaults too...

Soundcraft USB.png

Appears this, somehow, is an Adobe playback issue as other programmers play the files just fine.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 21, 2018 Dec 21, 2018

That's a huge buffer. Have you tried taking it out of Auto and selecting a smaller one? You may also need to take the check out of 'use machine-specific device defaults'. Admittedly it's quite rare, but having a buffer that's too large can be just as much of a problem as one that isn't large enough...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 21, 2018 Dec 21, 2018
LATEST

That's it !! Fixed

There was no option (despite the drop down box) to change the I/O Buffer Size in AA, but by deselecting 'use machine-specific device defaults'. ...

Audio Hardware Device Class fixed.png

..and changing the buffer size in the Soundcraft Control panel, all now works fine...

Soundcraft USB fixed.png

...when you create a file at 48K it sounds fine, when you create a file at 44.1K it sounds fine. Many, many thanks for your time on this, and hopefully this may help someone else who has this unique combination of errors.

Danny

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines