LiveTV freezes and shows a lot of artifacts (2 Viewers)

[Owlsroost]

@Mister Bean - any more news on the testing using MP TV server ?

To move this forward, we need to work out if this is a server or client (TsReader.ax) problem (or maybe the interaction between them + Windows SMB implementation), and trying TV server in the same enviroment is the quickest way to get more information.

 

[Owlsroost]

...also, using Argus server, can you post a TsReader.ax log where you start live TV, wait a minute, then skip back 30 seconds and leave it to play for 15 minutes - I need to see what the continuity errors etc. are in this situation.

 

[Mister Bean]

Hi Tony,

@Mister Bean - any more news on the testing using MP TV server ?

Nope, I have not had time for this yet.

To move this forward, we need to work out if this is a server or client (TsReader.ax) problem (or maybe the interaction between them + Windows SMB implementation), and trying TV server in the same enviroment is the quickest way to get more information.

I understand that, but for me it is (almost) clear that the 'interworking' between the lastest version of TsReader and the 'Tswriter' of Argus TV is not optimal. At the moment I'm running the Tsreader of MP122 (version 0.4.14) and it's working awesome. I haven't seen video continuity errors / pixelation with this version. Only a very few audio-dropouts.

Can you analyse the attached logs for me? I'm curious what you are thinking about these logs.

Thanks in advance.

Regards,

Nico

 

[Owlsroost]

I understand that, but for me it is (almost) clear that the 'interworking' between the lastest version of TsReader and the 'Tswriter' of Argus TV is not optimal. At the moment I'm running the Tsreader of MP122 (version 0.4.14) and it's working awesome. I haven't seen video continuity errors / pixelation with this version. Only a very few audio-dropouts.

I'm not going back to the old code - I'd like try and work out what is going on with the current version of TsReader.ax + Argus.

To do that I need logs using the latest version of TsReader.ax. If you want to help with that (so we can maybe improve things for other users as well) then please do so - it should only take a few minutes of your time, otherwise I'll stop wasting my time asking and start working on another problem instead....

I have private experimental code which interconnects dshowhelper+TsReader+MediaPortal Audio Reader to solve the 'clock' difference/audio dropout problems in an much nicer way, but this is of course based on the current versions - which is another reason why we can't go backwards in code terms.

 

[Mister Bean]

Ok. I agree with you that we need to find a more future-proof solution. When I have time, then I test various scenarios. I'll keep you informed.

Thanks.

Regards,
Nico

 

[Owlsroost]

I've been looking at our packet parsing code, and I think there may be a (theoretical at this stage) problem with it in some circumstances, which could get triggered in your situation because of your 'fast' render clock.

I'll keep you posted

 

[Owlsroost]

@Mister Bean

Attached is an experimental TsReader.ax with mods to the ts packet parsing code.

It will hopefully fix the regular continuity error problem (assuming my theory about the cause of these is correct, of course).

Please try it and attach the logs please.

 

[Mister Bean]

Hi Tony,

I'm gonna test this. Keep you informed Logs will follow soon.

Thanks.

Regards,
Nico

 

[Mister Bean]

Hi Tony,

This is the result after watching television for one hour (see log). Looks good! It seems that the video continuity errors are gone and that you have 'tackled' this issue. I've heard only a very few audio dropouts. BTW, the buffering delay was set to 300msec in registry

Tomorrow I will do some more testing.

Thanks!!!!!

Regards,
Nico

 

[Owlsroost]

Good

I realized there was another 'problem' parsing situation that wasn't covered, so attached is another TsReader.ax test version - please try out and report back (with the log).

Thanks,

Tony