![]() ![]() Just as it is about to finish encoding, Virtualdub gives this error message: "Out of memory (unable to allocate 3923088 bytes)". I've run an Avisynth script that takes about 2.5 hours to complete on my system. Hopefully this should clarify things to avoid confusion.I'm not sure whether to post this problem here or in the Virtualdub area. ![]() I guess the same thing may happen on Win8ProĪdded later when found text above displaying incorrectly - Preview shows correct text but published text always shows incorrectly Then edited the "vidc.x264 value to just x264vfw.dll ( where the file is now in the windows folder ). So I copied x264vfw.dll into both Windows System32 and SYSWOW64 folders, to be sure Whilst this works on my Netbook, maybe Permissions or something else are different on Win7Pro it points to the dll file where it was installed in Program Files (x86) not in a Windows Folder, as are other codecs. I patched this in but that alone did not solve the problem This is blank but should be "x264vfw-H264/MPEG-4/AVC codec" One problem was that one key is incorrect. I am not an expert in these matters and therefore somewhat reluctant to play around with the Registry, so took the precaution of creating a Restore Point and backing up the Registry first There seems to be a problem with the installation on Win7 Pro, even though it had worked for me on my Netbook (Win7 Home Premium). I'm not exactly sure why you're attacking me as if I'm some kind of ignorant person but I suppose nothing I can do to change your mind. Reason I joined this late was because I always think thrice before wanting to ask, I always do my research, but not many topics regarding getting vfw on vdub which I prefer and any none of topics mentioned external encoding only in the experimental vdub versions(which I didn't use). For your information I've also read online often before making this post, which is how I am able to find an alternative solution being using avidemux+ avisynth. I'd go for the external encoder if I didn't fix my problem already with my klite update. I was responding to his comment about him asking that he has codec settings which I respond that I also have. I know people rag on XP users for refusing to use Windows 7 or 8 but those same people have been using Virtualdub for years and refuse to learn all the features that this program has to offer. There are guides on the Virtualdub forum showing step by step instructions on how to use the feature and a few Virtualdub users here who are willing to help. Putting x264 in an avi container isn't the right way to go, especially if you can create an x264 mp4 or mkv with the same program using the x264 command line encoder. I think what Budman was trying to say was with the newer versions of Virtualdub with the external encoder feature, there is no reason to even use x264vfw. ![]() updating klite mega seemed to make it work! Thanks everyone for the great help. I have the codec settings, it's just that vdub can't read it for some reason. Yes, there are other tricks to install them but they do not always work in Windows 7. Note for anyone interested: If you ever find you cannot run installs such as right clicking an INF file as administrator, I find it easier to just log out and back in as the actual user administrator and run it again. If you need this please PM me and I can send instructions. This is simple and I have a script to import that has MP4, FLV, and Mpeg2 already set up. You can also encode with VirtualDub Beta versions 1.10.3+ versions with external encoders. This file is an EXE file, I believe, and should be run as Administrator. I am not advocating installing the mega pack but only as a reference to the latest commercially used version of x264VFW. The latest x264VFW used in K-lite Mega pack is revision 2274. There are also several threads on the internet that mention uninstalling Virtualdub and codec packs and doing a fresh install. Make sure it is installed and registered. The actual codec is x264vfw.dll as noted below and shown in Virtualdub. Careful with changing registry entries unless necessary. My codecs were are not listed in the registry as above and still work. Mine looks likes this and works: check your settings. I have x264 installed as part of K-lite but if any x264 VFW is installed you should have a start menu X264 configuration item: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |