MP 1.3.x dshowhelper development (1 Viewer)

[disaster123]

I see occasional stuttering when using 683 679 instead works fine to me.

 

[SciDoctor]

To me 679 works much better than 683

System specs, MP logs, screen caps of playback with stats as comparison would helpfull !!!!!

 

[disaster123]

To me 679 works much better than 683

System specs, MP logs, screen caps of playback with stats as comparison would helpfull !!!!!

Sorry.

>System specs
AMD HD5450 with CAT 12.10, AMD X2 235e, Win 7 64bit, MP 1.3 GIT, LAV 54.1

> MP logs
Sorry don't have one i already deleted them - will look when i've time to get new ones.

> screen caps of playback with stats
I haven't managed it to get this working since 2 years with my soundgraph RM200 remote with IRSS.

 

[Vasilich]

> screen caps of playback with stats
I haven't managed it to get this working since 2 years with my soundgraph RM200 remote with IRSS.

so what is the problem - in your Soundgraph or that you are use VMR instead of EVR? you should open new thread about this first then

 

[tourettes]

> screen caps of playback with stats
I haven't managed it to get this working since 2 years with my soundgraph RM200 remote with IRSS.

It will be much more easy for you to attach a keyboard to the HTPC for a moment than for Tony to guess what is happening there. One of those two tasks is pretty impossible / pointess

 

[Owlsroost]

I see occasional stuttering when using 683 679 instead works fine to me.

My only thoughts on this (based on SciDoctor's and your comments) are that some AMD setups seem a bit sensitive to the timing of the DWM queued mode initialisation (relative to when play starts) - no idea why....

The next version will have an option to chose early or late initialisation - this is the main difference between v679 (late) and v683 (early).

Tony

 

[Owlsroost]

I know last time it happened was when my gf was watching tv, she was on bbc HD and very bad pixelation occurred, she switched to bbc sd to continue watching.

When she told me I switched back to bbc HD and all was ok.

Using default dshowhelper it occurs on every channel change for roughly 3 secs (and when I use the skip steps). The latest dshowhelper is perfect most of the time, I rarely have the pixelation. I'd have to go back to default helper to test he older amd drivers

Is there anything that can be done to improve things with dshowhelper or tsreader do you think? Or is this definitely a amd issue here?

What I suspect is happening is that the AMD decoder struggles to handle H.264 stream errors/discontinuities when the GPU is heavily loaded (as the HD5450 will be when playing 1080i content on a 1080p display). The only reason I can think of for dshowhelper influencing this is that when DWM queued mode is enabled it may make it easier for the GPU to handle the load.

Tony

 

[onelegend]

I've gone back to the default dshowhelper and rolled my driver to 11.6, not seen pixelation but as you say I think the cards a little under powered.

Ill keep monitoring it though

 

[SciDoctor]

I am revisiting the earlier files like V679 since starting testing the alternate TsReader (using 'TsReader_noStopMod68' atm).

What I found was that the problems that I encountered with V679 and the standard release TsReader don't apply with 'TsReader_noStopMod68'

A three hour test and no problems.

I am now about to test V678 which caused severe problems and will feedback.

Nothing has changed on the PC driver wise; MP1.3b with updated BluRay support and new TsWriter (avoids subchannel locks to tuners).

 

[SciDoctor]

Well V678 has performed without a hitch with 'TsReader_noStopMod68'.

This is Very odd as it caused such problems with the standard 1.3b TsReader whch I believe is the same as noStopMod63b.

Anyway I thought I would feedback my findings.

Maybe when the next release is done a reg setting for soft or hard lock (default hard) also can be added if not to much code or problem.

Is there a major link with the TsReader that could cause this ?