[MP3 ENCODER] (Fwd) Re: question
About joint stereo and stereo with EAC and LAMe_DLL >CBR with bitrates higher 128 (means : 160,192...) are stored as stereo, >lower or equal 128 are stored with joint stereo... as the coder told me Cavallo de Cavallis <[EMAIL PROTECTED]> =-=--=--=--=--=--=--=--=--=--== = http://www.s0ftpj.org = = Digital Security for y2k = ==-=--=--=--=--=--=--=--=--=-== "Knowledge chases me, but i'm faster" "La Sapienza mi insegue, ma io sono piu' veloce" [Anonymous] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] Re: highq mode
oh one stupid suggestion for the stand alone executable : it could be a good idea to allow "| more" or "/page" or " file.asc" to see the command help, now it "goes away" without seein the beginning of it Learn your shell; the output is going to stderr, not stdout. You're only redirecting stdout. (If/when telling LAME to send it's output to stdout, you'd then collide with the usage outout and never see it). I know my shell, it cant handle that, so i suggested to modify lame on win32based system. btw i suggested it to see the command help so when no params are passed Simply use a better Computer or at least install an Operating System on your Inhell-Device. Wow what a f**kin useful remark !! so stop compiling lame for windows if u think it's useless. i gave my 2 cents, my world wont change if no one modify this, i have still my eyes to look at the commandline reference, but it could be an aid for future users. Cya Cavallo de Cavallis [EMAIL PROTECTED] =-=--=--=--=--=--=--=--=--=--== = http://www.s0ftpj.org = = Digital Security for y2k = ==-=--=--=--=--=--=--=--=--=-== "Knowledge chases me, but i'm faster" "La Sapienza mi insegue, ma io sono piu' veloce" [Anonymous] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] Re: highq mode
On Fri, 4 Feb 2000, Cavallo de Cavallis wrote: Learn your shell; the output is going to stderr, not stdout. You're only redirecting stdout. (If/when telling LAME to send it's output to stdout, you'd then collide with the usage outout and never see it). I know my shell, it cant handle that, so i suggested to modify lame on win32based system. btw i suggested it to see the command help so when no params are passed My shell is broken, please add extra cruft to your application to work around my problem. You can get bash for win32. Wow what a f**kin useful remark !! so stop compiling lame for windows if u think it's useless. I don't think that any of the lame developers did the windows compiling. i gave my 2 cents, my world wont change if no one modify this, i have still my eyes to look at the commandline reference, but it could be an aid for future users. Thanks. -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] Re: highq mode
Actually you can extend a Win95/98 DOS window to 43 or 50 lines which then allows scrolling up. It is in the Properties/Screen tab. It doesn't completely help because there are more than 50 lines printed. It goes back as far as "--lowpass freq". I have the same problem. I have become rather skilled at hitting the Pause button at roughly the right time. Ross. Mark Stephens wrote: BTW, in NT you can specify a scroll back buffer for the command line window. You can also make it as many lines that can fit on the screen, so this is really only an issue for win95/98 users. -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
[MP3 ENCODER] lame command line usage (was: Re: highq mode)
MoiN On Fri, Feb 04, 2000 at 07:54:19PM +0100, Cavallo de Cavallis wrote: oh one stupid suggestion for the stand alone executable : it could be a good idea to allow "| more" or "/page" or " file.asc" to see the command help, now it "goes away" without seein the beginning of it Learn your shell; the output is going to stderr, not stdout. You're only redirecting stdout. (If/when telling LAME to send it's output to stdout, you'd then collide with the usage outout and never see it). I know my shell, it cant handle that, so i suggested to modify lame on win32based system. btw i suggested it to see the command help so when no params are passed According to the GNU coding standards, a program should have the option "--help" to "output brief documentation for how to invoke the program, on standard output, then exit successfully."[1] I suggest to change lame to use this option. If you call lame without any arguments, this is considered an error, so lame should display only a brief message which points the user to the "--help" option. I have modified the latest CVS version to print a few lines to stderr if called with no arguments and to print the usage to stdout if called with "--help". Thus I had to modify display_bitrates() to take an argument which filehandle to use. I have also added the option "--help" to the usage. The last change I did was stop the option processing when an unrecognized gnu-style option was found. I have attached my changes as diff, if you want to have a look at them. Ingo [1] http://www.gnu.org/prep/standards_14.html#SEC14 -- Not bad but bad enough... lame.diff.gz
Re: Re[3]: [MP3 ENCODER] highq mode
At 17:13 03/02/00 -0600, you wrote: oh one stupid suggestion for the stand alone executable : it could be a good idea to allow "| more" or "/page" or " file.asc" to see the command help, now it "goes away" without seein the beginning of it Yes, that would be very useful, especially for Windows where you cannon scroll up to see the beginning of the help. For Linux this is less important, because of the possibility to scroll up and down. Can windows users redirect stderr like us poor saps stuck using Free Software? Maybe he can try "lame 2 file.asc more file.asc". Well, it works here on OS/2 anyway. Dont know about Windows. Windows Command.com does not support stderr redirection AFAIK, but if you use 4DOS from JPSoftware you can write: Lame | more or better "Lame | List /s" -- Jose Mejuto http://www.cdngo.com CD Audio ripper compressor -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] Pausing output to STDERR
If you use 4DOS as your command processor with win9X you can redirect STDERR to STDOUT and thus pause it. For example "" redirects both STDOUT STDERR while "|" will pipe both. There are heaps of other features that still make 4DOS the best thing for the CLI junkie under Win9x. -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] LAME in the PRESS
I agree in that encoding in CBR opposed to VBR gives me a feeling of being more safe :) I wonder where the myth that joint stereo would somehow adversely affect quality comes from. Was it the web pages from the BladeEnc guy? Actually, it was this mailinglist. I think Mark Taylor (correct me if I'm dead wrong!) said something like: "at high bitrates, joint stereo can do more evil than good, because the algorithm [of detecting similarities in the left/right channels] is not perfect". we all know this, but just to clarify: jstereo means the encoder is free to choose between regular (l/r) stereo or mid/side stereo for each frame. I think mid/side stereo will always improve quality when the left and right channels are similar. In that case, the mid channel is more important than the side channel and allocating more bits to the mid channel will effectively increase the bandwidth. But there are two problems I've seen with mid/side stereo: If the L and R channels are very different (and thus there is a lot of information in the side channel), encoding in mid/side stereo will creates problems, since noise in either mid or side channel will be spread to both the L and R channels. Check out mstest.wav on the lame web page for an example. If this is coded with mid/side stereo, you will get some very noticeable artifacts. So lame only tries to use mid/side stereo when the L and R channels are very similar. The second problem I've seen is too much switching: if lame switches back and forth between mid/side and regular L/R, the switching itself can create artifacts. The question is, when do the benefits of mid/side stereo outway the negatives? Until someone figures out the answer to that question, we'll just take what the FhG encoder does as the gospel truth: use mid/side stereo only for 128kbs and less. Mark -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] LAME CRASHES / LAME in the PRESS
From: "Cavallo de Cavallis" [EMAIL PROTECTED] Organization: S0ftPr0J3cT www.s0ftpj.org Date: Thu, 3 Feb 2000 13:35:40 +0100 so blade sucks in such evident way ? Yes. I is like lame without the patches ;) Please read the lame changelog, just the patches in the last year affecting quality. Yes but i thought XING was the worst one The early free version of Xing (tompg?) really did suck. Maybe they also started with the ISO dist10 code, and their first version was just a clean up and speedup of dist10. Their latest encoder is much better, but Xing's reputation has not yet recovered! Mark -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] lame command line usage (was: Re: highq mode)
I have modified the latest CVS version to print a few lines to stderr if called with no arguments and to print the usage to stdout if called with "--help". Thus I had to modify display_bitrates() to take an argument which filehandle to use. I have also added the option "--help" to the usage. The last change I did was stop the option processing when an unrecognized gnu-style option was found. I have attached my changes as diff, if you want to have a look at them. Ingo Hi Ingo, It looks like your changes have already been added to CVS. But on my system (RH5.2 linux), the line stderr = stdout gives an 'invalid lvalue' error. Any suggestions? I've temporarily commented it out for now. -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] lame command line usage (was: Re: highq mode)
It looks like your changes have already been added to CVS. But on my system (RH5.2 linux), the line stderr = stdout gives an 'invalid lvalue' error. stdin, stdout, stderr are not guaranteed to be valid lvalues by ANSI, and in glibc, they are not. The above line is not legal C. -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] lame command line usage (was: Re: highq mode)
"Ingo" == Ingo Saitz [EMAIL PROTECTED] writes: Ingo I have modified the latest CVS version to print a few lines Ingo to stderr if called with no arguments and to print the usage Ingo to stdout if called with "--help". On my linux machine, gcc says "invalid left hand value" and fails to compile this code :) --- Takehiro TOMINAGA // may the source be with you! -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
