Sorry this is a long post, but i've been trying to find more info on this ....
Originally posted by EAK125
Like I said - directshow... But note - using a software dvd player's codec is not the same as a dedicated directshow filter - using different sofware dvd player codecs will give different results.
@fused - do you have mpeg and m2v in your file list under your directshow filter ? I think it should be default but u never know...
Also what version of PowerDVD do you have? I did a little testing with power dvd (since elecard has the option to turn itself off). I could get v.4's codec to work with winamp but not v.5's... Maybe that's just me - anyone else?
And what video card/drivers are u using and what Direct X - may help others track down the bug.
Yes the file extensions are listed under the directshow filter.
Actually I am using PowerDVD v5, if this is a problem with PowerDVD version, I don't see why the codec would allow video to be decoded in other players with no problem though? With v5 were you experiencing a crash or something else?
Video card drivers are Detonator v52.13's. DirectX version is 9.0b.
I've also just tried a clean install, no 3rd party plugins at all, same crash problem with SVCD video files.
And I dunno if it points to soemthing, but the crash error is always exactly the same, the memory offset never changes:
The instruction at "0x1c403b9b" referenced memory at "0x00000000". The memory could not be "read".
Just did some googling on this type of error and I came across this comment on another forum:
In C and C++, there are useful, yet dangerous things called pointers. A pointer is a simple mechanism that allows you to 'point' to another object that you've already set up. This is very useful - in Orbiter, there are pointers to ships, MFD's, textures, you name it.
The error you mentioned happens whenever a program attempts to use a pointer that hasn't been initialised. Uninitialised pointers are typically set to 0, which leads the program to fail with a "Instruction xxxxxxxxx Referenced Memory at '0x0000000000', The Memory Could Not Be 'read'.
This happens because the memory at 0 is never assigned to a program, and so trying to read 0 leads to a failure of the program.
Pointers can occur all over the place - I regularly create this error with silly mistakes in my code whilst I'm programming.
1. This error is caused by a silly programming mistake (no disrespect to anyone - 99% of my mistakes are of this type!)
2. There is no single cause of this error - each programmer has many opportunities to cause it every time they create code with pointers in it.
Windows NT derivatives are much more stringent about memory errors.
Windows 9x will often let the read go ahead. More to the point, Windows 9x doesn't guarantee that the pointer will be set to zero when the program starts, so reads from uninitialised pointers will go almost anywhere depending on what that piece of memory was used for last time. Reading will lead to junk being pulled into your program.
So I tried turning on compatibility mode in WinXP, i set it to Windows 98/ME and now Winamp does not crash, but it still does not play properly.
The video does not show at all, and while there is audio that can be made out, it is very garbled.