TS record bug/issue (1 Viewer)

[onelegend]

Hi mm

I believe I have cleaned out mdapi fully (forgive me if not and I will do a full clean install if not possible to clean once installed)
- it no longer lists as installed under mdapi plus and descrambling no longer works - cam disabled in TV Server...

I was pretty harsh with the channel changes and it happened again, I was focusing on BBC 1 HD (not sure if it is the same issue or not, the picture was garbage but the audio intact - no bad signal notices in tswriter either - due to the audio intact???)

What was interesting - flipping to a different channel/pid on the same transponder (bbc 2 hd in this case), this is perfect. Flipping back to BBC 1 HD and its garbage. I can flip between them at will. The tuner isn't running a retune process switching in this manor I believe.

Once I actually stopped the stream and locked back in - BBC 1 HD looked perfect.

Screenshots attached as well as logs - signal is good according to Mediaportal (reliable?) - sorry they got bad reflection in them

Thanks
Ian

 

[Owlsroost]

Are these logs for the 'BBC 1 HD and its garbage' situation i.e. to match the BBC1HD.JPG ?

If they are, then the logs look OK.....I suspect the H.264 decoder is having problems (for sure BBC1HD.JPG is showing decode problems) - have you tried it with LAV Video in software-only decode mode ?

 

[onelegend]

Yes the logs match the pics, I can try reproducing with dxva off, or would it be better to reproduce as is, start recording when occurs and try to play via vlc?

I know the garbage recording before is unplayable in vlc so I suspect this is a different problem that has occurred

 

[Owlsroost]

I suspect this is a different problem that has occurred

I think so too....the AMD hardware decoder (used for DXVA) has had issues in some driver versions.

 

[onelegend]

Reproduced that one, indeed it looks like dxva, recording plays fine with dxva still on - dxva issue rarely occurs in natural usage (don't think I've seen it for 8 months actually lol). Shouldn't it have rebuilt the stream/graph on switch from bbc 1 to bbc 2 though?

Back to trying to reproducing the original issue think ill carry on another day, must have changed channel a 100 times lol

 

[Owlsroost]

Shouldn't it have rebuilt the stream/graph on switch from bbc 1 to bbc 2 though?

Normally, not on a channel change unless the video type or resolution changes, or if the timeshift buffer file is changed. But in your logs the TsReader.log is 'fresh' so the graph has been rebuilt in this case.

 

[onelegend]

The issue happened again today, I haven't seen it since my last post but I haven't done much recording (just watching)

I think I have drilled down more specifically to when this issue occurs now.

The bad lock seems to occur when tuner 1 is busy (with another recording or live tv) and tuner 2 has to kick in to record. This is on happening on 2 systems so I believe it should be reproducible.

My plan of attack is to setup multiple dual recordings throughout the night on fta channels with my current setup (mdapi is enabled atm). If it occurs I can then disable mdapi the following night.

 

[DJBlu]

@onelegend

Are you still having this issue?
I have noticed my recordings are now corrupt due to more than one recording.

I am looking into the TSWriter at the minute and would like to know what hardware you have so I can rule out driver issues.

 

[onelegend]

I haven't seen it since upgrade to 1.4, but I haven't done much recording/testing either. My parents system does it more often so will see if it is occurring there - I believe it has also stopped as no whining has happened deadliest catch at 3 am always seemed to do it every week on my parents system so I will set it up to record (she changed timeslot and it records fine)

My system seemed to do it when recording xfactor and the voice, the voice would be the corrupted stream. They have stopped airing now and I can't reproduce - it did it every week with those 2. It's weird tbh.

I believe it occurs when tuner 1 is on tv/recording and the 2nd tuner has to wake to do a second recording and it doesn't initialise properly/in a timely manner.

I could be talking out my bum hole though

I have changed the tuner settings to stop and unticked preload, was wondering if that would have helped it?

Tbs 6981 on the 2.0.1.6 driver

 

[DJBlu]

Update to this.

I have just moved my TBS 6984 from the PCIE x16_1 port to the PCIE x4 port on my motherboard and the stuttering and sound jitter have disappeared.

Fingers crossed.