EMER is a multiple encoders launcher for Exact Audio Copy (EAC). It is basically a "fake encoder" that has the ability of calling multiple encodes, creating multiple encoded files from a single track extraction. This is is very usefull for example, if you need to encode all (or some) of your CDs to Ogg Vorbis for archival, and also to MP3 for use with your MP3 player (when would iRiver support Ogg Vorbis?). While you can rip an entire CD with EAC to wav, and then run multplie encoders on them, EMER can do multiple encodes after each track EAC has riped! It is my humble contribution to the great Hydrogenaudio comunity, to whom it is dedicated, and also to the EAC, CDex, Foobar, Ogg Vorbis and LAME developers, and to Borland, for Delphi and Kylix, my loved programming environments.
It is very easy to set up:
1) Download EMER from Emer Home Page (ony 30 kilobytes!):
2) Uncompress it under EAC's folder.
3) Set EAC Compression Options (F11) as follows::
........ Program, including path, used for compression: emer.exe
........ Parameter passing scheme: User Defined Encoder
........ Additional command line options: '%o' '%s' '%d' "%a" "%g" "%t" "%n" "%y" "%m" "any comments?"
(NOTE that %o, %s and %d are sourrounded with (') and the rest with ("). Don't ask me why, but EAC does something weird with the command line, and this is the way it works)
This way, after EAC finishes ripping a track, it would run EMER, passing it, on the command line, in this order: Original_Filename (without temporary renaming) ... Source_Filename ... Destination_Filename ... CD artist ... CD title ... Track title ... Track number ... Year ... MP3 music genre ... Any comments you want to add.
EMER would then read the emer.ini file that should be located where emer.exe is, and for each ACTION LINE (an Action Line is any line that does not starts with a
, would replace all the LITERALS (specials strings codes that EMER recongnizes and that start and end with @) with the correct values, and would then execute the encode command.HERE IS THE LIST OF LITERALS THAT EMER ACTUALLY RECOGNIZES AND THE VALUES THEY REPRESENT :
@original@ ==[would be replaced with]==> Original_Filename (without temporary renaming) (Parameter Number 1)
@source@ ==[would be replaced with]==> Source_Filename (Parameter Number 2)
@dest@ ==[would be replaced with]==> Destination_Filename (Parameter Number 3)
@artist@ ==[would be replaced with]==> CD artist (Parameter Number 4)
@cdname@ ==[would be replaced with]==> CD title (Parameter Number 5)
@songname@ ==[would be replaced with]==> Track title (Parameter Number 6)
@track@ ==[would be replaced with]==> Track number (Parameter Number 7)
@year@ ==[would be replaced with]==> Year (Parameter Number 8)
@genre@ ==[would be replaced with]==> MP3 music genre (Parameter Number 9)
@comments@ ==[would be replaced with]==> Any comments you want to add. (Parameter Number 10)
@11@ ==[would be replaced with command line paramenter number]==> 11
.. ==[would be replaced with command line paramenter number]==> ..
@xx@ ==[would be replaced with command line paramenter number]==> xx
@emerpath@\ ==[would be replaced with ]==> the full path to EMER, WITHOUT the the *ending* backslash (\) *
@fullname@ ==[would be replaced with ]==> the full temporal name WITH the new extension
@pathonly@ ==[would be replaced with ]==> the full temporal path, WITHOUT the *ending* backslash (\)
@nameonly@ ==[would be replaced with ]==> the new temporal name, WITHOUT any extension
@extonly@ ==[would be replaced with ]==> the new extension WITHOUT the dot
* It is not required to use @emerpath@, as a fully qualified path name can be used.
As i said, the "ACTION LINES" are the actual commands EMER would run (after replacing all the LITERALS as described above). An Action Line must contain:
Extension_Of_The_Encoded_File Text_Between_Finall_Encoded_Name_And_.Extension The_Command_To_Run_With_Parameters
** Extension_Of_The_Encoded_File: if, for example, the encoder produces ogg files, this should be ogg.
** Text_Between_Finall_Encoded_Name_And_.Extension: this is used to add some text to the final name of the enconded file name, and file extension, for example. It is used if you want to encode with the same encode, but with diferent qualities. For example, suppose you want to encode with LAME, in Extreme and Insane qualities, the file "mana_song1.wav". EAC and EMER would try to generate two "mana_song1.MP3" files, which is not posible, so, if we define the text_between_finall_encoded_name_and_.extension of the second Action Line to be _extreme, EMER would rename this file to "mana_song1_extreme.MP3"! VERY IMPORTANT: if you don't want to add text between the file name and the file extension, put NONE, but you must include anything.
The_Command_To_Run_With_Parameters: this is the real command that EMER would execute, after replacing all the LITERALS with the correspongin values.
** used internally by EMER.
A REAL USE EXAMPLE:
Suppose that our INI file contains this 2 Action Lines:
mp3 NONE "@emerpath@\lame.exe" --alt-preset standard -Z @source@ @dest@
ogg NONE @emerpath@\oggenc.exe --quality 5 @source@ --output=f"@dest@"
and that we are ripping the song: Emma Shapplin - Etterna - 12 - La Notte Etterna.wav
EMER would take the 1st Action Line:
mp3 NONE "@emerpath@\lame.exe" --alt-preset standard -Z @source@ @dest@
convert it to:
"c:\watever\lame.exe" --alt-preset standard -Z c:\xxx\abreviated_song_name.wav c:\xxx\abreviated_song_name.mp3
and then execute it.
Then, it would take the Action Line:
ogg NONE @emerpath@\oggenc.exe --quality 5 @source@ --output=f"@dest@"
convert it to:
"c:\watever\oggenc.exe" --quality 5 c:\xxx\abreviated_song_name.wav --output=f"c:\xxx\abreviated_song_name.ogg"
At this point, he would rename the file c:\xxx\abreviated_song_name.ogg to Emma Shapplin - Etterna - 12 - La Notte Etterna.OGG.
EMER would then terminate, and pass control back to EAC, who, in turn, would rename c:\xxx\abreviated_song_name.mp3 to Emma Shapplin - Etterna - 12 - La Notte Etterna.MP3.
INI File:
On the INI file, i have put settings for Ogg Vorbis, LAME MP3 and MPC for practicall and exemplary use.
TESTING:
EMER has been developed and tested under Windows 2000. I would really apretiate confirmation that it runs on XP, NT, 95, 98, ME.
Portable MPC player ! Where's it I'm ordering one.
):