EAC+Lame Logfile incorrect?
Reply #7 – 2004-01-07 01:47:46
Good to know; but it would be very helpful to have a logfile for the "endproduct" cause my experience is that in the compression is the dog burried (as you say in german ). I think many or even most of the problems appear during the compression process. Perhaps I have missed your point but it does post the info you seem to be after.Used output format : C:\Program Files\lame-3.90.3\lame.exe (LAME MP3 Encoder) 192 kBit/s Additional command line options : --alt-preset extreme A) C:\Program Files\lame-3.90.3 \ B) lame.exe C) (LAME MP3 Encoder) D) Additional command line options : --alt-preset extreme There are circumstances where this is not always applicable; one example is if one were using M.A.R.E.O. in this case it is easy to deduct what EAC used for encoding. Barring the use of a "Wrapper" application being used, with a bit of sleuthing around you can almost always figure out the encoder used by the cmd-line switches. Here is a log of mine when ripping to FLAC:Used output format : D:\Program Files\Exact Audio Copy\Encoders\flac-1.1.0-win\bin\flac.exe (User Defined Encoder) 320 kBit/s Additional command line options : -7 -V -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" -T comment="Plextor PX-40TS; EAC 0.95, Offset corrected, Gap Detected, Test & Copy." %s I have always used cmd-line encoders so it's hard to say whether the log says .mp3 when a dll is used, my opinion leans more toward it remaining as wav. As far as faking logs, I doubt that this issue is high on Andre’s list of priorities, The intention is for your own records. Take care, tec (Nothing against M.A.R.E.O. I'm only using it as an example)