Clean up work path folder?

[TheBreen]

Pardon my noob question, but is there a way to automatically clean up temporary files in a work path once video_ts files have been successfully created in a destination path?

For example, let's say I want to batch process 4 projects overnight, each with custom bitrate settings using the segment viewer thingy. Wouldn't I have to use a different 'work path' for each project and therefore end up with e.g. ~20GB of temporary files left over from the 4 projects? Or is there another way to do this entirely?

[Rippraff]

Pardon my noob question, but is there a way to automatically clean up temporary files in a work path once video_ts files have been successfully created in a destination path?
No.

For example, let's say I want to batch process 4 projects overnight, each with custom bitrate settings using the segment viewer thingy. Wouldn't I have to use a different 'work path' for each project and therefore end up with e.g. ~20GB of temporary files left over from the 4 projects? Or is there another way to do this entirely?
No, not in the way you described it. Using the segment editor means you have to run prepare phase first, do your tweaking and save the project afterwards. Therefore you need four different working paths.

It is possible the 'normal' way, though, which means a complete backup (prepare/encode/rebuild) without interfering.
In this case you can save your project files somewhere outside the working path, set only one working path with four different output paths.
In this scenario your working folder will be overwritten in the 2nd/3rd/4th project ('Suppress warning prompts' must be ticked probably).

Cu Rippraff

[Calimari]

is there a way to automatically clean up temporary files in a work path once video_ts files have been successfully created in a destination path?


I use Ccleaner (http://www.ccleaner.com/).
Create a folder to be used only as a temporary folder for DVD-RB, then setup this folder in Ccleaner as a custom folder to be cleaned.
You could do a manual cleaning, or set it up to be cleaned periodically, eg. when you start your computer.
This isn't an ideal solution, but since DVD-RB doesn't offer this feature, it's better than nothing.

[TheBreen]

Thanks for the clarification. A clean up work folder(s) option wouldn't be a bad feature to add IMO, if you want to take advantage of the custom bitrates and batch processing features which otherwise doubles the disk space required.

[linx05]

If you're using batch then the files in the Work dir will only be overwritten for the next DVD.

[TheBreen]

If you're using batch then the files in the Work dir will only be overwritten for the next DVD.

Yes, but because the work files are overwritten in batch it means you cannot batch multiple projects with custom bitrates settings unless you use a different work folder for each project.

Of course, if there *was* a way to keep the custom segment editing settings for several projects in one common work folder without them getting mixed up or overwritten, then batch jobs would only add 4.32 GB disk space for every project added instead of double that (because of the need for separate work folders to remember custom bitrate settings). That would be as good or better than a temporary file cleanup function.

Again, unless there's some method I'm not seeing...

[jdobbs]

DVD-RB can't "clean it up" because there is no way of knowing when folks are done. You may want to edit and reencode, you may want to run a third party package, you may be in three click mode...

The only time it can be sure is when you do a PREPARE in that path again.... then it clears it before starting the PREPARE.

As for custom settings... if you cleared the directory -- they'd be gone. That's where they are stored.

[laserfan]

...your working folder will be overwritten in the 2nd/3rd/4th project ('Suppress warning prompts' must be ticked probably).I have thought for a long time now that DVD-RB needs some sort of "custom working/output directory naming/creation" feature. So if you want to queue-up 3 or 4 backups, you can do it while retaining all the temp files and not having to set-up separate working folders in advance.

Am I the only one who would find this useful--it seems like most everything ELSE I have ever thought "would be nice" has already been done...

[chainring]

@laserfan,

I used to use the "Output" directory feature, but have since turned that off and now just use the working for both temp and output files. When I'm going to do an encode, batch or not, I just create a directory under \Working with the disc label and point RB to it. Works nice and clean.

It would be pretty cool if RB could take, for example:
\DEAD_MANS_CHEST\VIDEO_TS
...grab "DEAD_MANS_CHEST" and use it for the working and/or output folder. If coming from a mounted ISO/disc, it would grab the label. That would be a nice little time saver...not much, but some.

[jdobbs]

I personally never use the output directory, I do everything in the working directory. In fact, on early versions of DVD-RB there was no output directory option. I added that as the result of a user request.

[chainring]

Oh, one great advantage to using separate work and output directories: Speed! Span your source, work and output on three separate drives, or at least two with work and output being separated, will speed up the rebuilding process quite a bit.

[jdobbs]

True, that. I use a single 250GB drive that I have dedicated for video... so it wouldn't make a difference in my case.

[laserfan]

Span your source, work and output on three separate drives...will speed up the rebuilding process quite a bit.Yeah, I do that too, for RB and every other video editing program I use (open from one drive/save to another).

[TheBreen]

In my case, I usually want to blank warnings/trailers and tinker with bitrates using the segment viewer, which means batch jobs require separate working folders for each project to retain customizations. It all works well enough and for that I am thankful.

I guess for these batch jobs I will just have to live with the disk space requirements of separate source, working and output folders (~16GB per project).