get VideoInfo using DirectX
@Hack. i removed all binaries except DirectX .dll
Printable View
get VideoInfo using DirectX
@Hack. i removed all binaries except DirectX .dll
testing report :
IT DIDN'T WORK
tested on : vb.net express 2010, win xp with media player 11
when run (f5) after a folder was selected the program jammed up and the button became light pale white.
did you set your target CPU to x86 + disable Loaderlock (Debug-->Exceptions-->Managed Debugging Assistants-->Loaderlock)?
set target CPU to x86 ?
@moti that's unnecessary unless you are running a 64-bit os. The compiler will target that cpu and directx sdk doesn't support it.
will target what cpu ? and directx sdk doesn't support what ?Quote:
Originally Posted by Lord Orwell
directx sdk doesn't support x64. your target cpu must be x86
did you know when I mouse hover over a video file it says, in a yellow label, it's time length.
ok let me go in length here.Quote:
Originally Posted by moti barski
1. There are two versions of windows: x86 and x64, which are 32 and 64 bits respectively.
2. While directx works on both x86 and x64, the sdk does not, so any programming you test, you must compile with your cpu target as x86. The problem here is that some versions of visual studio (the free ones) don't have an option to change it in their menu. You need to google how to edit the program solution's configuration file and manually change it.
3. As far as i am aware, loaderlock only applies if you are developing in c#.
I hope that clears up some issues.
my example from post #1 throws an error with Loaderlock exceptions handled.Quote:
Originally Posted by Lord Orwell
with it disabled it runs without an error
ok well i learned something then. I've only encountered an issue with it using c# and never had the pleasure of seeing the setting in vb.net 2010 or earlier. Well if i get an error i'll know why now.Quote:
Originally Posted by .paul.