Force-Attuned_Krogoth wrote:I use Vdub mostly for cutting clips. This means when I'm looking for a scene, I'm bouncing between a bunch of episodes. The shortcuts come into play because I used DVDFab to rip. When you do this, it makes a chain of four subfolders before actually laying the files down. I find this cumbersome, but leaving the folders where they are prevents slip-ups later. For instance, if I have to re-rip an episode (for example, to catch an intro before the opening credits) I have to remember to move the files somewhere else and then match the filenames in avs script. Because of this, I set up a series of shortcuts to the avs files so I can have an index of sorts that doesn't need to be redone every time I change something.
This is the part I don't really understand. If your directory structure is so variable that it could easily break, then the best option is to make sure the scripts and videos are in the same folder, or at least easily within striking distance, and use relative paths. That information always seems to be missing or outright ignored by the guides, but AviSynth doesn't require you to use the full C:\yadda\yadda\yadda file path. If the scripts are in the same folder as the videos, just the filenames themselves will work, as would something like yadda\filename.ext, if the script was in the next folder up. That way you can move files around without fear of them breaking because things aren't in just the right place (and DGIndex
can be set to use relative paths if you turn the Full Paths option off, and since DGIndex can autogenerate scripts, then you wouldn't have to worry about modifying them yourself). You just have to make sure the scripts are always either with the videos or in the same position in relation to them. It doesn't affect me because I just throw everything in one folder anyway.
The reason I'd prefer to set Vdub defaults is because clipping doesn't lend itself well to batch encodes. When I need a clip, I dig through the source, find it, cut it out, and drop it into my timeline before I forget. Thus I'm opening and closing instances of Vdub and each time I have to change the encoding from uncompressed to LAGS, and change from full processing to fast recompress. Yes, I could keep doing that manually, but what good is a labor-saving device that doesn't save labor?
I'm not very well-versed in avisynth scripting. If there's some way to have it feed configuration data to Vdub, that'd be an optimal solution. Even if it disrupts stability with other programs, I don't open my source in any other programs. I could make my index a series of shortcuts to Vdub that autoload config and avs files. But then I'd lose my direct association to the avs files when I want to edit those.
No, it's not possible for AviSynth to make VDub load its own config files. That's where using VDub's command-line interface comes in, as it's fully possible there. I'll explain something about this later.*
Also, it might be worth looking at the newest version of VDub proper (currently 1.9.5) rather than VDubMod, which hasn't been updated in 2-3 years, depending on which version you're looking at - I'm not totally up on the associated colorspace handling changes, but from a cursory readover it seems as though it's now possible to retain colorspace no matter which mode you have it set on. Whether it still incurs a conversion to RGB in the middle if set on Full processing mode I don't know, though. The newest version(s) also include a batch encoding wizard.
*Let's try something. Have the *.vcf file (myconfig.vcf, for example) set only Fast recompress mode and the Compression option. Then, make a new text file with this command in it (I'm assuming VirtualDub itself, not Mod; also take note I'm assuming
where VDub and the config file are located in the file system):
- Code: Select all
"C:\Program Files\VirtualDub\virtualdub.exe" /s"C:\Program Files\VirtualDub\myconfig.vcf"
Save the text file as vdublink.bat and close Notepad. Now, double-click on the .bat file. When VirtualDub comes up, is it configured and ready to go? That's about as much as you can probably hope for here. You could add that .bat file to your menu and just use it to load VDub when you need it instead of using the normal menu link to the program.