Capture Type Reset to Full-TS Options

[the Omrud]

Since I installed a new version of TV Scheduler on a new machine, I occasionally get "Consumer Did Not Start", which I've seen before, and "Capture Type Reset (Full-TS)", which I haven't. It has the effect of recording the whole Mux instead of the channel I'd selected.

Any ideas? I don't mind it resetting, but I'd rather it didn't fill my disk up with 12 GB per hour of a multiplex, the vast majority of which I don't want.

Thanks

David

[null_pointer]

check the logs and schedule info page, this will help you find out why the consumer did not start and thus the reason for the fall back to full ts.

[the Omrud]

Since I installed a new version of TV Scheduler on a new machine, I occasionally get "Consumer Did Not Start", which I've seen before, and "Capture Type Reset (Full-TS)", which I haven't. It has the effect of recording the whole Mux instead of the channel I'd selected.

Any ideas? I don't mind it resetting, but I'd rather it didn't fill my disk up with 12 GB per hour of a multiplex, the vast majority of which I don't want.

Thanks

David

I've attached the Logs in the zip file - can anybody help with understanding what's happening?

thanks

David

Attached File(s)

 ScheduleErrorReport.zip ( 6.49K ) Number of downloads: 3

 

[null_pointer]

your channels are not set up correctly

2009/12/22 23:58:18.330 - Could not find program PID with video (-1) or audio (1702)

the video pid is screwed for this channel it should not be -1, rescan the channel

[the Omrud]

your channels are not set up correctly

2009/12/22 23:58:18.330 - Could not find program PID with video (-1) or audio (1702)

the video pid is screwed for this channel it should not be -1, rescan the channel

Thanks, I've tried that, but this is a Radio channel and the rescan comes up with the same video PID of -1. Is that not normal for a radio channel?

I believe I see now where the "fall back" to Full-TS comes from - it's in the channel settings as a Capture Type for each channel, set to "Auto Select". I've changed each of the channels I record which should fix that bit of the problem.

Is it possible that the fact that the Consumer did not start is a driver issue?

David

[bear]

Is it possible that you have selected a radio channel that is not always running? Although it is in the program list at channel scan time it may not be sending any stream info when you try and capture. Do the other radio channels fail also? eg. The ones listed below

2009/12/22 23:58:18.330 - Program (5632) : (1400-PGM) (1402-PCR) (1402-MPG)

2009/12/22 23:58:18.330 - Program (5696) : (1500-PGM) (1502-PCR) (1502-MPG)

2009/12/22 23:58:18.330 - Program (5760) : (1600-PGM) (1602-PCR) (1602-MPG)

[the Omrud]

Is it possible that you have selected a radio channel that is not always running? Although it is in the program list at channel scan time it may not be sending any stream info when you try and capture. Do the other radio channels fail also?

Just to be clear - the recording never fails, but it sometimes has to reset because it can't get a consumer to respond. On the second try, however, it always works. And this reset problem only happens once in every five or so scheduled recordings, all of which are from one of three radio channels, which are broadcasting permanently - they are national BBC channels.

My main problem was that after a reset, the recording options dropped back to Full-TS. I think I've cured that by changing the default in each of the channel settings to TS-Mux. If it resets and then does what I want, it's slightly concerning, but not critical. I haven't had a reset error for three days now, so I can't tell whether it's really cured ...

Thanks,

David

[bear]

the recording never fails, but it sometimes has to reset because it can't get a consumer to respond.

Well sort of, the consumer actualy does fail with an unspecified error.

From Consumer log 845:

CODE

2009/12/22 23:58:18.330 - Could not find program PID with video (-1) or audio (1702)
2009/12/22 23:58:18.330 - findTSProg Failed
2009/12/22 23:58:18.441 - Run Graph Failed (0x80004005)
2009/12/22 23:58:18.451 - Error (0x80004005) Unspecified error

It fails to find the program audio PID because the PSI parser is unable to find any PMT tables for the radio service you have selected.

From Consumer log 845:

2009/12/22 23:58:16.328 - Timeout getting table (pid=06a4, tid=02)
2009/12/22 23:58:16.328 - Error Parsing Sections and Tables (0x80040206)

On the second try, however, it always works. And this reset problem only happens once in every five or so scheduled recordings, all of which are from one of three radio channels, which are broadcasting permanently - they are national BBC channels.

As the first consumer fails to find the selected program then it defaults to the Full-Mux Capture format as it tries to still record the show you have selected. This sometimes occurs if the broadcaster has removed the pids and substituted some others to imitate the program. eg. HD channels are dropped for special events requiring the use of the bandwidth but they get mapped back to the SD channel.

I think I've cured that by changing the default in each of the channel settings to TS-Mux. If it resets and then does what I want, it's slightly concerning, but not critical. I haven't had a reset error for three days now, so I can't tell whether it's really cured ...

More likely you may have a signal quality issue that is causing the intermittant failures. If the signal disappears during the parsing of the PSI tables when the consumer starts, it's possible that it may stop the data flow operation to it and result in the behavior.

[gilesp]

I've had this happen a couple of times recently, and each time it was ABC1 (Brisbane). If I convert the TS to MPG (using HDTV2MPEG2) and play it, I notice the ABCHD station logo on the content. Looks like those programs have been broadcast in HD specially.

My default is Cyberlink mpgmux - could mpgmux be having a problem with HD channels? (I'm not in the habit of recording them). Will changing the default cap type for each channel to mpgmux then make things worse?

Another curiosity is that the resulting MPG cannot be seeked or jumped about in. That's probably the converter's fault; is there a better one that won't do this? (Preferably command-line).

[bear]

If I convert the TS to MPG (using HDTV2MPEG2) and play it, I notice the ABCHD station logo on the content. Looks like those programs have been broadcast in HD specially.

It's more likely that as the Full TS stream contains all of the programs that the stream that is converted is the first stream in the list which for the ABC is the HD stream.

My default is Cyberlink mpgmux - could mpgmux be having a problem with HD channels?

It's always possible depending on the HD format used although for ABC HD it should work fine as the muxer does not alter the data just packages it in a different way.

Will changing the default cap type for each channel to mpgmux then make things worse?

Not sure what you mean here but if no program match is found then it will default to the original stream pid values which suggest that it will have no data flowing and just fail.

Another curiosity is that the resulting MPG cannot be seeked or jumped about in. That's probably the converter's fault; is there a better one that won't do this? (Preferably command-line).

This is normally due toi the player that you are using, if wmp then it could use the default directshow filters and so play the file like it was a live stream. There are plenty of players about that should play and seek fine.

[gilesp]

It's more likely that as the Full TS stream contains all of the programs that the stream that is converted is the first stream in the list which for the ABC is the HD stream.

Probably - HDTV2MPEG2 lets you choose the stream to convert, so I must have not paid attention to the preview, and the stream names are not informative.

This is normally due toi the player that you are using, if wmp then it could use the default directshow filters and so play the file like it was a live stream. There are plenty of players about that should play and seek fine.

DNTV live plays MPG's, but it doesn't like these ones - cannot connect input pin or something informative like that. It looks like whatever is needed for seeking is not added by HDTV2MPEG2, so I'll have to find another converter.

[bear]

DNTV live plays MPG's, but it doesn't like these ones - cannot connect input pin or something informative like that. It looks like whatever is needed for seeking is not added by HDTV2MPEG2, so I'll have to find another converter.

DNTVLive latest release 1.3.6 should be able to play the Full TS mux files and let you select the sub program from the menu list. If you need to convert it and keep for later then maybe try project x or VLC.

[gilesp]

DNTVLive latest release 1.3.6 should be able to play the Full TS mux files and let you select the sub program from the menu list. If you need to convert it and keep for later then maybe try project x or VLC.

Cool - thanks for that. I'll upgrade and try it -

[gilesp]

Got rid of Cyberlink MPGMUX and selected TS_Mux as recording type, after installing a new DNTV Live that could play them. The files sizes are similar.

Best thing of all is that the frame dropping and audio squawks that always came out when using both tuners are also gone. That was an ever present condition, in spite of:
- line of sight TV reception to towers
- 3GHz Core2Duo CPU, 2GB of memory, and a fast SATA HDD
- a PCI-express dual tuner.

So it was a ridiculously over-engineered system just to not quite record properly on two tuners. I was about to plop in a separate HDD for recording. Hopefully I can save the expense. Haven't seen it drop back to Full-TS yet either.

MPGMUX? Just Say No.

[bear]

MPGMUX? Just Say No.

What version muxer were you using? There are a number of these about with different version numbers and it could have been an older one.

So it was a ridiculously over-engineered system just to not quite record properly on two tuners. I was about to plop in a separate HDD for recording. Hopefully I can save the expense. Haven't seen it drop back to Full-TS yet either.

I have a similar system working fine with Win7, the issue you may have could still be signal overloaded related if your too close to the Towers. Using a seperate drive for captures is recommended as it prevents HDD clogs if you have high local drive issues. Windows doing an auto defrag for one.

This post has been edited by bear: Feb 2 2010, 04:40 PM

[gilesp]

What version muxer were you using? There are a number of these about with different version numbers and it could have been an older one.

Can't quote numbers, but I'm aware of the old ones not working right - I went through that process a while ago.

I have a similar system working fine with Win7, the issue you may have could still be signal overloaded related if your too close to the Towers. Using a seperate drive for captures is recommended as it prevents HDD clogs if you have high local drive issues. Windows doing an auto defrag for one.

Will do a new HDD for capture if/when my present 350GB drive fills up :-) So far not close. As far as tower strength goes, I'm a fair way away but can see them in the distance - probably 15-18km.

[DrP]

Since I installed a new version of TV Scheduler on a new machine, I occasionally get "Consumer Did Not Start", which I've seen before, and "Capture Type Reset (Full-TS)", which I haven't. It has the effect of recording the whole Mux instead of the channel I'd selected.

Any ideas? I don't mind it resetting, but I'd rather it didn't fill my disk up with 12 GB per hour of a multiplex, the vast majority of which I don't want.

Thanks

David

Now this is interesting. I had DVB web scheduler (5.2.0.7) running last night while tinkering and had the exact same thing happen and yes, its because the PIDs for the program have changed. WS is set to record to the TS-MUX option, but like your experience it switched to TS FULL when the event was auto-restarted. In a way its a smart behaviour.

This post has been edited by DrP: Feb 10 2010, 05:11 AM