[mythtv-users] mythtranscode failure - deadlock detected
John Pilkington
J.Pilk at tesco.net
Sun Nov 16 23:04:29 UTC 2014
On 16/11/14 21:03, Alistair Grant wrote:
> Hi John,
>
> On Mon, Nov 17, 2014 at 6:28 AM, John Pilkington <J.Pilk at tesco.net> wrote:
>> On 16/11/14 10:45, Alistair Grant wrote:
>>>
>>> Hi,
>>>
>>> mythtranscode is failing with deadlock detected, see the log file below.
>>>
>>> I'm able to watch the recording within mythtv and using mplayer
>>> without any problems.
>>> ...
>>> 2014-11-16 21:32:15.728014 E Deadlock detected. One buffer is full
>>> when the other is empty! Aborting
>>
>>
>> Ticket #2077 from 2006. Probably a result of audio streams stopping or
>> starting unexpectedly.
>>
>> See, perhaps, (end of thread)
>>
>> http://www.gossamer-threads.com/lists/mythtv/users/579736#579736
>
> Thanks very much for your reply.
>
> I had seen this, but since my problem file only contains a single
> audio track I assumed that it was a different problem.
>
> However modifying rmExtraAudioStream.sh to not check the number of
> audio streams allowed mythtranscode to complete successfully, so I now
> have a (rather IO intensive) workaround. I've added the output from
> mythffmpeg -i to the end of the message in case it is useful to
> somebody.
>
> Thanks again,
> Alistair
>
Hi: I'm glad it worked. I may have been too specific about the cause
of the problem but it does seem to lie in stream-management.
I should perhaps say that I'm still using mythDVBcut, with demux and
sync correction by ProjectX, When Mike first posted his script I
wondered if ffmpeg would give as good a result; but I have seen nothing
to suggest that it doesn't, and it looks more convenient.
John
John
More information about the mythtv-users
mailing list