and i'm sure it's not the tuner problem, as i don't have tuner.
| Printable Version of Topic
Click here to view this topic in its original format |
| Unofficial VirtualDub Support Forums > Capture > Vvcrs2 Problem |
| Posted by: i4004 Mar 10 2005, 01:29 AM |
| and i'm sure it's not the tuner problem, as i don't have tuner. |
| Posted by: fccHandler Mar 10 2005, 02:13 AM |
| Um, do you mind telling us what you're doing? BTW, did you notice that was your 1337 post!  |
| Posted by: i4004 Mar 10 2005, 04:07 AM | ||||
i decided to run desktop at full glorious b/w! 
<blush> i'm not really doing anything; i fire up vvcrs2, set times, and it starts vdub....with this error. i dunno what is vvcrs trying to "open". oh yeah; http://vvcrs.asktech.ca/virtualdub.php you try it too. i didn't used too many words as leon wrote on the forum recently. |
| Posted by: phaeron Mar 10 2005, 06:01 AM | ||
The error is bring thrown because a filename with spaces isn't being quoted. Here's what I'm getting on my end from GetCommandLineW():
|
| Posted by: i4004 Mar 10 2005, 11:39 PM | ||
| i actually thought it would be something like that, as i saw time-tag of vvcrs2 wasn't completed (brackets left unclosed). i would suggest this to leon
i would also suggest vvcrs2 to use same time format as win uses; i have always found yyyy-m-d exactly the opposite to human way of thinking, so i just changed it to d.M.yyyy. i mean, are we writing time as 55-52-21? (what is the historic reason for that anyway?) although that's a no problem anyway; there's a file date/time as a part of file-system itself, and i surely won't use the date/time tag as a filename when it gets to media burning phase. |
| Posted by: leoncheong Mar 16 2005, 09:46 AM |
| OK. fixed. I'll keeping the format for it is the same as VirtualVCR. |
| Posted by: i4004 Mar 16 2005, 08:53 PM |
| i tried it with 2 timers in a row, and it seems to be working fine now. thanks. ps. i just tried 6 timers in a row, and it went fine. |