|DXZeff's Computing Forum|
| DPict Nexeon HD Capture card HELP!!!!|
Jump to page : 1
Now viewing page 1 [25 messages per page]
|View previous thread :: View next thread|
|Computer Speak -> Hardware (DOS & Windows)||Message format|
|Ok so the "new" capture card arrived. This card is listed as being capable of doing everything I could ever want it to except make me a sandwich. Product specs - http://www.dpictimaging.com/Products/NexeonHD.html |
My trouble is, while the DPict driver suite from their website includes a utility to, more or less test/preview the card, I am unable to get any capture software I have to even see the card. OBS, Vegas, and Debut Capture all fail to see the existence of the card.
While I could not find this question asked specifically for the Dpict card on a late night google search, I was also no able to find an an answer related to this problem in general with capture cards other than "reinstall the driver" which is not the fix unfortunately despite also trying the, what I call generic device driver "Snappy Driver Installer" installed for the device.
SO the big ? is... has anyone experienced this problem of apps not seeing the capture device, and is there a way around this problem or am I just screwed here as I feel I am? of ALL the apps I would have thought OBS would see it.
One thing that might be key is that the capture card does not install in the device manager as a multimedia sound/video device, but installs itself under it's own Dpict category in DM.
Location: Hull, UK
|The only information I can find in the manual is; |
DirectShow® is a multimedia framework developed by Microsoft® to enable video streaming in applications conforming to the DirectShow API. Nexeon HD Setup installs the DirectShow driver for the Nexeon HD, named dpictds_hd.ax, in the Windows/System32 directory. With the Nexeon HD DirectShow® driver, the Nexeon HD can be used to view and capture video with third-party applications that support the DirectDraw® framework.
But nothing about how to register this driver with the system, nor do I have any real idea how this would work now as playing with SYSTEM.INI as in days of old is likely not the solution.
Perhaps you could try regsvr32 dpictds_hd.ax if this file does exist, there also exist DirectShow filter managers out there which might help out.
Unfortunately I have had no success in breaking into the installation EXE files to poke the files inside around. It looks as though this card is from the same era as the Intensity Pro and Hauppauge Colossus, a time when vendors decided to be silly and lock their cards down to only work with the software they wanted them to. Blacgmagic fixed theirs, Hauppauge did not (theirs are locked to the included CD as well), looks like DPict did something about it but attempted to make it obscure.
Edited by DXZeff 2018-04-11 5:23 PM
|Thanks for poking around with it. I didn't think this would be such a difficult thing to do. I thought I was pretty much home free with what quote you posted. I saw that on the website and thought, well why the hell then is this not visible to "third party apps" I figured the driver installer would take care of things. I did try running the included app with the driver while also trying OBS to see if maybe the app did something to make the device visible but that made no difference of course. |
I will try registering that file manually and see what happens. Hopefully it is actually on the hard drive.
|Well I looked and the file is no where to be found on the hard drive. I also extracted the contents and looked inside of the various files and the directshow driver is not included in the driver anywhere. I looked at the Aexeon drivers and same thing. Looking at their FTP site revealed a lot of promising files named CODEC and another driver version for the cards but still cannot find the dpictds_hd.ax file. Even a google search reveals no results. I even found an alternate site who sells the card and had their own driver package but still no .ax file. So at this point, I really have no ideas except email the company and ask them for the file. Even went back in time on archive.org and it looks like the current driver has been there since at least 2011.|
Edited by waybacktech 2018-04-12 3:39 AM
|Jump to page : 1 |
Now viewing page 1 [25 messages per page]
|Search this forum|
Printer friendly version
E-mail a link to this thread
|(Delete all cookies set by this site)|
|Running MegaBBS ASP Forum Software|
© 2002-2018 PD9 Software