Go Back    Forum > Digital Video > Video Project Help > Capture, Record, Transfer

Reply
 
LinkBack Thread Tools
  #1  
01-26-2020, 03:10 AM
imgkd imgkd is offline
Free Member
 
Join Date: Jan 2019
Location: Yes.
Posts: 17
Thanked 7 Times in 5 Posts
Recently I acquired a complete workflow (in separate transactions though) from LS, and I put it together, then after several freezes and crashes I was able to get VirtualDub set up and have the settings dialed down, system tested and all that nonsense.

But then once I restarted the system, not only did my bootup time take probably a solid hour (because Windows updates are fun, aren't they?), but the update that got installed outright broke any functionality which enables access to the card.

Now, every time I attempt to access VirtualDub (both 1.9.11 x86 and 1.10.4 x64), it responds with "VirtualDub cannot connect to the desired capture driver."

When I go over to Crossbar Thing and click on "Pinnacle 710-USB", an error dialog immediately pops up with the following error details:
Code:
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at System.Runtime.InteropServices.ComTypes.IMoniker.BindToObject(IBindCtx pbc, IMoniker pmkToLeft, Guid& riidResult, Object& ppvResult)
   at Crossbar_Thing.Form1.CreateFilter(Guid category, String friendlyname)
   at Crossbar_Thing.Form1.crossbarList_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Crossbar Thing
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/imgkd/Desktop/Crossbar%20Thing/Crossbar%20Thing.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
DirectShowLib-2005
    Assembly Version: 2.1.0.42374
    Win32 Version: 2.1.0.42374
    CodeBase: file:///C:/Users/imgkd/Desktop/Crossbar%20Thing/DirectShowLib-2005.DLL
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Lastly, if I attempt to access the capture card directly as a DirectShow device, via FFmpeg, it too prints an error message that's similar to the one Crossbar Thing prints out:
Code:
Microsoft Windows [Version 10.0.18362.535]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\imgkd>ffmpeg -f dshow -i video="Pinnacle 710-USB"
ffmpeg version git-2020-01-24-e931119 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.2.1 (GCC) 20200122
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  libavutil      56. 38.100 / 56. 38.100
  libavcodec     58. 66.100 / 58. 66.100
  libavformat    58. 35.104 / 58. 35.104
  libavdevice    58.  9.103 / 58.  9.103
  libavfilter     7. 71.100 /  7. 71.100
  libswscale      5.  6.100 /  5.  6.100
  libswresample   3.  6.100 /  3.  6.100
  libpostproc    55.  6.100 / 55.  6.100
[dshow @ 000001fa03d296c0] Unable to BindToObject for Pinnacle 710-USB
[dshow @ 000001fa03d296c0] Could not find video device with name [Pinnacle 710-USB] among source devices of type video.
video=Pinnacle 710-USB: I/O error
Based on these errors, and some research of my own, it is apparent that this error is not an application-specific issue, but rather something is getting blocked whenever any application attempts to request access to the capture card.

To be clear, this BindToObject issue only happens with this capture card; it does not happen with any other device. It's that way with FFmpeg (was able to access my mic via DirectShow), and with VirtualDub (Crossbar Thing throws another error when accessing one device but that's a totally different thing).

Some users who have come across similar errors have noticed that their antivirus application was blocking access to their DirectShow devices, and that disabling or uninstalling the anitivirus worked. However, I only have Windows Defender (I used to have Avast! but I uninstalled it long ago since I use Linux 99% of the time), and turning off some of the anti-malware protection settings did nothing.

Some made references to the DLL files being moved around. However, I don't know what the DLL files corresponding to the capture card driver are. And even if I did, I wouldn't know what the original locations were when they did work before the Win10 update.

Apparently there are ways to configure COM objects, which is what BindToObject deals with, but I can't get a full grasp of how one could get around that stuff to see if the problem is solvable there.

Also, running Crossbar Thing as an administrator did not fix the issue.

Is there anything else I could try, in order to see if this problem can be fixed?

-ImgKD
Reply With Quote
Someday, 12:01 PM
admin's Avatar
Ads / Sponsors
 
Join Date: ∞
Posts: 42
Thanks: ∞
Thanked 42 Times in 42 Posts
  #2  
01-26-2020, 04:02 AM
lordsmurf's Avatar
lordsmurf lordsmurf is online now
Site Staff | Video
 
Join Date: Dec 2002
Posts: 13,509
Thanked 2,449 Times in 2,081 Posts
Ugh. Win10 is breaking more and more capture card installs. We've seen reports of other cards, like the ATI 600 USB. I've even read some reports (in other forums/blogs) with HD cards (not-suggested models like Magewell and Blackmagic) being zapped as well.

Win10 is a tablet OS for the internet. Anything else is simply iffy.

The best OS for video capture is WinXP or Win7.

Others are using Win10 without issue. I don't have my dev box finished yet, otherwise I could fire up Win10 myself.

Maybe jwillis will pop into this thread? This sort of thing is up his alley.

- Did my advice help you? Then become a Premium Member and support this site.
- For sale in the marketplace: TBCs, workflows, capture cards, VCRs
Reply With Quote
  #3  
01-26-2020, 03:37 PM
jwillis84 jwillis84 is offline
Free Member
 
Join Date: Aug 2017
Location: College Station, TX
Posts: 800
Thanked 217 Times in 174 Posts
Its very hard to target a proper response to solve a problem without knowing "precisely" which version of Windows 10

The quickest way is open a command window and type "winver"

This program will reveal the Four digit code that indicates the "real" version of Windows 10 running.

-----------

Be that as it may.

The first error train indicates Crossbar thing was denied access so either the Device or some resource of the PC.

The second error train indicates the Device Driver for the Pinnacle 710-USB is not loaded, or that its not addressed by the name "Pinnacle 710-USB".

-----------

With the four digit Win10 version

I could probably attempt to replicate the problem, or confirm whether the combination can work.

Last edited by jwillis84; 01-26-2020 at 04:14 PM.
Reply With Quote
  #4  
01-26-2020, 05:23 PM
imgkd imgkd is offline
Free Member
 
Join Date: Jan 2019
Location: Yes.
Posts: 17
Thanked 7 Times in 5 Posts
Quote:
Win10 is a tablet OS for the internet. Anything else is simply iffy.
Windows 8/8.1 especially. To be clear, I absolutely hate Windows with a passion (especially after this problem and that it also broke my Linux boot configuration). I would rather use Linux. But sadly, like most things in life, Windows is the only supported OS for this capture card.

Quote:
The best OS for video capture is WinXP or Win7.
I've read quite a bit of posts on capturing and I've drawn the same conclusion. Since I already had Windows 10 installed on my computer (it's a dual-boot configuration between that and Linux, even though I use the Linux side much much more), I was hoping I wouldn't have to do any extra work or install any more OSes. In fact I was thinking about getting yet another copy of Windows 7 as soon as I experienced this issue.

Quote:
With the four digit Win10 version

I could probably attempt to replicate the problem, or confirm whether the combination can work.
Specific version is Version 1903.

Quote:
The second error train indicates the Device Driver for the Pinnacle 710-USB is not loaded, or that its not addressed by the name "Pinnacle 710-USB".
I think the "not found" part is an artifact of FFmpeg's error handling. For one, the line above it mentions "BindToObject" which is the similar thing we're seeing with Crossbar Thing. I also checked the code and FFmpeg is executing the exact function that Crossbar Thing is when that error is thrown (FFmpeg isn't really specific about what kind of error is being thrown, it just prints an error if the return value isn't "OK").

And if you want further proof that the identification of the card is correct:
Code:
C:\Users\imgkd>ffmpeg -list_devices true -f dshow -i dummy
ffmpeg version git-2020-01-24-e931119 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.2.1 (GCC) 20200122
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  libavutil      56. 38.100 / 56. 38.100
  libavcodec     58. 66.100 / 58. 66.100
  libavformat    58. 35.104 / 58. 35.104
  libavdevice    58.  9.103 / 58.  9.103
  libavfilter     7. 71.100 /  7. 71.100
  libswscale      5.  6.100 /  5.  6.100
  libswresample   3.  6.100 /  3.  6.100
  libpostproc    55.  6.100 / 55.  6.100
[dshow @ 00000251442ec0c0] DirectShow video devices (some may be both video and audio devices)
[dshow @ 00000251442ec0c0]  "Pinnacle 710-USB"
[dshow @ 00000251442ec0c0]     Alternative name "@device_pnp_\\?\usb#vid_2304&pid_0224#6&59cb9c4&0&3#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{fb112213-ff34-40a9-bb84-f2c76b349ebb}"
[dshow @ 00000251442ec0c0] DirectShow audio devices
[dshow @ 00000251442ec0c0]  "Microphone (5- USB Advanced Audio Device)"
[dshow @ 00000251442ec0c0]     Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{020E2297-4C0E-4730-BD95-6D77DE6FE020}"
dummy: Immediate exit requested
-ImgKD
Reply With Quote
  #5  
01-27-2020, 02:01 AM
imgkd imgkd is offline
Free Member
 
Join Date: Jan 2019
Location: Yes.
Posts: 17
Thanked 7 Times in 5 Posts
Update: I have managed to revert my Windows 10 installation back to version 1607 (since it had only been a day since it was updated), and I'm no longer having driver-related issues. Thanks for your help!

-ImgKD
Reply With Quote
  #6  
01-27-2020, 02:33 AM
jwillis84 jwillis84 is offline
Free Member
 
Join Date: Aug 2017
Location: College Station, TX
Posts: 800
Thanked 217 Times in 174 Posts
1903 - Spring 2019 edition

Had a lot of teething problems, it broke many device driver types... its not well tested, and testing has not improved with subsequent updates.
Reply With Quote
Reply




Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot capture 720x480 in Win10 64-bit Pinnacle-710? BruceOlsen Capture, Record, Transfer 2 01-26-2020 08:31 PM
Dealing with telecine cadence breaks? ELinder Restore, Filter, Improve Quality 5 05-01-2019 01:41 PM
Uneven breaks in tapes: How to repair? Gotanno Video Hardware Repair 4 06-26-2018 07:58 PM
Warning: Latest Firefox browser update! rocko General Discussion 3 03-21-2017 12:08 AM
What makes/breaks a DVD recorder admin Capture, Record, Transfer 0 11-17-2005 04:02 PM

Thread Tools



 
All times are GMT -5. The time now is 05:55 AM