search

fongecore / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

Show encoder output on-screen #119

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
Rip a cd. :)

When I use an encoder, I'd like to be able to have an option to display the
encoding programs output somehow. I encode to flac using the -V option,
which checks that the encode was successful. But I can't see the output, if
it says OK or not. Also, something like the compression ratio is
interesting for the user that wants to see details.

I'm using 0.4.2, compiled from source. But I don't suppose it matters, as
this is more of a feature request.

Any thoughts?

Original issue reported on code.google.com by mar...@wustenberg.dk on 20 Sep 2007 at 6:47

GoogleCodeExporter commented 8 years ago 
I think you need to set verbose mode in the preferences. Perhaps I can extract 
some 
info from the output to show in the logfile.

Original comment by rubyripp...@gmail.com on 20 Sep 2007 at 8:31

GoogleCodeExporter commented 8 years ago 
Actually, both verbose and debug mode are on in my settings. I've started the 
GUI
from the shell, but it just shows the ripping process (which is nice, too), not 
the
encoding process.

I'm not sure what would be good in the logfile. Doesn't it depend too much on 
the
encoder used? Not everyone is a flac fan. :)

Original comment by mar...@wustenberg.dk on 20 Sep 2007 at 8:35

GoogleCodeExporter commented 8 years ago 
The listed encoders are intended to be supported, so this should be no problem. 
I'll see what I can do.

Meanwhile, when you want to see the output of the encoder, make sure you 
disable 
threaded encoding. Otherwise the ripping will overwrite the output of the 
encoder. 
I'll look for a more elegant solution in the future.

Original comment by rubyripp...@gmail.com on 20 Sep 2007 at 8:48

GoogleCodeExporter commented 8 years ago 
The encoders are now visible when started from a terminal when verbose is 
checked. 
Also you will be noticed in the logfile if one of the encoders failed. To 
include 
the console output in the main program is not a good idea in my opinion. 
Therefore, 
I'm closing the issue.

If you need anything more, file a new issue please.

Original comment by rubyripp...@gmail.com on 29 Dec 2007 at 3:40