|
|
| play32 |
| Posted: Mar 6 2006, 07:55 AM |
 |
|
Unregistered
|
For those of us scheduling video captures through the Windows Task Scheduler, it'd be great if the date/time could be automatically added to the capture filename, e.g. for recording a TV show that airs several times a day and/or several days a week.
Also, I thought autoincrement was supposed to avoid overwriting files as of 1.6.12 -- I'm using 1.6.13 and it is still overwriting whatever file I specify with the /capfile parameter. |
|
| phaeron |
| Posted: Mar 6 2006, 08:25 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
The autoincrement check for overwrites is in the GUI code, but unfortunately the /capfile switch bypasses the GUI and goes straight to the capture engine, so it doesn't do the check. Oops. Will fix for 1.6.14.
|
|
| play32 |
| Posted: Mar 6 2006, 08:58 AM |
|
|
Unregistered
|
Thanks, that seemed like what was happening. Hope you'll still consider the timestamps as a possibly cleaner way of solving this problem. |
|
| isidro |
| Posted: Oct 11 2012, 07:17 PM |
|
|
Advanced Member
Group: Members
Posts: 82
Member No.: 7195
Joined: 8-November 03
|
Just opened a thread about this bahaviour, I'm almost sure that there was a vdub version which incremented filename automatically in commandline, but latest (v1.10.2 and v1.9.11) overwrites without incrementing filename. |
|
| phaeron |
| Posted: Oct 13 2012, 07:53 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
/capfileinc bumps the filename until it's clear.
|
|
| isidro |
| Posted: Oct 14 2012, 07:44 PM |
|
|
Advanced Member
Group: Members
Posts: 82
Member No.: 7195
Joined: 8-November 03
|
Thanks! Feel stupid I didn't see that option 
It might be more intuitive to have only "/capstart" and use same bahaviour as when you manually capture: (Verify if "Autoincrement Filename" is checked or not in Capture menu) |
|
| phaeron |
| Posted: Oct 21 2012, 08:54 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
I could go both ways on that. The problem with options that affect command-line operation is that it can cause a batch file to succeed or fail depending on the GUI state. That's good if you're constructing the batch file by thinking in terms of the GUI, bad for consistency and if there isn't a command-line override.
|
|
