MP 1.3.x dshowhelper development (1 Viewer)

[Owlsroost]

Tony,
can you embed VersionInfo resource into your DLL so we can easily see what version is currently active?

It's on the render stats screen - 'ver: xxx' - and in the logs.

I use VS2010 Express, which (AFAIK) doesn't support adding/editing resource files - although I *think* it's possible to link in existing files (I think I've done this in the past for another project).

Tony

 

[Owlsroost]

Tony,
can you embed VersionInfo resource into your DLL so we can easily see what version is currently active?

It's on the render stats screen - 'ver: xxx' - and in the logs.

I use VS2010 Express, which (AFAIK) doesn't support adding/editing resource files - although I *think* it's possible to link in existing files (I think I've done this in the past for another project).

Tony

Worked out how to get the resource into a VS express project - it'll be in the next version

Tony

 

[SciDoctor]

V678 was released Saturday !, didn't see the announcement in the thread, will post feedback after testing.
EDIT found it in thread must be going blind.

 

[mhoogenbosch]

V678 was released Saturday !, didn't see the announcement in the thread, will post feedback after testing.

See:

Added v678 to the first page - no new features, just a change in how it works internally.

Tony

should work the same as v677

 

[Owlsroost]

Tony,
can you embed VersionInfo resource into your DLL so we can easily see what version is currently active?

It's on the render stats screen - 'ver: xxx' - and in the logs.

I use VS2010 Express, which (AFAIK) doesn't support adding/editing resource files - although I *think* it's possible to link in existing files (I think I've done this in the past for another project).

Tony

Worked out how to get the resource into a VS express project - it'll be in the next version

Tony

v679 added to first page.

Tony

 

[SciDoctor]

679 causing MP to become unresponsive and just black screen.

677 has been by far the best for my setup with zero problems. 678 close but I did have some MP freezing after BD playback which I couldn't repeat for logs. 679 exagerates the frequency of what i saw with 678; could be a link.

 

[Owlsroost]

679 causing MP to become unresponsive and just black screen.

677 has been by far the best for my setup with zero problems. 678 close but I did have some MP freezing after BD playback which I couldn't repeat for logs. 679 exagerates the frequency of what i saw with 678; could be a link.

Try this one - I've reverted the locking back to how it is in v677.

Tony

 

[SciDoctor]

Testing now. Thanks

Initial tests much, much better. The reduction in the time the black screen appears is very noticable compared to 678/679 where I didn't see any reduction at all plus instability.

Playback starts almost instantaniously.

Will be continuing test throughout this evenings viewing.

 

[SciDoctor]

TS file playback was fine for the duration of this test, lots of stop/starts skips for adverts, seek forward and backwards no problems. hour and half test. (Season final of Homeland)

Did the same for the BluRay rips I have no problems. Short test but usaly enough to judge.

Tried my usual DVD and the display driver crashed/restarted then the system hard locked needing a hard reboot.Not had this before with 677. may be connected logs att.

 

[Owlsroost]

TS file playback was fine for the duration of this test, lots of stop/starts skips for adverts, seek forward and backwards no problems. hour and half test. (Season final of Homeland)

Did the same for the BluRay rips I have no problems. Short test but usaly enough to judge.

Tried my usual DVD and the display driver crashed/restarted then the system hard locked needing a hard reboot.Not had this before with 677. may be connected logs att.

It's hard to really tel what is going on from the logs (other than possibly the AMD video decoder may have crashed/hung at some point - it looks like dshowhelper has been stalled for 22 seconds (!) while trying to get video samples from the EVR mixer just after start-of-play). I'm beginning to suspect that we might be provoking a bug in the AMD drivers somehow....

Anyway, attached is v681 - this is same as v680 except that the DWM initialisation is run earlier (but later than in v677), just to see if it makes any difference to your crashing problems. Next thing I might try is running the DWM initialisation code via one of the internal threads instead of directly from one of the filter graph manager interface methods.

Tony