hi
Is there any difference between using the Windows mode & Dos mode of lame.
For eg.
Is there any difference where; encoding , - Speed etc ...is concerned between using
the dos & the windows mode of the Lame encoder here at Hydrogen ?
Can you'll comment....
Would appreciate your confirmation on it.....
Thanks
~~~~~~~~~
What is the Windows mode and the DOS mode?
AFAIK lame has only a Win32 command line interface
Hi.
I'll try to explain with this example...
Say I open the Dos Prompt and key in the commands to encode the file.
Here I'm opening it using Command.com
I could also encode by using Run on the start menu & filling in the
same command.
The above two ways aren't the same . are they ?
Run.., accesses lame in a different way. isn't it ?
So that's what I mean.....- by Windows mode
Thanks.
It is exactly the same thing
Hi.
I'll try to explain with this example...
Say I open the Dos Prompt and key in the commands to encode the file.
Here I'm opening it using Command.com
I could also encode by using Run on the start menu & filling in the
same command.
The above two ways aren't the same . are they ?
Run.., accesses lame in a different way. isn't it ?
So that's what I mean.....- by Windows mode
Thanks.
It's completely the same.
Though, if you really use command.com, not cmd.exe, some magic happens behind the scene, you can safely assume that these two ways are identical.
-Eugene
Yes actually, command.com is misleading. When it encounters a win32 application (such as lame.exe) it checks whether windows is running or not.
- If not, it displays "This program is win32 only blah blah"
- Otherwise, it tells windows (by system call in w9x, or by cmd.exe invocation in NT) to execute it.
It is exactly the same thing
how about any diff. of the Lame.dll used by many frontends and the lame.exe? I know both use the presets. But the dll seems not to support all switches?
It is exactly the same thing
how about any diff. of the Lame.dll used by many frontends and the lame.exe? I know both use the presets. But the dll seems not to support all switches?
You answered your own question.
Unless you are using unsupported presets or switches, the quality is the same.
What i means is IF THEY BOTH WORK WITH -APS, QUALITY IS THE SAME (of course, they most be the same version)
hi.
Thanks folks for the confirmations.
.....& stilling my paranoia..... :-)
hi.
just thought about one more thing...
when issued through the 'Run 'box, the console window closes after completion.
Is there any way to keep it open ?
When used from the Dos prompt it remains open after completion.
would much appreciate you'll could tell me how; if it is possible...to
keep it open while using Run...
thanks..
~~~~~~~~~~
Jan S, Gabriel ....hope you'll are around...
could you just clear the question in my last post....
> Is there any way to keep it open ?
Only if you open cmd.exe then run the LAME exe from within it. There's no guarantee that a front end (consider EAC one in this case) would use that window, though. EAC will tell Windows it wants to run LAME.exe which will open up a new cmd window. When encoding is complete, LAME will terminate and so will the cmd window. Due to this...you can't recycle the same cmd window. You could possibly create a pif file (there's an option to keep the window open when whatever program ends), but passing EAC wildcards to LAME through the pif probably won't work.
xen-uno
hi.
just thought about one more thing...
when issued through the 'Run 'box, the console window closes after completion.
Is there any way to keep it open ?
When used from the Dos prompt it remains open after completion.
would much appreciate you'll could tell me how; if it is possible...to
keep it open while using Run...
thanks..
~~~~~~~~~~
Just use a batch file and it'll stay open after it completes. For example use this line:
@for %%i in (*.wav) do lame --alt-preset standard "%%i"
appreciate the feedback & help.......