Jump to content

Recommended Posts

Posted

I have been successfully burning audio CDs with Imgburn for a year now. The most recent CDs are all playing too fast, like twice normal speed. The only possible thing I have done different is changing the recording from stereo to monaural before saving it as a wav file. Even setting the project to 22050 before saving as a wav file does not fix the fast playing recordings on CDs. Why is this happening and can it be fixed?

 

Debug log follows. If it provides the answer, what is it that provides the clue?:

00:16:05: Trying to load FFmpeg libraries

00:16:05: Trying to load from default path C:\Program Files\FFmpeg for Audacity\avformat-52.dll.

00:16:05: Looking up PATH...

00:16:05: PATH = C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\Program Files\QuickTime\QTSystem\;C:\WINDOWS\system32\WindowsPowerShell\v1.0

00:16:05: Checking that C:\Program Files\FFmpeg for Audacity is in PATH...

00:16:05: not in PATH!

00:16:05: Appending ;C:\Program Files\FFmpeg for Audacity ...

00:16:05: Loading avformat from C:\Program Files\FFmpeg for Audacity\avformat-52.dll

00:16:08: Loading avutil from C:\Program Files\FFmpeg for Audacity\avutil-50.dll

00:16:08: Loading avcodec from C:\Program Files\FFmpeg for Audacity\avcodec-52.dll

00:16:08: Returning PATH to normal...

00:16:08: Importing symbols...

00:16:08: All symbols loaded successfully. Initializing the library.

00:16:09: Retrieving library version.

00:16:09: AVCodec version 0x342000 - 52.32.0 (built against 0x342000 - 52.32.0)

00:16:09: AVFormat version 0x342400 - 52.36.0 (built against 0x342400 - 52.36.0)

00:16:09: AVUtil version 0x320300 - 50.3.0 (built against 0x320300 - 50.3.0)

00:16:09: AVCodec version mismatch is 0

00:16:09: AVFormat version mismatch is 0

00:16:09: AVUtil version mismatch is 0

00:16:09: Libraries loaded successfully!

Posted

I have been successfully burning audio CDs with Imgburn for a year now. The most recent CDs are all playing too fast, like twice normal speed. The only possible thing I have done different is changing the recording from stereo to monaural before saving it as a wav file. Even setting the project to 22050 before saving as a wav file does not fix the fast playing recordings on CDs. Why is this happening and can it be fixed? Log file is attached to this message. I see that I am getting errors at the end. I have been successfully using CDs from this same batch for several weeks now. I have burned 3 CDs in a row with the same fast playing.

 

Debug log follows. If it provides the answer, what is it that provides the clue?:

 

00:16:05: Trying to load FFmpeg libraries

00:16:05: Trying to load from default path C:\Program Files\FFmpeg for Audacity\avformat-52.dll.

00:16:05: Looking up PATH...

00:16:05: PATH = C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\Program Files\QuickTime\QTSystem\;C:\WINDOWS\system32\WindowsPowerShell\v1.0

00:16:05: Checking that C:\Program Files\FFmpeg for Audacity is in PATH...

00:16:05: not in PATH!

00:16:05: Appending ;C:\Program Files\FFmpeg for Audacity ...

00:16:05: Loading avformat from C:\Program Files\FFmpeg for Audacity\avformat-52.dll

00:16:08: Loading avutil from C:\Program Files\FFmpeg for Audacity\avutil-50.dll

00:16:08: Loading avcodec from C:\Program Files\FFmpeg for Audacity\avcodec-52.dll

00:16:08: Returning PATH to normal...

00:16:08: Importing symbols...

00:16:08: All symbols loaded successfully. Initializing the library.

00:16:09: Retrieving library version.

00:16:09: AVCodec version 0x342000 - 52.32.0 (built against 0x342000 - 52.32.0)

00:16:09: AVFormat version 0x342400 - 52.36.0 (built against 0x342400 - 52.36.0)

00:16:09: AVUtil version 0x320300 - 50.3.0 (built against 0x320300 - 50.3.0)

00:16:09: AVCodec version mismatch is 0

00:16:09: AVFormat version mismatch is 0

00:16:09: AVUtil version mismatch is 0

00:16:09: Libraries loaded successfully!

ImgBurn.log

Posted

Is there some issue with leaving the WAV files as stereo and 44khz?

 

That's what all audio must be converted back to before being burnt as a CDDA track.

 

If the converted stuff isn't playing properly, your DirectShow/ACM filters are doing a bad job.

 

When you're on the 'Create CUE File' screen and have added one of the problem WAV files, right click that file in the list and select 'Display DirectShow Filters List'. When the message box pops up, press CTRL+C to copy its contents to the clipboard. You can then CTRL+V (paste) it into a reply.

Posted

The original sound source is a single microphone recorded in Audacity as a stereo track. Using Audacity I split the stereo tracks to monaural. Splitting stereo to monaural was cutting my wav file sizes in half. As I said this is the first time I have done this. Previously I was burning with the stereo tracks, and I forgot that CDDA required stereo tracks, so... my bad. This is probably the issue. D'oh! When I have time, I will see about duplicating the monaural track as a second track and then try burning it. I have not used ImgBurn to create a cue file, I do that in Audacity because the track is typically 45 minutes long, and so I use Audacity label function to pinpoint cue'd tracks. However, below is the DirectShow filter list you asked for, and voila, why don't I have any files listed? I don't know.

 

Right now I have to go make a recording, so I will check in later. "Thanks for the heads up.", he said sheepishly.

 

---------------------------

ImgBurn

---------------------------

File Name:

 

C:\Documents and Settings\Administrator\My Documents\WCF\Sunday Raw Audio\101-01 Jan 30 2011 edit noise.wav

 

DirectShow Filter List:

 

1. -> Source (Vendor Info: Unknown)

2. -> Wave Parser (Vendor Info: Unknown)

3. -> AC3Filter (Vendor Info: Unknown)

4. -> ACM Wrapper (Vendor Info: Unknown)

5. -> Sample Grabber (Vendor Info: Unknown)

6. -> Null Renderer (Vendor Info: Unknown)

 

---------------------------

OK

---------------------------

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.