![]() |
#1 |
Junior Member
Join Date: Jan 2006
Posts: 2
|
Problems ripping a CD of mine.
I purchased winamp pro today, so I could get some of my new CD's onto my comp, but everytime I try to rip this cd it gives me this error "error ripping track#1 Can't open decoder. Aborting."
Any clue? I'm really hoping I just didn't waste 20 bucks >< |
![]() |
![]() |
![]() |
#2 |
Junior Member
|
Can you play the cd in winamp? and do you hear sound then?
|
![]() |
![]() |
![]() |
#3 |
Junior Member
Join Date: Jan 2006
Posts: 2
|
yes the tracks play, and I can hear them clearly
|
![]() |
![]() |
![]() |
#4 |
Techorator
Winamp & Shoutcast Team Join Date: Jun 2000
Posts: 35,867
|
http://forums.winamp.com/showthread....d=161361#specs
Was it a clean install of 5.12 Pro, or did you install it straight on top of a previous installation of Winamp? If the latter, then are there ANY 3rd-party plugins present, eg. any replacement mp3 decoders like in_mp3pro? Were there any error messages during installation? (eg. any relating to Sonic Engine / px.dll) What is your Windows OS? What is your CD-ROM Drive make/model? What are your relevant settings in Winamp? Winamp > Prefs > CD Ripping: Encoder tab: Encoding Format = ? Encoder Options = ? Ripping tab: Speed = ? Read audio data using Sonic... = checked/unchecked? Output File Settings tab: Destination Folder = ? Does this folder definitely already exist? Naming Convention = ? What other processes are running concurrently? (c/o HijackThis log - see "specs" link for details) _____________________________________________________ Then there's this from the FAQ Error ripping track #1: Can't open decoder. Aborting http://forums.winamp.com/showthread....65#post1223065 http://forums.winamp.com/showthread.php?threadid=233947 http://forums.winamp.com/showthread.php?threadid=233499 |
![]() |
![]() |
![]() |
#5 |
Junior Member
Join Date: Feb 2006
Posts: 2
|
For what its worth. I had the same problem.
Error "error ripping track #x: can't open decorder. Aborting" and "CD Drive Currently in Use" and "Can't open destination file" The solution was simple dispite seeming otherwise. As it turns out, some file names get too long when a complete file naming convention is used. For example if <Artist> - <Album>\## - <Artist>-<Album>- <Title> is used for some tracks the number of characters exceeds the maximum. I found that either by shorting the file naming convention for certain tracks (sometimes things like "featuring xx" or "writtin by xx" will show up in the track title causing extremely long file names) or by editing certain tracks or changing album title in the track editor the problem was resolved very easly. Hope this helps, MandoMan ![]() |
![]() |
![]() |
![]() |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|