Andavari what file needs to be copied to the EAC installation folder LAME.EXE or lame_enc.dll?
You can use either one. Or if you like you can put both of them in the EAC folder, you'd of course have to select which one you want to use in EAC.
I personally just use the .dll myself since there's no need to mess around with parameters.
Note: Many people use the .exe because it can write ID tags into the files, input replaygain tag's, and to have more/full control over the parameters used or to modify them to their own needs.
On the link you posted(to the guide) the author of the guide posts some Additional command line options
-V2 --add-id3v2 --pad-id3v2 --ignore-tag-errors --tt "%t" --ta "%a" --tl "%g" --ty "%y" --tn "%n" --tg "%m" %s %d
-V3 --add-id3v2 --pad-id3v2 --ignore-tag-errors --tt "%t" --ta "%a" --tl "%g" --ty "%y" --tn "%n" --tg "%m" %s %d
-V4 --add-id3v2 --pad-id3v2 --ignore-tag-errors --tt "%t" --ta "%a" --tl "%g" --ty "%y" --tn "%n" --tg "%m" %s %d
-V5 --athaa-sensitivity 1 --add-id3v2 --pad-id3v2 --ignore-tag-errors --tt "%t" --ta "%a" --tl "%g" --ty "%y" --tn "%n" --tg "%m" %s %d
Additional command line options are their to encode at a particular quality, and to automatically input compliant ID tag's using LAME.exe.
I'm not sure if I'm remembering this accurately/correctly or not, therefore I quote it: "EAC shouldn't be used to input ID3v2 tags, instead setup LAME.exe to input the tags via the LAME.exe parameter used"
I've personally never let EAC input any tags, I use Tag Frontend for all tagging.
he also states
-V2 ends up at around 190kbps on average
-V3 ends up at around 175kbps on average
-V4 ends up at around 160kbps on average
-V5 --athaa-sensitivity 1 ends up at around 135kbps on average"
That just shows the resulting average VBR bitrate. However depending upon what type of music you listen to the bitrate can easily bloat significantly, metal music usually makes the resulting average bitrate allot higher, I'm typically use to having 215 kbps or higher. Note: The encoder is smart enough to allow for a lower or higher average bitrate depending upon the source material, hence the reason to use the recommended VBR settings.
Does this mean my audio wont end up being 192kbs as i have selected in "Bit Rate:". Again thanks for all the help.
No you're files won't be what you've selected in EAC's clickable options, therefore they won't be 192 kbps. They will instead be what's been inputted into the parameter listed after LAME.exe, the parameter listed after LAME.exe is what the resulting encoded files will be. If you want 192kbps CBR files and not the recommended VBR files you'd use something like this (modify it to suit your needs):
lame.exe -b 192 %s %d
Edit: I noticed EAC burns audio cd's, anyone had good or bad experience with it or is burrrn beta?
EAC can burn audio CD's however it doesn't necessary support all writer drives. I've personally never used it. If you do decide to use it for burning audio CD's make sure you use a CD-RW for the testing purposes with your writer drive. Test it by opening "Tools > Write CD-R" then use the options "Create Offset Test CD" and "Detect Write Features" to make sure there's no problems.
By the way if you do want to burn audio CD's with EAC you need to download the EAC installation with CDRDAO included, I suppose this fixes the previous problems with EAC not supporting some writer drives. I however think Burrrn is the quickest and simplest approach to burning audio CD's.
------
If you're going to use LAME.exe I suggest you 'print->save to .txt' file the LAME.exe documentation/help files here's how:
1. Open Notepad
2. Input the following:
lame --help > "LAME Help.txt"
lame --longhelp > "LAME Long Help.txt"
lame --preset help > "LAME Preset Help.txt"
exit
3. Save as a batch file in the folder with LAME.exe, a good name would be:
Create LAME Help Files.bat
4. Run the batch file.
5. Now all or most of LAME's documentation will be available in the created .txt files for you to study.
