Hi all,

This is most likely an error with avconv, but as I'm using it it as part of get_player - I thought that someone here might know what is going on.

I'm getting a lot of errors of the type "Continuity check failed for pid 4095 expected 1 got 0 bitrate=1673.8kbits/s" after avconv is launched to encode the downloaded file. The outputted video plays fine.

This in turn is slowing down the time it takes to run my downloads.

It doesn't happen with all shows, just some. Still trying to work out what is the difference which triggers it.

Has anyone seen this before? Got any tips on speeding up the process?

Log file attached.

Thanks,

Dave

log.txt

You should expect those messages for some HLS streams with avconv, though you probably won't see those warnings with latest ffmpeg.  Unless there is a problem with playback, you can ignore them.  They do not slow down anything.  If your downloads seem slower than before (and this example is typical of your other downloads) it's most likely because your RTMP downloads are failing and you have configured get_iplayer to fall back to HLS, which can be slower (more network/DNS overhead for chunked downloads).

The do seem to be HLS downloads rather than RTMP, so that might explain it.

Maybe I should turn off verbose? That way I may not see the error messages, and as they say "out of sight, out of mind" :)

Thanks user-2!

Regards,

Dave

The warnings will still appear without --verbose.

From this page: https://libav.org/avconv.html

I see that avconv has different levels of logging

‘-loglevel loglevel | -v loglevel’

Set the logging level used by the library. loglevel is a number or a string containing one of the following values:

‘quiet’
‘panic’
‘fatal’
‘error’
‘warning’
‘info’
‘verbose’
‘debug’
‘trace’

Just a thought, but could the "quiet" option be set when launching avconv unless get_iplayer is run with --verbose, in which case it could be amped up to verbose or higher.

not a high priority of course, but something for the back log :)

cheers

Dave

No. It is a bad idea to suppress error messages. Plus, avconv won't print a progress display at loglevel warning or above.