|
|
| element |
| Posted: Mar 23 2011, 03:02 AM |
 |
|
Newbie
Group: Members
Posts: 8
Member No.: 30371
Joined: 23-March 11
|
I use VirtualDub 1.9.11 on Win7 x64 with a StarTech USB capture cable to digitize old VHS tapes. The capture works great except for one issue. Usually, I run vdub.exe from a batch file to capture overnight, when I go bed. The capture works fine, but after it's done, the audio input from the StarTech ends up "locked". By "locked", I mean that when I launch VirtualDub, no audio comes in from the StarTech. VirtualDub's VU meter is either stuck at -20dB or -40dB (i.e, nothing). The video from the StarTech comes in fine. Other audio sources in my PC work fine, as well. When I reboot my PC, the audio lock gets fixed: now when I start VirtualDub, the audio from the StarTech comes in OK. But when I run vdub.exe again, the problem re-occurs. Any ideas how to debug this? Below is my vdub batch file. Again, the capture works OK, it's the audio lock after the capture that's the problem.
| CODE | | vdub /s settings.vcf /capture /capdevice MyDevice /capfile Output.avi /capstart 60 |
|
|
| ale5000 |
| Posted: Mar 23 2011, 04:12 AM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
I don't know about your problem but try with the latest test build: http://forums.virtualdub.org/index.php?act...ST&f=15&t=19755
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
| element |
| Posted: Mar 23 2011, 07:08 PM |
|
|
Newbie
Group: Members
Posts: 8
Member No.: 30371
Joined: 23-March 11
|
Thanks for the pointer to 1.10.1, but it didn't help. There's one small slight change. Now after vdub capture the VU meter in VirtualDub initially shows the red peak lines descending, as if after a spike in audio signal. Previously there was no motion in the VU meter at all. There's still no audio, though, and I still have to reboot.
BTW, VirtualDub 1.10.1 always crashes in Capture when I select Video->Extend Luma Point (White or Black):
"An out-of-bounds memory access (access violation) occurred in module 'VirtualDub'... reading address 5B041340" |
|
| ale5000 |
| Posted: Mar 23 2011, 07:56 PM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
About the crash, it would be nice if you post the full crash report here: http://forums.virtualdub.org/index.php?act...ST&f=15&t=19755
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
| element |
| Posted: Mar 23 2011, 09:31 PM |
|
|
Newbie
Group: Members
Posts: 8
Member No.: 30371
Joined: 23-March 11
|
Done. BTW, the problem I'm experiencing almost looks like vdub.exe requests an exclusive access to the capture device, but then fails to release it. Does vdub.exe call any exclusive access type functions? |
|
| ale5000 |
| Posted: Mar 24 2011, 12:58 AM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
For the problem you should wait a reply from phaeron.
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
| element |
| Posted: Mar 26 2011, 07:31 PM |
|
|
Newbie
Group: Members
Posts: 8
Member No.: 30371
Joined: 23-March 11
|
OK, found the fix to my problem: don't set the capture device, i.e remove "/capdevice MyDevice". Looks like VirtualDub's remembers the last one used. Now audio capture doesn't get locked. |
|
| phaeron |
| Posted: Mar 26 2011, 10:34 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
This sounds like the capture device has a timing problem: the combination /capture /capdevice causes the capture device to be set twice in succession. I wonder if there's a way I can avoid this.
|
|
| element |
| Posted: Mar 27 2011, 02:21 AM |
|
|
Newbie
Group: Members
Posts: 8
Member No.: 30371
Joined: 23-March 11
|
Perhaps VirtualDub could check if the device in the /capdevice parameter has the same name as the default one (last one used). If so, than skip the /capdevice request (i.e don't set the device twice). |
|
| phaeron |
| Posted: Apr 3 2011, 12:59 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Yeah, I'll go ahead and do this. I don't see any reason not to, and it should fix the problem.
|
|
| Mark Donovan |
 Posted: Apr 14 2011, 05:22 AM |
|
|
Newbie
Group: Members
Posts: 1
Member No.: 30801
Joined: 14-April 11
|
If you have completed the preceding sections on tuning, you are finally ready to begin capturing the video to your hard drive. Remember that right now you will need about 1.25-3.0 GB of free hard disk space with Huffyuv or 350-800 MB with MJPEG per 10 minutes of video that you wish to capture .  |
|
