Ok, thanks for version 0.10! Now I'm compressing my music with flac and found a few points that I dont like: I started flac to compress 15 files with "flac -V *.wav" Flac finished to compress the 15 files without problem. To check if Flac had problems with one of the files I had to scroll the screen up all the "XX% complete: frame YYY, wrote ZZZ ..." screen output. While flac compressed my WAVs I used X to write this mail and so. After flac had finished the job I changed to a virtual console but the <SHIFT> + <PG UP> combination did not worked. So I had to use flac with the -t argument again to see if all files were correct. This is a point I dislike. I wish to see per default (!) one or two output lines per file and not more! Something like: "FLAC is compressing file xyz.wav: now XX% done" is enough. FLAC produce similar output with the "-t" argument. If I want to see the complete output (which is now the default) it could be possible to give an "-information" argument. To see possible warning messages I started flac by tiping "flac -V -s *.wav". I hope FLAC will print warning messages although I used the "-s" argument?! Is'n it? One point to keep in mind for later after 1.0 releases: I wish that FLAC 2.0 (or whenever flac has a file-format-change) will accept (old) .flac files as input and write an output flac-file in the new 2.0 format. This will be to update all my old flac files to the new flac format in an easy way. congratulation, FLAC compressed my >1GB WAVs with no problems I hope you understand my bad english! Thank you! Jan
> Now I'm compressing my music with flac and found a few points that Idont like:> I started flac to compress 15 files with "flac -V *.wav" Flacfinished> to compress the 15 files without problem. To check if Flac hadproblems> with one of the files I had to scroll the screen up all the > "XX% complete: frame YYY, wrote ZZZ ..." screen output. While flac > compressed my WAVs I used X to write this mail and so. After flac had > finished the job I changed to a virtual console but the <SHIFT> + <PG > UP> combination did not worked. So I had to use flac with the -t > argument again to see if all files were correct. > This is a point I dislike. I wish to see per default (!) one or two > output lines per file and not more! Something like: > "FLAC is compressing file xyz.wav: now XX% done" > is enough. FLAC produce similar output with the "-t" argument. > If I want to see the complete output (which is now the default) it > could be possible to give an "-information" argument. >well, I don't put filename and stats on the same line because that will wrap on most people's terminals, then \r starts to not work and look ugly. but you should see only 2 lines per file, 3 with -V. I will think about an encode mode that shows just 'filename: status'. not sure about the keystroke problems but if you use -s it will be nice and silent unless there are verification (or other) errors.> To see possible warning messages I started flac by tiping "flac -V -s > *.wav". I hope FLAC will print warning messages although I used the > "-s" argument?! Is'n it? >yes, all warnings and errors are printed to stderr even when -s is on.> One point to keep in mind for later after 1.0 releases: I wish that > FLAC 2.0 (or whenever flac has a file-format-change) will accept(old)> .flac files as input and write an output flac-file in the new 2.0 > format. This will be to update all my old flac files to the new flac > format in an easy way. >I plan on keeping the format backward compatible for just this reason. I just didn't guarantee backward compatibility during beta because the basic format was still being hammered out. thanks for the info. Josh __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Matt Zimmerman wrote:> > On Fri, Jun 08, 2001 at 09:32:44PM +0000, Jan Suhr wrote: > > > "XX% complete: frame YYY, wrote ZZZ ..." screen output. While flac > > compressed my WAVs I used X to write this mail and so. After flac had > > finished the job I changed to a virtual console but the <SHIFT> + <PG > > UP> combination did not worked. So I had to use flac with the -t > > argument again to see if all files were correct. > > Note that this is a side effect of how the virtual console scrollback feature > works (I assume you are using Linux). It uses video memory to store the > previous lines, so they are lost when the video mode is changed. Something > along those lines. Anyway, this part isn't flac's fault. >If you are looking for some way to capture the output to a file, use the "tee" command. Essentially you'll want to run "flac <params> 2>&1 | tee flac.log". The "2>&1" will redirect stderr to stdout so they become one stream, then tee will save it to the file flac.log and output it to stdout as well. Lates.. Josh Green
On Fri, Jun 08, 2001 at 09:32:44PM +0000, Jan Suhr wrote:> "XX% complete: frame YYY, wrote ZZZ ..." screen output. While flac > compressed my WAVs I used X to write this mail and so. After flac had > finished the job I changed to a virtual console but the <SHIFT> + <PG > UP> combination did not worked. So I had to use flac with the -t > argument again to see if all files were correct.Note that this is a side effect of how the virtual console scrollback feature works (I assume you are using Linux). It uses video memory to store the previous lines, so they are lost when the video mode is changed. Something along those lines. Anyway, this part isn't flac's fault. -- - mdz