|
|
| SenorKaffee |
| Posted: Jun 5 2011, 09:03 AM |
 |
|
Newbie
Group: Members
Posts: 1
Member No.: 31621
Joined: 5-June 11
|
The current behavior of VirtualDub is that it stops processing if it can't write additional data on the disk. I think this is needlessly punishing for the user because hours of processing time can be lost because of a recoverable problem.
Please just pause processing instead - give me the chance to make some room and continue. Especially with CQ and lossless compression it can be hard to predict how much space the compressed file will actually need in the end.
Think of the environment... and the children, and everything.  |
|
| freedomdwarf |
| Posted: Oct 29 2011, 07:38 PM |
|
|
Advanced Member
Group: Members
Posts: 119
Member No.: 30166
Joined: 7-March 11
|
VirtualDub is not alone in this behaviour.
You will probably find that most software will halt if it runs out of disc space.
Although it might be a nice feature it is not likely to work as you would expect it to.
Most modern OS'es use a 'Write behind' and 'delayed write' processes so if you did manage to make more room it might not have gotten written back to the hard drive at the point that VirtualDub (or any other software) needs to carry on writing data. That, and the fact that with these type of errors there is no real way of knowing exactly how much data actually got written (if any) without interrogating the drive and it's dynamics makes recovery from this problem somewhat fraught with headaches and errors.
So unfortunately, although theoretically possible, it isn't very likely to be incorporated into standard software; VirtualDub included.
--------------------
Sometimes, intelligence means the obvious flies over your head! |
|
| phaeron |
| Posted: Nov 1 2011, 05:54 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
The situation on Windows is not quite that bad. Running out of disk space is purely an OS phenomenon, so buffering in the drive hardware doesn't matter, and typically NTFS allocates on write instead of on flush so data loss is unlikely. It might be possible to pause and restart on a disk full error as long as compression isn't being used, but I'd have to do some testing to determine feasibility.
|
|
| levicki |
| Posted: May 9 2012, 08:09 AM |
|
|
Advanced Member
Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07
|
| QUOTE (SenorKaffee @ Jun 5 2011, 10:03 AM) | The current behavior of VirtualDub is that it stops processing if it can't write additional data on the disk. I think this is needlessly punishing for the user because hours of processing time can be lost because of a recoverable problem.
Please just pause processing instead - give me the chance to make some room and continue. Especially with CQ and lossless compression it can be hard to predict how much space the compressed file will actually need in the end.
Think of the environment... and the children, and everything. |
Maybe the user will learn to always have enough free disk space in advance after the punishment? 
|
|
| phaeron |
| Posted: May 12 2012, 05:48 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
If we could avoid all problems through foresight there would be no need for error handling. 
In any case, consider this feature request added to the future list for consideration.
|
|
| Dowlphin |
| Posted: Apr 9 2014, 11:08 PM |
|
|
Member
Group: Members
Posts: 23
Member No.: 37864
Joined: 9-April 14
|
In fact, it would be generally great to be able to pause the rendering process, especially for bigger projects. While you can set the process priority to idle, it's still not free of certain interference. Might not be one of the most crucial features, but once the pause-when-disk-full is implemented, it's probably trivial to make it user-controllable, too. I guess the really awesome level of this feature is not tricky at all, but imagine you could interrupt the rendering project and continue it at a later time. (As long as there is a log file with info on where it was halted, which is probably easier to do than a smart analysis algorithm that figures it out without a log.)
OK, I'm phantasizing now. I'll stop.  |
|
| Altaf |
| Posted: Apr 10 2014, 05:57 AM |
|
|
Advanced Member
Group: Members
Posts: 75
Member No.: 36396
Joined: 9-April 13
|
1) Windows can warn about the place termination on disks in advance.
2) Immediately, come into a status window VD.
3) Put the slider "Speed limit" on the left edge.
In you there will be a lot of time to clear a disk.
4) Place the "Speed limit" slider on the right edge.
Phaeron It can be used as a pause?!
- to press the pause button - "Speed limit" = 0.
- to press the pause button - "Speed limit" = 100%. |
|
| Altaf |
| Posted: Apr 10 2014, 06:05 AM |
|
|
Advanced Member
Group: Members
Posts: 75
Member No.: 36396
Joined: 9-April 13
|
del |
|
