MP4Box -info doesn't appear to be on stdout. Can't redirect to file or capture in scripts

[Eric Morgan]

I have scripts that use MP4Box -info to grab video details like resolution. They have stopped working because the backticks no longer capture the out of the -info. I also can't redirect the output to a file using MP4Box -info file.mp4>text.txt. The info is displayed on the terminal and the text.txt is empty.

[Ralf Herold (ralf-herold)]

Try MP4Box -info <filename> 2>&1 | grep <what_to_find> and / or MP4Box -info <filename> &> <name_of_file_to_save_into>. This redirects stderr to stdout, where it can be captured.

[Joe (exekutive)]

the output of stderr is really ugly. It looks like

[0mImporting AVI Video: | | (01/100)
Importing AVI Video: | | (02/100)
Importing AVI Video: | | (03/100)
Importing AVI Video: | | (04/100)
Importing AVI Video: |= | (05/100)
Importing AVI Video: |= | (06/100)
Importing AVI Video: |= | (07/100)
Importing AVI Video: |= | (08/100)
Importing AVI Video: |= | (09/100)
Importing AVI Video: |== | (10/100)
Importing AVI Video: |== | (11/100)
Importing AVI Video: |== | (12/100)
Importing AVI Video: |== | (13/100)
Importing AVI Video: |== | (14/100)
Importing AVI Video: |=== | (15/100)
Importing AVI Video: |=== | (16/100)
Importing AVI Video: |=== | (17/100)
...

As the OP has mentioned, MP4BOX needs to output info in a more compliant way.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.