On Sat, 12 Jul 2014 19:17:52 +0100 dinkypumpkin <[email protected]> wrote:
> On 11/07/2014 16:20, [email protected] wrote: > > Is there a hack to workaround this? I've done the above many times, > > No. If rtmpdump receives garbage, there is nothing it - or you - can > do about it. If you're the same Nick as the OP, then you already > know the solution: use the alternate CDN. Nope, a different Nick. > The video files must be edited frame-wise, not byte-wise. Before > resuming a download, rtmpdump looks for the last frame boundary as a > splice point. You could use an editor to cut the file on an I-frame > boundary, but I have no idea if that will help. I had concluded it was definitely more complicated than simple byte count, I might well have a look into an editor that can work with video > > You can try using --start and splicing the pieces together yourself. > However, "sanity failed" errors usually appear at the beginning of > the download before much content has been downloaded, so you'll waste > less time by just deleting the partial download and starting over. > You can also supply a single value to --modes and use --attempts=1 to > avoid unnecessary retries and a bunch of "corrupt file" warnings when > rtmpdump attempts to resume the download. Thanks for the ideas, I'll bung a few things in the options file and see if the odd weird-out becomes less of a problem (not that they really are, I just kinda asked in passing). Nick _______________________________________________ get_iplayer mailing list [email protected] http://lists.infradead.org/mailman/listinfo/get_iplayer
