[mythtv-users] "Unable to find 2021_20131216000000.mpg.tmp in HandleDeleteFile()"

John Pilkington J.Pilk at tesco.net
Wed Dec 18 22:47:04 UTC 2013


On 17/12/13 08:54, John Pilkington wrote:
> On 16/12/13 22:12, A. F. Cano wrote:
>>
>> Hello,
>>
>> I tried to transcode from within myth ("m"->Job Options->Begin
>> Transcoding->
>> Low Quality-><ENTER>) and I got this:
>>
>>
>> 2013-12-16 16:22:53.994272 I  JobQueue: Transcode Starting for "60
>> Minutes": Low Quality (6.8 GB)
>> 2013-12-16 16:22:54.000954 I  New DB connection, total: 10
>> 2013-12-16 16:22:54.044489 I  New DB connection, total: 10
>> 2013-12-16 16:22:56.672400 I  MainServer::ANN Monitor
>> 2013-12-16 16:22:56.672437 I  adding: tashi as a client (events: 0)
>> 2013-12-16 16:22:56.673880 I  MainServer::ANN Monitor
>> 2013-12-16 16:22:56.673907 I  adding: tashi as a client (events: 1)
>> 2013-12-16 16:22:57.072554 I  MainServer::ANN Monitor
>> 2013-12-16 16:22:57.072568 I  adding: tashi as a client (events: 0)
>> 2013-12-16 16:22:57.073153 I  MainServer::ANN Monitor
>> 2013-12-16 16:22:57.073165 I  adding: tashi as a client (events: 1)
>> 2013-12-16 16:22:58.652535 E  Unable to find
>> 2021_20131216000000.mpg.tmp in HandleDeleteFile()
>> 2013-12-16 16:23:00.264029 I  JobQueue: Transcode Errored: "60
>> Minutes": Low Quality (exit status 255, job status was "Errored")
>>
>> This is possibly a permissions issue, but the recording worked just
>> fine and
>> resulted in these files (./ included just in case - user afc is in group
>> mythtv)
>>
>> drwxr-xr-x 2 afc afc 4.0K Dec 16 16:29 ./
>> -rw-rw-rw- 1 afc afc  98K Dec 16 16:22 2021_20131216000000.mpg.png
>> -rw-r--r-- 1 afc afc 6.8G Dec 15 20:00 2021_20131216000000.mpg
>>
>> Since I have / (and /tmp) in a separate partition with only 1.5G
>> available,
>> and I found a setting Setup->General for "Screen shot path" that was
>> set to
>> /tmp, (this was the only /tmp path I found) I set it to /var/tmp that
>> has more than enough space to hold twice the above file.  It didn't make
>> any difference, so it's not an issue of not finding enough space to hold
>> the file.  Or is it and I didn't find the place where temp storage is
>> set for the transcode operation?
>>
>> Any hints/ideas out there? What's causing transcode to fail?
>>
>> Thanks.
>>
>> Augustine
>
> IIRC that .tmp file should later be renamed as the original;  I think it
> should be in the recordings storage group.  Have you looked for
> *.mpg.tmp files there?
>
> I think MythTV is going to be a struggle until you can give it more
> capable hardware, especially since you can only record in HD.  But you
> know that...
>
> And I wouldn't be surprised if this is another UTC-related filename
> problem.
>
> John P

As far as I can see no-one else has touched on the part of your posts 
that asked about reducing the dimensions of your picture.  I quoted an 
mythffmpegf/ffmpeg command line that works for me but uses pal options; 
your variant didn't work for you, and it appears that you have tried one 
of the backend 'transcoder' options.  The only one of those that I have 
used, and that not recently, is lossless mpeg.

I've just looked at the other transcoding options in mythtvsetup, and I 
got a shock.  It isn't clear to me what your defaults would be, or 
whether you have used non-default values.  I don't know what I would 
choose, and I would be surprised if anyone has tried it or updated it 
recently.  It looks to me to be a relic from the non-digital era.  If 
someone steps forward who really does use it, or if you have now 
persuaded it to do what you want, fine. Otherwise I wouldn't spend more 
time on it.  But it's your choice....

And a more general comment/query:  I hadn't looked at the mythtvsetup 
options earlier because doing that properly needs a non-running backend 
and carries the risk of making unwanted and untracked changes.  Is there 
a better way of exploring it?

John






More information about the mythtv-users mailing list