On that page, you'd go for the ICL10 build, I believe it's the one right above the OSX build.Sabihato wrote:The second method Qyot27 mentioned sounds promising, since I'm not able to find the older versions of dBpoweramp and SSRC appears to be for MAC OS only.
Forewarning: this is more or less a crash course in using CLI apps - I also use Windows XP, so the methodology may differ a bit on Vista. It should still exist, though, so it may require a little Googling to find the exact way to do it on Vista (that is, if it doesn't work the way I describe).
wavi and VirtualDubMod are two separate methods - wavi's major benefit over VirtualDubMod is that it can handle files with no video stream, whereas VDubMod will reject video-less files. wavi also streamlines into batch scripts more easily than VDubMod can.I've downloaded wavi and extracted it. Unfortunately, it doesn't tell me where to place the contents and the applications flash momentarily before disappearing. I think I could use AviSynth to get this done, but the question is where should I include the script lines to convert the audio? In a blank, brand new .avs file or should I use one of my existing scripts I've used to modify the video portion of my DVD source (see example script below)?
Somewhere in there? And lastly, am I correct in assuming I'll be using VirtualDubMod to get the audio converted? Or the wavi application? Or are they both different methods in themselves? I appreciate just a little bit more instruction. Thanks, everyone.Code: Select all
MPEG2Source("C:\Users\********\Desktop\*** ****** *******\DVD_01.d2v", cpu=4) Deen("w3d,3,3,5") vmToon(strength=24) LanczosResize(848,480) ConvertToRGB32()
wavi is a command-line application, just as SSRC is (although on SSRC's benefit, it is able to link into GUI apps; there's a couple GUIs that can use wavi, but generally it's easier not to). That's why clicking on them makes them flash for a second and go away.
So, what you need to do is place wavi.exe into C:\WINDOWS or whatever that folder actually is on Vista (well, feasibly you could put it anywhere as long as you go into Windows' Environment Variables and add the directory to your PATH, but C:\WINDOWS is just easier most times). Now, you can either use Run to call up the command prompt and navigate into the directory your files are in to run the command (by typing in cmd and hitting Enter, then using cd to go up and down the directory tree to get to your files), or you can create a Windows batch script in that directory and avoid trying to wrangle with the Prompt at all. In which case, copy and paste this into a text file using Notepad (after saving, change the extension of the file from .txt to .bat):
Code: Select all
wavi "input.avs" "output.wav"
pause
Now, wavi uses the AviSynth script, so the frequency change has to be done in the script for wavi to recognize it. So, with your script as a reference, it would look like this with the frequency change inserted:
(new parts in bold; the change in formatting is to make it easier to acknowledge which parts are for the video stream and which parts aren't - AviSynth recognizes periods between functions the same way it recognizes the functions being on new lines)video = MPEG2Source("C:\Users\********\Desktop\*** ****** *******\DVD_01.d2v", cpu=4).Deen("w3d,3,3,5").vmToon(strength=24).LanczosResize(848,480).ConvertToRGB32()
audio = WAVSource("audio.wav")
AudioDub(video,audio).SSRC(44100,fast=false)
HOWEVER, if you don't want to change your video's script so dramatically, then you could load just the WAV inside of its own script, like so:
Code: Select all
WAVSource("audio.wav")
SSRC(44100,fast=false)
If it wasn't for the fact you use a 64-bit version of Vista, I would suggest you look at the Microsoft 'Open Command Window Here' PowerToy for XP - I don't know if it would work with Vista at all, but if it does, then I would expect it only would be able to work with the 32-bit version, as it integrates into Explorer as a Shell Extension. It would remove the need to do the batch script stuff, as you could just right-click on the folder name and bring up the command prompt already in the directory you need to work in, without having to navigate with cd commands. I suppose for the 64-bit version you could just make a point of using a 32-bit Explorer clone, like ExplorerXP and see if the Powertoy works with it.