Databases
StackOverflow2013
Postsdbo
POIs there a good way to tell if HandBrakeCLI actually encoded anything?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs there a good way to tell if HandBrakeCLI actually encoded anything?
    primarykey
    data
    text
    <p>I'm working on a system to convert a bunch of .mov files to H.264 (using HandBrakeCLI) and webm (using ffmpeg) as the .mov files are created. In general, things are going very well. I'm hung up on a bit of error detection. I want to know if one of the encodings failed so that we can investigate, try again, etc. </p> <p>To test encoding failure, I copied a text file into a file with a .mov extention, and set the programs about trying to encode it. Naturally, they both fail to encode the file (I'm not sure what "success" would mean in this context...) However, while ffmpeg reports this failure by setting its exit code to 1, HandBrakeCLI sets the exit code to 0, because it exited cleanly. This is consistent with the <a href="https://trac.handbrake.fr/wiki/CLIGuide" rel="nofollow">HandBrakeCLI documentation</a> but it leaves me wondering how I can tell if HandBrakeCLI knows if it failed to encode anything. That same documentation page suggests "If you want to monitor HandBrake's process, you should monitor the standard pipes", so I'm now getting the effect that I want by doing something like this: </p> <pre><code>HandBrakeCLI --preset 'Normal' --input bad.mov --output out.mv4 2&gt;&amp;1 | grep 'Encode done' </code></pre> <p>grep then sets its exit code to 0 if it found a match, and 1 if it didn't. But, this seems rather barbaric: for instance, the text "Encode done!" could change in a future release of HandBrake. </p> <p>So, anyone have a better way to tell if HandBrake encoded something or not? </p> <p>Some edited shell output is included below for reference...</p> <pre><code>$ ffmpeg -i 'develqueuedir/B_BH_120409.mov' 'develqueuedir/B_BH_120409.webm' FFmpeg version 0.6.4-4:0.6.4-0ubuntu0.11.04.1, Copyright (c) 2000-2010 the Libav Developers [snip] develqueuedir/B_BH_120409.mov: Invalid data found when processing input $ echo $? 1 $ HandBrakeCLI --preset 'Normal' --maxWidth 720 --optimize --input 'develqueuedir/B_BH_120409.mov' --output 'develqueuedir/B_BH_120409.mv4' Output format couldn't be guessed from file name, using default. [11:45:45] hb_init: starting libhb thread HandBrake 0.9.6 (2012022900) - Linux x86_64 - http://handbrake.fr Opening develqueuedir/B_BH_120409.mov... [snip] [11:45:45] libhb: scan thread found 0 valid title(s) No title found. HandBrake has exited. $ echo $? 0 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdavidreedernst
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs there a good way to tell if HandBrakeCLI actually encoded anything?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs there a good way to tell if HandBrakeCLI actually encoded anything?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am using HandBrakeCLI -Z iPod -i "test.avi" -o "test.mov" 1> /dev/null 2> grep "Encode done" && echo "this will only print if Encode done is found"
      singulars
      1. POIs there a good way to tell if HandBrakeCLI actually encoded anything?
      1. USJonas Oestman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload