Mailing List Archive: MythTV: Users

Interrupted commercial detection

Index | Next | Previous | View Threaded

jan at horde

May 30, 2012, 1:26 AM

Post #1 of 5 (374 views)
Permalink

Interrupted commercial detection

Is anybody else seeing the commercial detection being interrupted a
lot in recent 0.25-fixes?

From the gut I'd say that in 1 of 4 cases the job stops with
"decoding error eno: Input/output error (5)". It's not an intermittent
issue, re-running the detection job stops at the same point. It
usually happens while in the 90%ies. It *could* be at the place where
I usually have frame drops that have been reported at lot, during
program changes or starting another recording. But that's rather
guessing. I also have "AFD: Unknown audio decoding error" during the
detection, but those don't seem to do any harm.

This never happened before in years for me, and it didn't happen right
after upgrading to 0.25 either.

--
Jan Schneider
The Horde Project
http://www.horde.org/

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

support at drdos

May 30, 2012, 2:33 AM

Post #2 of 5 (364 views)
Permalink

Re: Interrupted commercial detection [In reply to]

Jan Schneider wrote:
> Is anybody else seeing the commercial detection being interrupted a
> lot in recent 0.25-fixes?

In recent fixes? No, since I've moved to .25, yes. Lots of, "Failed
with exit status 140". Goto MythWeb or the mythfrontend and launch
commercial detection again and most of the time, it'll succeed.

Doug

--
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

May 30, 2012, 7:19 AM

Post #3 of 5 (362 views)
Permalink

Re: Interrupted commercial detection [In reply to]

On 05/30/2012 04:26 AM, Jan Schneider wrote:
> Is anybody else seeing the commercial detection being interrupted a
> lot in recent 0.25-fixes?
>
> From the gut I'd say that in 1 of 4 cases the job stops with "decoding
> error eno: Input/output error (5)". It's not an intermittent issue,
> re-running the detection job stops at the same point. It usually
> happens while in the 90%ies. It *could* be at the place where I
> usually have frame drops that have been reported at lot, during
> program changes or starting another recording. But that's rather
> guessing. I also have "AFD: Unknown audio decoding error" during the
> detection, but those don't seem to do any harm.
>
> This never happened before in years for me, and it didn't happen right
> after upgrading to 0.25 either.
>

There's a "known" issue (with an unknown cause) that results in
"near-real-time commercial detection" hitting the end of the file. If
you either disable "Start auto-commercial-detection jobs when the
recording starts" in mythtv-setup or re-run commercial detection after
the recording finishes, detection should be as reliable as it was in
0.24-fixes.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

adeffs.mythtv at gmail

May 30, 2012, 10:05 AM

Post #4 of 5 (356 views)
Permalink

Re: Interrupted commercial detection [In reply to]

On Wed, May 30, 2012 at 10:19 AM, Michael T. Dean
<mtdean [at] thirdcontact> wrote:
> On 05/30/2012 04:26 AM, Jan Schneider wrote:
>>
>> Is anybody else seeing the commercial detection being interrupted a lot in
>> recent 0.25-fixes?
>>
>> From the gut I'd say that in 1 of 4 cases the job stops with "decoding
>> error eno: Input/output error (5)". It's not an intermittent issue,
>> re-running the detection job stops at the same point. It usually happens
>> while in the 90%ies. It *could* be at the place where I usually have frame
>> drops that have been reported at lot, during program changes or starting
>> another recording. But that's rather guessing. I also have "AFD: Unknown
>> audio decoding error" during the detection, but those don't seem to do any
>> harm.
>>
>> This never happened before in years for me, and it didn't happen right
>> after upgrading to 0.25 either.
>>
>
> There's a "known" issue (with an unknown cause) that results in
> "near-real-time commercial detection" hitting the end of the file. �If you
> either disable "Start auto-commercial-detection jobs when the recording
> starts" in mythtv-setup or re-run commercial detection after the recording
> finishes, detection should be as reliable as it was in 0.24-fixes.
>
> Mike

is there an "easy" way to get failed flags to be re-added to the queue
until this issue is figured out?

--
Steve
http://www.mythtv.org/wiki/User:Steveadeff
Before you ask, read the FAQ!
http://www.mythtv.org/wiki/Frequently_Asked_Questions
then search the Wiki, and this list,
http://www.gossamer-threads.com/lists/mythtv/
Mailinglist etiquette - http://www.mythtv.org/wiki/Mailing_List_etiquette
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

jan at horde

May 31, 2012, 3:13 AM

Post #5 of 5 (346 views)
Permalink

Re: Interrupted commercial detection [In reply to]

Zitat von "Michael T. Dean" <mtdean [at] thirdcontact>:

> On 05/30/2012 04:26 AM, Jan Schneider wrote:
>> Is anybody else seeing the commercial detection being interrupted a
>> lot in recent 0.25-fixes?
>>
>> From the gut I'd say that in 1 of 4 cases the job stops with
>> "decoding error eno: Input/output error (5)". It's not an
>> intermittent issue, re-running the detection job stops at the same
>> point. It usually happens while in the 90%ies. It *could* be at the
>> place where I usually have frame drops that have been reported at
>> lot, during program changes or starting another recording. But
>> that's rather guessing. I also have "AFD: Unknown audio decoding
>> error" during the detection, but those don't seem to do any harm.
>>
>> This never happened before in years for me, and it didn't happen
>> right after upgrading to 0.25 either.
>>
>
> There's a "known" issue (with an unknown cause) that results in
> "near-real-time commercial detection" hitting the end of the file.
> If you either disable "Start auto-commercial-detection jobs when the
> recording starts" in mythtv-setup or re-run commercial detection
> after the recording finishes, detection should be as reliable as it
> was in 0.24-fixes.

That would be a different issue then, because I have comm detection
during recording disabled already, and re-running the detection
doesn't fix it.

I'll be watching this further, the actual detection is less reliable
recently too, I still need to send some samples to Gavin.

--
Jan Schneider
The Horde Project
http://www.horde.org/

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads