Experimental TsReader development (8 Viewers)

[disaster123]

AW: Experimental TsReader development

With the video or audio part of LAV? V0.42?

 

[wouter1971]

I think it must be in video part of LAV. Stall/hang/black screen audio continues. Have seen it too, switched codecs to MS.

 

[GoldenEye]

Thanks for your energy to solve this issue, owlsroost.

I am following this thread thoroughly and I thought it's time to test again.

I use your TsReader_noStopMod34, LAV filters version 37.

I am running the TV server on my server machine. The TV signal flows from the cable provider --> set top box --> HD Fury III --> Hauppauge Colossus --> Network --> MP client. On the client, an intel core-i3 CPU is used as the graphics processor.

The HD Fury might be the reason the logs don't show any HD channels as you stated earlier. But if the Fury delivers all channels in HD format, I am wondering why there are still issues between SD/HD and HD/SD changes?

Here's what I did:

(1) started MP, accessed EPG, chose channel '13th Street' --> TV starts w/o issue
(2) back to EPG, chose 'TNT Serie HD' --> sound starts, after 1 second picture appears, then sound and picture stalls
(3) back 1 second --> after ~2 seconds picture and sound start and TV is ok
(4) back to EPG, chose 'Fox HD' --> channel switches, picture and sound starts w/o issu
(5) back to EPG, chose 'Kinowelt TV' --> same behaviour as in (2)/(3)

Logs are attached.

Thx, G.

 

[Owlsroost]

Re: AW: Experimental TsReader development

With the video or audio part of LAV? V0.42?

It's LAV video - not sure if it's only CUVID affected, or if the software-only decoder also shows the problems.

Tony

 

[Owlsroost]

Thanks for your energy to solve this issue, owlsroost.

I am following this thread thoroughly and I thought it's time to test again.

I use your TsReader_noStopMod34, LAV filters version 37.

I am running the TV server on my server machine. The TV signal flows from the cable provider --> set top box --> HD Fury III --> Hauppauge Colossus --> Network --> MP client. On the client, an intel core-i3 CPU is used as the graphics processor.

The HD Fury might be the reason the logs don't show any HD channels as you stated earlier. But if the Fury delivers all channels in HD format, I am wondering why there are still issues between SD/HD and HD/SD changes?

Here's what I did:

(1) started MP, accessed EPG, chose channel '13th Street' --> TV starts w/o issue
(2) back to EPG, chose 'TNT Serie HD' --> sound starts, after 1 second picture appears, then sound and picture stalls
(3) back 1 second --> after ~2 seconds picture and sound start and TV is ok
(4) back to EPG, chose 'Fox HD' --> channel switches, picture and sound starts w/o issu
(5) back to EPG, chose 'Kinowelt TV' --> same behaviour as in (2)/(3)

Logs are attached.

Thx, G.

You have a client/server system using RTSP - I need the client and server logs please

It looks like data just stops arriving at the client sometimes.....

Tony

 

[GoldenEye]

You have a client/server system using RTSP - I need the client and server logs please

It looks like data just stops arriving at the client sometimes.....

Tony

Thx, Tony

I have added/updated the logs in my post above.

 

[Owlsroost]

noStopMod35 added -> here <-

I haven't had any video hangs with this version using LAV Video + CUVID (0.42), so can people reporting problems with v34 please try it and report back ?

Tony

 

[GoldenEye]

noStopMod35 added -> here <-

I haven't had any video hangs with this version using LAV Video + CUVID (0.42), so can people reporting problems with v34 please try it and report back ?

Tony

I have run my earlier test procedure using v35 - after updating LAV to v0.42.

I get the same results as before.

Thx, G.

 

[Owlsroost]

Microsoft video codecs, ffdshow audio codecs, mpaudiorenderer. Maybe it's because of the last one. I hope Tourettes will pick up developing it. Can you?
I'll try to figure out which one gives the best results 33 or 34.

I've also found that MP AudioRenderer doesn't seem to like large jumps in the timestamps (e.g. from bad signal corruptions) - that's why I asked which audio renderer you were using

Tony

 

[tourettes]

Microsoft video codecs, ffdshow audio codecs, mpaudiorenderer. Maybe it's because of the last one. I hope Tourettes will pick up developing it. Can you?
I'll try to figure out which one gives the best results 33 or 34.

I've also found that MP AudioRenderer doesn't seem to like large jumps in the timestamps (e.g. from bad signal corruptions) - that's why I asked which audio renderer you were using

It shouldn't mid about corrupted / dropped data. All it does is it schedules the 1st sample after the discontinuity point to be rendered in time when the rtStart tells. Of course there could be some bug, but at least I haven't noticed such during the 1,5 years the renderer has been in use.

Was the timestamps modified somehow? Maybe a backwards jump?

I hope Tourettes will pick up developing it. Can you?

I wish I would... but it is pretty much impossible with real work + blu-ray development. I wish just that someone could continue my work - it will is probably the only way how the audio renderer could advance (especially when I personally wont have any issues with it )