VDub 1.88 (stable) 64-bit

[AaronAMV]

I haven't tried the 64-bit of DGIndex, because well, I can't find a download for it. I did what Viper_666 said to do on this thread, but still no luck. Now it's saying

This application has failed to start because libmm.dll was not found. Re-installing the application may fix this problem.

Script:

Code: Select all

LoadPlugin("C:\Program Files (x86)\AMVApp\DGMPEGDec\DGDecode.dll")
MPEG2Source("C:\Users\Aaron\Downloads\VIDEO_TS\SEV1.d2v")

It's only the basics to get it to work, is the LoadPlugin not right?

[Qyot27]

I haven't tried the 64-bit of DGIndex, because well, I can't find a download for it.

Thinking about it, I realized that it could be a version mismatch occurring, rather than an issue with not having a 64-bit DGIndex. The version of DGIndex used could be too new for that 64-bit DGDecode build. I had simply assumed there was a corresponding 64-bit port of DGIndex to go along with it. You need to make sure the version of DGIndex used was 1.4.6 - if you need to get that version, it's located here:
http://neuron2.net/dgmpgdec/dgmpgdec.html

You want the 'Executables' package.

Script:

Code: Select all

LoadPlugin("C:\Program Files (x86)\AMVApp\DGMPEGDec\DGDecode.dll")
MPEG2Source("C:\Users\Aaron\Downloads\VIDEO_TS\SEV1.d2v")

It's only the basics to get it to work, is the LoadPlugin not right?

Yeah, should be right. Is the path really 'Program Files (x86)', though? And is it just that you replaced that DGDecode with the 64-bit one, or is that the original that came with the AMVapp? The 64-bit DGDecode should be put in C:\Program Files\AviSynth 2.5\plugins - or the otherwise-corresponding folder if the path really has that (x86) addition to it and there is no C:\Program Files\AviSynth 2.5\plugins folder.

[AaronAMV]

It still didn't work. I got the 1.4.6 Executables package, swapped the DGDecode.dll, indexed it, and it still said the same message as before-- about the libmm.dll. And yes, the path is 'Program Files (x86)', that's what it installed under.

Code: Select all

LoadPlugin("C:\Users\Aaron\Desktop\_\rer\DGDecode.dll")
MPEG2Source("C:\Users\Aaron\Downloads\VIDEO_TS\SEV1.d2v")

The 'rer' folder is just where I extracted the DGIndex to.

[Qyot27]

It still didn't work. I got the 1.4.6 Executables package, swapped the DGDecode.dll, indexed it, and it still said the same message as before-- about the libmm.dll. And yes, the path is 'Program Files (x86)', that's what it installed under.

Code: Select all

LoadPlugin("C:\Users\Aaron\Desktop\_\rer\DGDecode.dll")
MPEG2Source("C:\Users\Aaron\Downloads\VIDEO_TS\SEV1.d2v")

The 'rer' folder is just where I extracted the DGIndex to.

Did you rename DGDecode64.dll? If not, then it's the one LoadPlugin should be referring to.

Still, the DLL missing issue is odd. From a cursory search, I found that it's possible it's an alias for libmmd.dll, which is sometimes needed for ICL builds to work correctly. Check C:\WINDOWS\system32 and see if it's in there. If it isn't, then go to this page and download it (it's at the very bottom; I dunno if you'd need 9.1 or 10.1, but you can get both of them, just in case the one you try first fails):
http://www.rarewares.org/others.php

You may also need to put it in the same folder with DGDecode.dll, but I'm not sure. Sticking it in system32 should be enough.

[AaronAMV]

So I SHOULD rename it, because I haven't. It's still named DGDecode.dll

I tried both versions of the libmmd.dll, put them in both system32 and the DGIndex folder, neither of them are working. It says re-installing the application may be solved. I'm assuming the error is talking about VDub itself, but I never actually installed it. I just start the program up.

[Qyot27]

So I SHOULD rename it, because I haven't. It's still named DGDecode.dll

Renaming the plugin isn't necessary, I was just getting confused. Just be aware of which version you're loading, is what I meant.

I tried both versions of the libmmd.dll, put them in both system32 and the DGIndex folder, neither of them are working. It says re-installing the application may be solved. I'm assuming the error is talking about VDub itself, but I never actually installed it. I just start the program up.

VDub doesn't need installation and never has - at least in the sense of programs that come with an installer (like Winamp, or iTunes). It's just an unpack-and-run type of program. The installation for VDubMod that occurs with AMVapp, for instance, is basically just doing the same thing, but because other programs in the package require more intensive installation, it's easier to streamline by packaging up VDub that way too. I don't know of any other advantage to doing up a fancy installer for it, anyway.

Go back to http://members.optusnet.com.au/squid_80/, and grab libmmd.zip (for x64) that's there. Unpack, and put the .dll in system32, or the folder with the 64-bit DGDecode.dll, and see if that fixes it. It may need to be registered, or in even more bizarre circumstances, need to be put in the sysWOW64 folder, even though I think that's strictly for 32-bit stuff (you could also try putting those ones from rarewares in there as well).











As an absolute last resort, though, do you need VDub to cut clips, or do you just convert the whole episode/movie/etc. and then use that? In the case of the first scenario, then I've run out of ideas. As for the second, then I'd suggest looking at mencoder (it comes with mplayer, independently from others that compile it, or through MeGUI's updater*), and making a Windows batch script to control it. Since Windows builds of mencoder can (usually) open AviSynth scripts, and can convert internally or using VFW to other formats, it can act as a replacement. But unless there's a 64-bit Windows build (I'm not aware of any, but it probably exists), then you'll need to use 32-bit AviSynth and 32-bit plugins when interfacing with it.

*I'd recommend using the MeGUI way of getting it, since it vastly simplifies things. MeGUI's installer can be downloaded from http://x264.nl/

When configuring the system, you'll want to add the folder mencoder.exe is in to Windows' PATH. On XP this is done through the Control Panel->System->Advanced->Environment Variables, and using the bottom pane (click on the Path line, click edit, and add the full path to the folder at the end). I don't know how to do it on Vista, but it could be nearly identical. You can also customize mencoder's configuration by editing mencoder.conf. It should be located in the 'mplayer' subfolder in the same directory as the .exe. You can specify several commands there so that all that has to be done in the batch script is this:

Code: Select all

mencoder "input.avs" -o "output.avi"

For instance, on my computer I have mencoder set up to convert to YV12 HuffYUV, without sound, while suppressing some of the useless warnings and forcing the FourCC to HFYU. My mencoder.conf file looks like this:

Code: Select all

ass=no
subcp=enca:ru:cp1251
fontconfig=no
nosound=yes
autoexpand=no
ovc=lavc=yes
lavcopts=vcodec=ffvhuff:context=1:vstrict=-1:pred=2
ffourcc=HFYU
force-avi-aspect=1/1

Any of those commands can be overridden simply by extending the command-line used in the batch script. For instance, if I want sound but all the rest of that stuff above still applies, I just need to do this (I think, I don't keep sound in the files too often):

Code: Select all

mencoder "input.avs" -o "output.avi" -sound -oac pcm

All the batch script entails is putting that command line in a .txt file much like you would an AviSynth script, renaming the file from .txt to .bat, and then double-clicking. If you want to do more than a single conversion (hence the name batch script), then the other operations go on new lines. Say I want to convert a video to DVD - this is what my batch script generally looks like:

Code: Select all

wavi "AMV Hell CE.avs" - | aften -b 192 - "AMV Hell CE.ac3"
mencoder "AMV Hell CE.avs" -o "4.3 23.976 AMV Hell CE.avi"
pause
hcenc_024 -i "4.3 23.976 AMV Hell CE.avs" -o "4.3 23.976 AMV Hell CE.m2v" -ini "C:\Program Files\HC023\024\4-3_23fps-6000.ini"
mplex1 "4.3 23.976 AMV Hell CE.m2v" "4.3 23.976 AMV Hell CE.ac3" "AMV Hell CE.mpg"

In this example, wavi extracts the audio and pipes it over to aften to convert to ac3. The next line converts the script's output to HuffYUV-YV12. After mencoder finishes converting, the 'pause' line stops the script so that I can edit the script to refer to the new AVI file instead - I also remove all the processing stuffs so it's just a simple AVISource reference. I then do as the instructions on screen say and press any button so the script starts again. HCenc 0.24 beta then takes the newly-redirected script and uses the assigned profile (the -ini parameter, which is pointing to one specialized for converting 4:3 ratio NTSC Film to ~6000kbps MPEG-2 with pulldown) to encode the m2v. Finally, mplex1 takes the .m2v and .ac3 and muxes them into an .mpg file I'll later give to my authoring program.

(Note: with stuff as long as AMV Hell CE I generally wouldn't use mencoder and just give the script directly to HCenc, but I'm illustrating the point that each line represents a different part of the process - if you wanted, you could call the same programs over and over, if it was necessary. I've batch converted several scripts' audio streams to WAV using wavi before, and all that takes is repeating the operation on new lines with different input and output files)

[Qyot27]

After mencoder finishes converting, the 'pause' line stops the script so that I can edit the script to refer to the new AVI file instead

That should be,
stops the batch script so that I can edit the AviSynth script

[AaronAMV]

Yes yes yes yes yes <33

I was doing the regular .dll before, not the 64-bit. If I could kiss you through my internet screen, I would. Thanks for all the help!