ffmpeg conversion

[artisticforge .]

hello

if you log the output of get_iplayer you can see the ffmpeg commands
being issued.

under Linux and Mac OSX the below is what i use.
<begin  quote>
#!/bin/bash

ddate=`date +%F`;
day=`echo ${ddate} | awk -F\- '{ printf( "%2.2d",  $3 ) }'`;
mth=`echo ${ddate} | awk -F\- '{ print $2 }'`;
yrs=`echo ${ddate} | awk -F\- '{ print $1 }'`;

date;
date
                     | tee -a
~/get_iplayer-logs/get_iplayer-3.02-pvr-radio-${yrs}${mth}${day}
~/get_iplayer-3.02/get_iplayer --verbose --type=radio --pvr
| tee -a ~/get_iplayer-logs/get_iplayer-3.02-pvr-radio-${yrs}${mth}${day}
date
                     | tee -a
~/get_iplayer-logs/get_iplayer-3.02-pvr-radio-${yrs}${mth}${day}
date;
<end quote>

This proves useful when the tagging operation fails under Linux I am
able to rerun the command under MacOSX.

On Sun, Sep 3, 2017 at 4:36 AM, RS <richard22j at zoho.com> wrote:
>> From: Nick Payne Sent: Sunday, September 3, 2017 04:23
>
>
>> What is the ffmpeg command that GiP uses to convert the ts downloads to
>> mp4? I occasionally find after downloading a program that for some reason
>> the conversion to mp4 has not happened and I only have the ts file. I can
>> convert this to mp4 with ffmpeg using the following command, but that takes
>> about 20 minutes to convert a one hour program downloaded using hlshd, and
>> so is obviously not the way the GiP does it.
>
>
>> ffmpeg -i input.ts -c:v libx264 -c:a copy -bsf:a aac_adtstoasc output.mp4
>
>
> Since about v2.99 for some modes get_iplayer has introduced the ability to
> resume failed downloads, and that includes failed remultiplexing from .ts to
> .mp4.  Just repeat the command with --force.  It includes HLS modes, and I
> think HVF as well.
>
> The reason your command is taking a long time is that -c:v lib264 is
> re-compressing the video in the file.  If you use -c:v copy only the
> container will be changed, and that is much faster as you have noticed when
> get_iplayer does it.
>
> I regard get_iplayer as an educational tool as well as performing the
> function it was written for.  I have often felt it would be useful if the
> commands passed to ffmpeg were displayed so we could learn to do it for
> ourselves.  It is of course possible to search through the code for the
> commands, but that takes a long time.
>


-- 
terry l. ridder ><>