Bugs & Missing Options with the 'Pinnacle 510-USB' Device
An enhanced version of the original VirtualDub
Brought to you by:
shekhjkl
Menu
▾
▴
1 Attachments
#110 Bugs & Missing Options with the 'Pinnacle 510-USB' Device
The issues are as follows:
1.) The "Video->Video source" menu shows "No video source". This capture device has three video inputs: 'FireWire 400', 'S-Video', and 'Composite'.
2.) Audio captures are often digitally distorted (see attached examples). This occurs regardless of timing settings or signal quality. Manually disabling and re-enabling the device in 'Device Manager' can reduce errors, but doesn't eliminate the problem.
3.) The longer the device is used, the more distorted each capture becomes. Eventually, it drops frames randomly on a clean signal, misses the audio stream entirely, produces an AVI file that plays back at ~half speed, or causes the application to lock-up completely. Once any of these problems occur a system reboot is necessary.
(I've found Build 41106 to be more stable with this device than newer releases, so it's what I'm using for the moment.)
Pinnacle 510-USB Hardware
USB bridge: 'Cypress CY7C68013A'
Audio ADC: 'Empia EMP202'
S-Video/CVBS decoder: 'Philips SAA7113H'
FireWire 400 bridge: 'Agere LFW3226-100' + 'Altera Cyclone EP1C3T144C8N'
Discussion
Anonymous
1) Thanks for noticing, uploaded new build with fixed menus.
2,3) This all sounds like HW/driver instability. Have no idea what to do about it. There was no big changes affecting capture since 41106, nothing sufficient to distort sound (if only VersionInfo resource? It might be used to control compatibility shims) . Did you compare behavior with x86 and x64 versions?
1.) Build 41552 still shows “No video sources”.
2 & 3.) Evidently, your efforts have done something to improve the operation of this device. If I use 'VirtualDub 1.10.4', for example, it will always freeze at the start of a 2nd capture. I’ve also recently reinforced its’ power supply with electrolytic capacitors, so there’s no problem there.
What would help is an option to automatically power cycle the device twice after each capture. Doing it manually is quite tedious.
I’m using an x86 setup. The last time I was able to test the x64 version, it had a greater tendency to lock-up.
I double checked: the menu should be filled properly (the issue in older builds also affected Audio->Audio input, Audio->Audio source).
Do you see "Video source" options in 1.10.4? Do you see anything under Video->Crossbar?
I doubt it is even technically possible. Not going to mess with this, sorry.
Last edit: Anton Shekhovtsov 2018-04-03
In '1.10.4' and ‘Build 41585‘: “No video sources”, “No audio sources”, “No audio inputs”, and "Video->Crossbar" is not selectable.
In that case it means there is nothing to put in that menu. It may show crossbar options but looks like this is not how pinnacle driver works (doesn't have crossbar interface).
I wouldn't say that. The application, "Crossbar Thing", is able to detect everything except the FireWire (see attached photos).
Also, I noticed that the outdated "VirtualDub-dazzle-hack" is able to consistently capture audio without distortions. It lists the audio stream twice under different labels (see photo). Only the generic label works.
Where is "dazzle-hack" from? I noticed some lines in code saying it is "disabling dazzle hack now" and by coincidence the disabled code was exactly needed for some other issue. So current version does list some audio sources twice (ones with WDM are enabled by "hack").
I only find out about crossbar by following code which is supposed to list video sources. Sad that it does not work for you. The reason could be anything, I never tested that code (it was written long before I saw it).
It’s also known as ‘VirtualDub 1.9.1-prerelease (Build 31474/release)’. Avery Lee made it in 2009 for owners of “Dazzle"-branded capture devices sold since 1997. For whatever reason, it is not included with the other pre-releases on SourceForge. It’s only hosted on the official VirtualDub website.
There’s likely a reason for that. Add a menu option to enable/disable the hack, just in case a conflict emerges.
Which issue?
I just find it strange that a small single-released piece of abandonware would have better crossbar detection than a full-featured recorder with ~18 years worth of updates, hacks, and mods.
I can only guess that Avery was too bored to make this hack into real thing and abandoned it.
The issue that was reported to me: with Magewell pro there are more options to select (number of audio channels) when using audio sources from WDM group rather than "normal" audio sources.
This can be seen in GraphStudioNext: you can search for available audio sources in the "audio sources" group or in "WDM streaming capture" group. I still don't know what is the difference but same logical devices have different options for some reason.
In the end it is just more source options many of which don't connect at all. I don't see reason to disable this now.
It is not surprising to me that something doesn't work. I have found many flaws, some quite simple like typo.
Does the WDM group consistently show the proper device name instead of “Capture device”?
Speaking of which: “Video->No display” cuts off “Audio->Enable audio playback”.
I already saw examples where device is officially named "Capture device". Drivers world is weird.
This is weird. I'll look what I can do.
fixed
Hi, I also have a 510-USB and would like to use it with a modern VirtualDub. Any update on number 1? Right now, I have to use another program, like CaptureFlux, to change the crossbar from Composite to S-Video on each boot. Then, I can use it in VirtualDub. Thanks!
Can you provide remote access to your system? Please sign in so we can exchange private messages.
"Missing video sources" also occurs with the 710-USB in AmarecTV. I do not think this is a Virtual Dub issue.