CD audio does not load in Sound Forge 2

dogfish wrote on 6/18/2020, 3:18 PM

It takes 3 or 4 uploads for the CD track Info (Wave form etc.) to load in Sound Forge Audio Cleaning lab 2, current version, 64 bit Windows 10.. This is not the case with older versions and was not the case with this version until a week ago. The problem is very consistent and is extremely annoying as I do a lot of work with CD's. The program reads the CD info and appears to be uploading but when the upload is finished there is only a track number and no Information. Can anyone provide insight on this or a solution. Thanks.

Comments

rraud wrote on 6/18/2020, 5:17 PM

Are you extracting the audio from a CD (whatever that is)?. In my experience, some tracks take longer to extract than others, regardless of the track length.. error correction maybe.

Does this behavior happen with all discs?

If this version of Cleaning Lab worked before, it could be a drive issue. I would try another drive to see if the issue persists.

emmrecs wrote on 6/19/2020, 4:36 AM

@dogfish

As @rraud has suggested, it would be very useful to we fellow-users if you were to detail, step by step, exactly what you are doing and with what results? I have SFACL2 and would be happy to follow your "method" and see what results I get.

HTH

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

OwenMeany57 wrote on 6/10/2024, 7:59 AM

I started having this exact same audio CD import issue when I got a new computer and installed Cleaning Lab 2, which I had been using on another computer without any import issues. I have since upgraded to versions 3 and 4, and the problem persists. I added an external disc drive and audio CD imports now work fine using that drive. Apparently the problem was related to an incompatibility with the particular disc drive in my computer, which, incidentally, shows no other symptoms of any problem.