Help - Search - Members - Calendar
Full Version: Comman prompt programs problem (LAME encoder)
Hydrogenaudio Forums > CD-R and Audio Hardware > CD Hardware/Software
slimer5
When I was trying to rip a cd for the first time with EAC, i saw that the LAME encoder command box was opening and then immediately closing less than a half second later. after seeing that it did this with each song, i checked the output folder after it completed and saw that only the .wav files were there and not the compressed mp3s.

this reminded me of a problem i used to have with programs that were based off a command box. they would do the same thing (open and then close right away)

so obviously this is probably not a problem with the LAME encoder, but i thought you guys could point me to a solution.

thanks for any help.
Cosmo
are you passing tag data via the command line?

QUOTE(the wiki)
Note on ID3 tagging: Lame will exit with an error if you try to write a non-standard genre to either of the ID3 tags. If you experience this issue, either remove --tg "%m" from, or add --ignore-tag-errors to the command line; or simply allow EAC to tag since it doesn't have this problem.

*supported genres

slimer5
QUOTE(Cosmo @ Nov 10 2007, 17:27) *

are you passing tag data via the command line?

QUOTE(the wiki)
Note on ID3 tagging: Lame will exit with an error if you try to write a non-standard genre to either of the ID3 tags. If you experience this issue, either remove --tg "%m" from, or add --ignore-tag-errors to the command line; or simply allow EAC to tag since it doesn't have this problem.

*supported genres



yes, but when i open the lame.exe file directly, it does it still.

i am using this command line:
-V 0 --vbr-new --add-id3v2 --ignore-tag-errors --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" %s %d

which was supplied by this site:
http://jiggafellz.isa-geek.net/eac
Cosmo
QUOTE(slimer5 @ Nov 10 2007, 17:34) *


yes, but when i open the lame.exe file directly, it does it still.



explain what that means
slimer5
QUOTE(Cosmo @ Nov 10 2007, 18:23) *

QUOTE(slimer5 @ Nov 10 2007, 17:34) *


yes, but when i open the lame.exe file directly, it does it still.



explain what that means


when i go to the folder its located in and double click the exe
Rio
Usually the DOS prompt box closes when the command line is too long (above the maximum characters for DOS, was it 255?), especially when ripping and encoding using std in/out.

Most probably you could change directories near to the root so as not to elongate directory structure (such as C:\MP3 rather than C:\Documents and Settings\My Name Is Too Long\My Documents\My Music...)

EDIT: Also, having that long command line switches (especially tags) contribute to the problem. Try only this (-V 0 --vbr-new %s %d), since EAC can add the tags even without the tag switches (-V 0 --vbr-new %s %d)
kmart
QUOTE(slimer5 @ Nov 11 2007, 00:58) *

QUOTE(Cosmo @ Nov 10 2007, 18:23) *

QUOTE(slimer5 @ Nov 10 2007, 17:34) *


yes, but when i open the lame.exe file directly, it does it still.



explain what that means


when i go to the folder its located in and double click the exe


If you go to the lame folder and double click lame.exe, it will open and close the command window because it is running without any arguments. (So it should just print a usage message and then exit.)

Cosmo
So, the genre descriptions you're using in EAC are confirmed as being supported by LAME ?

EDIT: nevermind, i missed the fact that you did include the ignore-tag-errors switch
verbajim
slimer5:
You must select "user defined encoder" in the compression options. I'm pretty sure that's the problem here.
slimer5
QUOTE(Rio @ Nov 10 2007, 20:23) *

Usually the DOS prompt box closes when the command line is too long (above the maximum characters for DOS, was it 255?), especially when ripping and encoding using std in/out.

Most probably you could change directories near to the root so as not to elongate directory structure (such as C:\MP3 rather than C:\Documents and Settings\My Name Is Too Long\My Documents\My Music...)

EDIT: Also, having that long command line switches (especially tags) contribute to the problem. Try only this (-V 0 --vbr-new %s %d), since EAC can add the tags even without the tag switches (-V 0 --vbr-new %s %d)


i will definitely try that, thanks for the tip

QUOTE(verbajim @ Nov 11 2007, 11:52) *

slimer5:
You must select "user defined encoder" in the compression options. I'm pretty sure that's the problem here.


i do have "use external program for compression" enabled in the "external compression" tab in compression settings.

so ill try using a shorter command line and ill let you know if this solves it.

thanks everyone.
slimer5
it seems that the problem is still happening even after shortening the line and saving it in a different folder with a smaller path. but, it also seems that its staying open a little longer... like a little more than a half a second.

any other ideas?
Cosmo
make sure to check the setting verbajim mentioned:

Parameter passing scheme: [ User Defined Encoder ]

setting it to "LAME MP3 Encoder" is a common mistake

also, on the same tab, you should enable "Check for external programs return code" - which should cause EAC to pop up an error message if the external encoder fails
slimer5
QUOTE(Cosmo @ Nov 12 2007, 07:44) *

make sure to check the setting verbajim mentioned:

Parameter passing scheme: [ User Defined Encoder ]

setting it to "LAME MP3 Encoder" is a common mistake

also, on the same tab, you should enable "Check for external programs return code" - which should cause EAC to pop up an error message if the external encoder fails


oh, i did not know that the "user defined encoder" was under the drop down menu, i thought he was referring to something else.

i will try this again and will report back.

thanks.
slimer5
it worked!

i thought the problem was going to stretch out further than a simple option change, but thankfully it did not. when setting up EAC i simply followed the guide that i linked earlier, so i guess they need to change that.

thank you to everyone who helped, i am very grateful.
greynol
You're better off following the information in the wiki here at HA.

It's clear to me that the author at jiggafellz does not fully understand the information he is presenting.

...but it appears that user defined encoder is definitely specified at that site.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.