Problem with LP transfers

9 replies
86 views
Translate

I produce a weekly radio series (Analog Masters) devoted to classical LPs and 78s. I regularly use Audition to transfer audio from the original source to a digital format. Since the most recent Windows update (late August 2026), I have noticed an audio problem that was not previously audible. Natural fades (such as at the end of a movement) are no longer smooth. One or more ‘bumps’ in audio level are noticeable as the last note fades. I use a Behringer U-Phono UFO202 unit for analog-to-digital conversion. My computer is a recent Dell running Windows 11. I had the most recent version of Audition, but as a test I reverted to 25.6.6. This did not cure the problem. I have also restarted my computer and double-checked all audio settings.

Is anyone else experiencing this issue? Any suggestions?

F

FugitiveVisionCorrect answer

Inspiring

There was an audio driver update in July that may have been the cause of this problem: Microsoft Corporation AudioProcessingObject Driver Update (1.0.4.7057). I’ll continue to investigate. Thanks again!

F

FugitiveVisionAuthor

Inspiring

This has somehow been designated as the ‘correct’ answer. IT IS NOT. Enabling dithering changes nothing. The problem is not at -96. It’s clearly audible at about -18dB. It sounds almost like the old fashioned analog tape ‘slap back’ echo. See sample below. Listen from about 14.5 seconds into the file to the end. Thoughts anyone?

Translate

MousTest.wav

SteveG_AudioMasters_

Community Expert

I don’t know who marked it as correct - it wasn’t me. And I’ve unmarked it.

But I’ve now listened to your sample and I can hear exactly what you mean. Assuming that you can monitor the output of the UFO202 using the headphone socket and it sounds fine, then this rather points the finger at whatever driver you are using, because that’s the only thing between it and Audition. Windows can get up to all sorts of tricks, including some very dodgy resampling that it doesn’t tell you it is doing.

One thing that can provoke this to happen is to have the sample rate set differently to the rate at which you are actually recording, and this is something an OS update could muck up. Your file is 44.1k, but the UFO202 only operates at 48k, so I’m a bit suspicious....Anyway, this will invoke resampling by the OS, and that’s always bad. Buried deep in the Sound settings is the place to check this - on this laptop you have to go the Sound settings, pick your input device, go to device properties, then under Related Settings click on Additional device properties, and then go to the Advanced tab, and finally you will find the Default Format settings. You need to make sure that this is set to 2 channel 16 bit,48000 Hz (DVD Quality). Whilst you are there, in the Enhancements tab make sure that all effects are off.

Now, when you go to record in Audition, make sure that this is also set to 48k, even if you want the end result to be 44.1k. When you’ve made your recording then use Audition’s File>Convert Sample Type to convert it - this is an absolutely blameless conversion (independently verified).

If after all this you still have the problem, report back.

Translate

F

FugitiveVisionAuthor

Inspiring

SteveG: I think you’re definitely on to something, though I have been recording at 44.1 all along (may years!) -- and this problem just started after the most recent windows update. I’ll do as you suggest and report back.

Translate

SteveG_AudioMasters_

Community Expert

I’m pretty sure that the UFO202 is a 16bit device, and that’s significant. When you digitise with one of these,you need to make sure that when you finally save the file, you have enabled dither (of some sort) on the file settings panel. If you don’t do this, then all sorts of strange things happen when your 16-bit file drops off a cliff at about -96dB. Dither ‘randomises# this process and effectively replaces the troublesome digit with noise. Dither is actually a complex subject, but not enabling it when saving an integer-based 16bit file always gives this problem with the least significant bit. Fortunately you don’t really need to understand it to be able to use it!

Translate

F

FugitiveVisionAuthor

Inspiring

I’ll check my settings. I haven’t changed anything since the Win 11 update, but sometimes the updates do cause changes to existing settings. Also, the problem I’m hearing is audible long before -96!

Translate

SteveG_AudioMasters_

Community Expert

If that’s the case, then make sure that it’s actually a 16bit file you are recording!

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.