Skip to main content

Topic: EAC/LAME configuration issue? (Read 3011 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • macarser
  • [*]
EAC/LAME configuration issue?
I searched through the previous posts in hopes for an answer but didn't see one so was hoping someone could help me.

I always use the combo of EAC and LAME to make mp3's out of my store bought CD's, however normally using LAME through EAC has always resulted in mp3's with nothing but silence in them, no sound, so I had to run WinLAME manually and do it that way.

I have recently gotten a new machine and so re-installed EAC and LAME/WinLAME, but now even the WAV files ripped from EAC are coming up with nothing but silence, there's no sound, nothing that triggers anything in the visualizations.

Is there some sort of setting I have configured wrong, or has anyone else but me seen this before?

Thank you!

  • Supernaut
  • [*][*][*]
EAC/LAME configuration issue?
Reply #1
I've had that happen when using the Native Win32 interface for WinNT/2000/XP. Installing an external ASPI interface solved the problem.

  • macarser
  • [*]
EAC/LAME configuration issue?
Reply #2
Quote
I've had that happen when using the Native Win32 interface for WinNT/2000/XP. Installing an external ASPI interface solved the problem.
[a href="index.php?act=findpost&pid=317222"][{POST_SNAPBACK}][/a]

I already did have ASPI 4.60 Layer in Windows installed, and EAC is configured for "Installed external ASPI interface".  Per your suggestion I went and installed ForceASPI 1.7 and am still getting the same results, although honestly I could not actually specify in EAC which to use, so it may still be using the wrong one. :/

I noticed an unavailable option in EAC which are the ASPI drivers for VOB Instant CD/DVD, yet it appears this product is no longer available.  Was EAC support for this never upgraded to Pinnacle's newer product line?
  • Last Edit: 01 August, 2005, 05:59:54 PM by macarser

  • kheops
  • [*][*]
EAC/LAME configuration issue?
Reply #3
double check that the read features are correct for your drive, also, check the "drive read command" setting or autodetect it once again

+