FAQs
  • Q: Can only use WildFire CD Ripper when having adming rights, how to solve this?
    A: First, login as Administrator, then:
    1. Open the “Local Security Policy” console by clicking on the start menu -> control panel -> administrative tools, and select local security policy.
    2. Then expand the “Local Policies” section and select “security options”.
    3. Change “Devices: Restrict CD-ROM access to locally logged-on user only.” to ENABLED.
    4. Reboot your computer, and try as user…
  • Q: When I rip mp3’s and then view file info in winamp it says Header found at: xxx bytes and not zero, why?
    A: Winamp reports the location of the first MPEG header in the MPEG stream data. If you have enabled the ID3V2 tags, it will place the ID3V2 header before the MPEG stream, the the first MPEG header will be shifted with the size of the ID3V2 header.
  • Q: Replace space character does not work.
    A: The function does work, however, the character replacement will only replace one character and by default the space is replaced with a space character. So to set the space replacement character, you have to delete the space character in the edit field and then type the replacement character.
  • Q: When are you going to support MP3Pro?
    A: Probably not in the near future, since there is not a free implementation of the MP3Pro encoder. Using the Fraunhofer library is not an option due to licensing issues using the MP3Pro encoder library.
  • Q: I Installed WildFire CD Ripper, but are not able to listen to MP3 files, and the MPEG->MPEG conversion does not work and neither the MPEG->WAV option fails also, what’s wrong?
    A: If you used the zip file, you probably have not selected the “Use Folder Names” option during the unzipping process, therefore the input plugins (e.g. in_mp3.dll) are not placed in the Plugins folder. To remedy this problem, Unzip the files again with the “Use Folder Names” option enabled within WinZip (or create a Plugins folder, and move the in_*.dll files into this folder). When you used the EXE Installer file, you probably have de-selected the “Winamp Plugins” option, so the plugins are not installed. To remedy this problem, re-install WildFire CD Ripper with the “Winamp Plugins” option enabled.
  • Q: When I extract MP3 files from a CD, I woulb like WildFire CD Ripper to create ‘Napster Style’ file names (i.e. [artist]-[title].mp3) instead storing tracks into separate directories based on artist/album/trackname information, how can I do that?
    A: Will just change the build file name string (press F4 and select the Filenames TAB) to: %1-%4 and you should be set, take a look at the help file for more details which options you can use for the build filename string.
  • Q: At home, I can access the CDDB database, but when I use WildFire CD Ripper at my work place it does not work.
    A: At your work you are almost certainly behind a firewall, therefore you have to select the Use Proxy option in the CDDB options dialog box (use F4 and press the CDDB-TAB). In addition you have to fill in the proxy address in the edit field next to the Use Proxy selection box (which should be enabled when you’ve selected the Use Proxy option, and maybe have to change the Proxy Port). A tip: take a look at the proxy settings of your Web browser (e.g. Internet Explorer or Netscape) to determine the proxy address and proxy port.
  • Q: When I try to access the CDDB database, I get an Invalid E-mail Address message.
    A: You have to fill in the E-mail Address field in the CDDB options dialog box (use F4 and press the CDDB-TAB).
  • Q: I like to create file names that have track number with a leading zero (so 01 02 03 etc in stead of 1 2 3)…
    A: Use the %7 option in the Build File Name string in stead of the %3 option. The %7 tag will be replaced with the track number, including a leading zero for single digit number (i.e. track 1..9) when creating the file name
  • Q: Will WildFire CD Ripper work with Windows 2000?
    A: Many people have problems running WildFire CD Ripper with the Windows 2000 operation system. However, you have to make sure that you have installed the proper ASPI drivers that are supported under Win2K.
  • Q: How can I clear the status information that’s displayed in the main track windows?
    A: The status information is stored in separate files in the Windows Temp directory as TXT files. The file name is derived from the CD-Volume ID. You can safely delete these text files, and the status should be cleared. I will likely add a special menu item to make this a little bit more user friendly.
  • Q: Is it possible using WildFire CD Ripper to merge several track into one single WAV/MP3 file?
    A: What you can do is to to select several tracks, and hit the partial track copy, with this option you can select a range which is ripped/encoded into one big file.
  • Q: When I extract file there is no music at all, just dead silence, what’s wrong?
    A: This problem might be one of the following:
    1. Make sure that you have installed the proper ASPI drivers. This link http://w3.westnet.gr/mp3/rippers/aspi.htm has information how to install the proper ASPI drivers (version Adaptec’s ASPI version 4.54 or 4.57 should work)
    2. Make sure your drive does support CDDA (see http://www.mp3.com/cdrom.html to determine if your drive does support CDDA
    3. Some CD-ROM drives can not read more than 27 sectors at once. If you run WildFire CD Ripper version 1.02 or lower, make sure that the SUM of Read Sectors and the Read Overlap value does not exceed 27. Thus if Read Overlap is set to 7, reduce the Read Sectors value to 19. If you are running WildFire CD Ripper version 1.10 or higher, it is safe to set Read Sectors to 26.
    4. Try the Auto Detect feature. See the WildFire CD Ripper help file for more details

    Note: Some people have reported that WildFire CD Ripper or the system would crash when doing the auto detection procedure, they got around this problem by turning of the DMA setting in the Control Panel-> System -> Device Manager ->CD-ROM -> Your CD-ROM (press properties button and select the Settings TAB). Of course, don’t take Your CD-ROM literal, it means the brand/type of the CD-ROM which you want to perform the auto detect procedure.

    If WildFire CD Ripper is not still able to read audio data from your CD-ROM, please send us an e-mail, include the WildFire CD RipperAutoDetect.txt and add also the info you get from the System Info button (see also contact for more details what information is useful for me).
  • Q: When I convert/rip MP3 file, it takes a very long time, is there something wrong?
    A: The MP3 compression consumes a lot of computation time, actually, the lame encoder that’s used by WildFire CD Ripper is relatively fast compared to other MP3 encoders (with comparable sound quality, listen the output of the Xing ‘fast’ encoder, and you know what I mean). The ripping process can be slow; when you have Pentium 166-MMX, with 32 Mb of SD-RAM, a one minute song, takes about 2 minutes to rip and encode. With certain CD-ROM drives you might get better performance when you set the CD-SPEED to 32, but this might increase the change of jitter errors.
  • Q: File OLEAUT32.DLL is missing, what should I do?
    A: Normally this DLL should be present on your system, however I’ve got two cases where it was not, therefore you can download them here oleout32.zip Unzip the file and move it to the Windows/System directory. You can download this file here : http://members.tripod.com/~cd2mp3/Download/.
 

WildFire CD Ripper