eac3to - audio conversion tool

[r0lZ]

Yes. If you use that syntax, the error message is still printed in the command prompt window, and the log file contains only backspace and space characters.

The syntax I've described above eac3to test.dts test.ac3 1>log.txt 2>&1 is the way recommended by M$ to redirect stderr and stdout to the same file, and it works somewhat better: nothing is printed to the command prompt window. But the content of the log file is exactly identical than with your syntax. The message is lost in the two cases, and only the control characters are kept in the log.

[AYColumbia]

Why don't you just use the -log switch?

[r0lZ]

Originally Posted by AYColumbia

Why don't you just use the -log switch?

E:\>eac3to test.dts test.ac3 -log
Command line parameter "log" is unknown.

[LigH]

Maybe try LoRd_MuldeR's Logging Utility, it can log both stdout and stderr to the same file (and also does *not* confuse text editors with a bunch of "delete" characters = ^H, like the normal eac3to help output does).

[r0lZ]

Thanks for the suggestion, but that doesn't work. Again, the error message is not in the output of LoggingUtil.exe, regardless of the syntax and parameters used.

It seems that eac3to "knows" that its output is captured, and it modifies its formatting accordingly. I guess it suppress the error message by mistake (bug).

[LigH]

So, for example, which command line did you use with the logger?

There is a third method to output text: Manipulating the console output in the "graphic memory". Whatever that is in Windows NT... But that's quite unusual if a programmer once decides to use file output methods.

[heerschop]

Originally Posted by r0lZ

E:\>eac3to test.dts test.ac3 -log
Command line parameter "log" is unknown.

Try this command line:

e:\>eac3to test.dts test.ac3 -log="test.txt"

This writes the error in the log file:

eac3to v3.27
command line: C:\Tools\eac3to\eac3to.exe test.dts test.ac3 -log="test.txt"
------------------------------------------------------------------------------
Source file "test.dts" not found. <ERROR>

greetz

[r0lZ]

Yeah, -log works with the syntax above. Thanks heerschop.
Why that option and -progressnumbers are not documented is a mystery. But at least they exist.
Now, I would like to redirect the log to STDOUT instead of to a physical file, so that I can parse the output while eac3to is running. How can I do that with the -log option? I've tried -log=STDOUT and -log=-, but each time, a file is written to disc.

[LigH]

I wonder if -log="CON:" (with or without colon) may work. The "CON"sole was the combined device for stdin and stdout in good old MS-DOS times.

[r0lZ]

Well, indeed, you are right. Using CON: (with and without the quotes, and with and without the colon) seems to work. Indeed, no file is written to disc, and the message appears on screen. But... the original behaviour is back! The error message appears again with a red background, there are again a lot of BS and Space characters printed to STDOUT. More importantly, the error message disappears again if STDERR is redirected. In fact, it seems that the -log argument is totally ignored when CON: is used.

I think now that there is absolutely NO WAY to grab the error messages when eac3to is launched from another program. It's a very serious bug, and I suppose that we have to live with it. Pity!

@LigH: I'm sure that the error message is not simply hidden because a text editor is confused by the BS characters. I have used an hex editor to examine the outputs. Also, I can already parse the output of eac3to when it prints the stream information, for example. It is theoretically sufficient to remove all BS and tailing spaces to get a "normal" output. It's only the STDERR output that is wrong and cannot be processed properly.

Thanks to all of you.

[Kurtnoise]

Originally Posted by r0lZ

Anyway, using -log has a serious drawback. I have no way to distinguish the error message (if any) from the other messages. There is no leading string such as "ERROR:" to identify the line containing the error in the log.

This is not true...as soon as an error occurs, you have the <ERROR> string that appears.

[r0lZ]

OK, I think I have a working solution.
In fact, if you use the -log option, the log file is written to disc only at the end of the process (or when the process is aborted due to an error). But STDOUT still contains the normal messages (including the progress numbers when --progressnumbers is specified, as well as all that nasty BS and Spaces, that can be stripped out). Therefore, it is still possible to display the messages and update a progress bar while eac3to is working. Only the error messages are missing. But if the process returns a non-zero return code, you can then open the log file that has been written to disc, and search for the lines ending with "<ERROR>". They are the lines that are theoretically printed to stdout, but that are unavailable when STDOUT is redirected. It's a somewhat convoluted method, but it works.
Thanks again to everybody.

[EDIT] Kurtnoise has posted his message when I was writing mine and I was editing my previous message. Yes, <ERROR> is printed in the log at the end of the lines containing the error messages. I haven't noticed that when I did my first tests.

[stax76]

This and hoping for a fix is all we can do, I could read from a simple colored test app so it's possible.

[frenshprince]

Hello,

Coule you tell mi if its possible to use eac3to to convert a bluray playlist (mpls) with multiple m2ts to one m2ts ?

Of course I could use tsmuxer to do that, but I don't know why, it doen't work well' and the length of the m2ts is doubled.

Thanks

[Music Fan]

Originally Posted by frenshprince

Coule you tell mi if its possible to use eac3to to convert a bluray playlist (mpls) with multiple m2ts to one m2ts ?

Previous page ;
http://forum.doom9.org/showthread.ph...11#post1704811

[tebasuna51]

eac3to can extract the video to one mkv (or one video stream .h264/.vc1), can extract/recode the audio streams and extract subs.

But can't mux the streams to m2ts.

[frenshprince]

That's what I thought.

Thank you for your help.

[stinman]

Wil this program ever be able to decode TrueHD with Atmos or at least still decode TrueHD and disregard the atmos data like Lav Filters do? Or is there any way to get eac3to use the Lav Filters kind of like it will use the ArcSoft Decoders? I tried to put the Lav Filters in the folder with eac3to 3.27 and the HDDVD Bluray Stream Extracter to see if it would work. The only way to to extract a TrueHD atmos stream now is to run a MKV thru MakeMKV and out put the TrueHD atmos to flac, then the flac can be converted to wavs. I can't code like you guys can, if I could I would try and make eac3to use the new lav filters.

[Music Fan]

Originally Posted by frenshprince

That's what I thought.

You can use eac3to anyway to demux streams then use TSMuxer to remux in ts (or m2ts).

[tebasuna51]

Originally Posted by stinman

The only way to to extract a TrueHD atmos stream now is to run a MKV thru MakeMKV...

You can use also ffmpeg, search in this thread. Or better in ffmpeg syntax thread.

The problem was already reported to madshi.