[mythtv-users] Mytharchive: "Failed to run mythtranscode to remove unwanted segments"
John Pilkington
J.Pilk at tesco.net
Sat Oct 12 16:46:03 UTC 2013
On 12/10/13 16:03, Zig wrote:
>
> On 10/12/2013 6:10 AM, John Pilkington wrote:
>> On 12/10/13 09:40, John Pilkington wrote:
>>> On 12/10/13 01:28, Bob Shanteau wrote:
>>>
>>>> 2013-10-11 17:15:45 mythffmpeg -threads 2 -v 1 -i
>>>> "/var/lib/mytharchive/temp/work/1/newfile.mpg" -r ntsc -target ntsc-dvd
>>>> -b:v 2344k -s 352x480 -acodec copy -copyts -aspect 4:3
>>>> "/var/lib/mytharchive/temp/work/1/newfile2.mpg" -map 0:0 -map 0:1
>>>
>>> I don't see anything wrong with that command line, although the line
>>> break and html format at first appeared not to have a space after 4:3;
>>> there's no sign of a cutlist there, this is just a reencoding before
>>> going into mythtranscode to do the cut.
>>
>> Hmm. On reexamination it looks as if mythtranscode has been run, but
>> with no logged record of the command used. I think the questions
>> below are still pertinent.
>>>
>>> Can you play newfile.mpg? Can you run this line standalone? Are both
>>> -r ntsc and -target ntsc-dvd needed? See, for example,
>>>
>>> http://code.mythtv.org/trac/ticket/11297#comment:3
>>>
>>> As I've said repeatedly, I prefer to do all this sort of stuff outside
>>> mytharchive, but it ought to work :-)
>>>
>>> John P
>>>
> The attached patch will force mythburn.py to log the mythtranscode
> command line regardless of whether the command succeeds or fails.
> Ziggy
>
Yes, but... Here I think mythtranscode returned 'success' but
mythffmpeg can't process its output - which is in line with other recent
reports. Perhaps try cutting with Project-X if it's an mpeg2 recording;
I have used it inside mytharchive, although ususally I don't.
More information about the mythtv-users
mailing list