Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
13th November 2014, 18:44 | #1 | Link |
Registered User
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
|
64bit Windows and Avisynth/Vdub
64Bit or 32Bit - Which platform is the right one if I want to work with avisynth (film- and video restoring) and Virtual Dub with more render power?
What about the filters and plugins? Will they still work with 64 Bit… I am especially into these plugins : despot, degrain, depan, remove dirt, remove grain, warpsharp, mvtools, etc….
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore |
13th November 2014, 22:42 | #2 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
64 Bit.
32 bit software works fine in 64 bit Windows and you have access to a lot more memory. The 32 bit apps will not, they get up to 4 GB with large address aware, but the rest of the OS can. |
13th November 2014, 22:59 | #3 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
There are not many plugins which were ported to 64 Bit, looking at your list it seems that you have to stick with 32 Bit. However, on a 64 Bit OS, you can utilize almost 4 GB for Avisynth32 alone which should be sufficient in most cases. |
|
14th November 2014, 11:10 | #6 | Link |
Registered User
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
|
thank You for Your input. But I still don't know… shall I go for 32bit OS or 64Bit?
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore Last edited by papcom; 14th November 2014 at 12:19. |
14th November 2014, 11:30 | #7 | Link |
Registered User
Join Date: Mar 2014
Posts: 308
|
You should always choose to install the x86-64 version of an OS over the x86 version unless you have very special requirements and know what you're doing.
1: Scripts are plain text files, and if you have the appropriate plugins for the appropriate architecture installed, they'll work just as well on 32-bit as on 64-bit. The only problem is that many older plugins do not have 64-bit binary releases, so it's generally less painful to stick to using 32-bit Avisynth. 2: The Avisynth+ installer installs both 32-bit and 64-bit DLLs by default.
__________________
Say no to AviSynth 2.5.8 and DirectShowSource! |
15th November 2014, 05:15 | #11 | Link | |
47.952fps@71.928Hz
Join Date: Mar 2011
Posts: 940
|
Quote:
It can pass 32/64 back and forth. Requires quite a bit of reading to understand how it works and some testing to get it right. I've not used it (enough to give any help). Just to pass the source indexed as x64 DGdecNV. MP_Pipeline 0.18 - run parts of avisynth script in external processes [2014-04-06] http://forum.doom9.org/showthread.php?p=1542161 the little work i did was not beneficial to my simple editing needs. but more complex scripts requiring x64 plugins would be better suited to actually use something like MP_Pipeline. The documentation provided in the archive provides much more reading material and examples.
__________________
Win10 (x64) build 19041 NVIDIA GeForce GTX 1060 3GB (GP106) 3071MB/GDDR5 | (r435_95-4) NTSC | DVD: R1 | BD: A AMD Ryzen 5 2600 @3.4GHz (6c/12th, I'm on AVX2 now!)
|
|
17th November 2014, 02:12 | #12 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
Quote:
OS: Use 64 bit. No reason to use a 32 bit OS for Avisynth & VirtualDub. Avisynth: 32 bit, it is more stable and generally works better. There is little advantage to >4GB of memory for even the most demanding of scripts (may change if using 4K) and the ecosystem is much more robust with 32 bit Avisynth. 32 bit Avisynth runs better in a 64 bit OS than it does in a 32 bit OS. VirtualDub: 32 bit, you need to use the same bitdepth as Avisynth. You probably still don't need more than 4GB of RAM so this is ok. x264: I like piping to 64 bit, 64bit x264 is faster. Piping has gotten pretty easy now and there are some good GUIs and guides for it. 32 bit x264 works as well if you wish to avoid piping. Last edited by Asmodian; 17th November 2014 at 02:15. |
|
17th November 2014, 02:29 | #13 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
Quote:
Edit: I see my "The 32 apps will not"; that was referring to the "accesses to a lot more memory" not weather or not they ran in 64-bit OS. I can see how it would be confusing for a non-native speaker. Rewritten to be more specific, maybe it is less confusing (maybe more confusing?). "32 bit software works fine in 64 bit Windows and you have access to a lot more memory. The 32 bit apps will not have access to a lot more memory, they only get up to 4 GB with large address aware, but the rest of the OS can access more memory so each 32 bit application can get the full 32 bit limit." Last edited by Asmodian; 17th November 2014 at 02:46. |
|
17th November 2014, 14:15 | #14 | Link |
Registered User
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
|
thanks a lot for Your detailed explanations. I have bought a Win8 Pro 64Bit OS and I will setup my 64Bit PC asap. Will report my experience when I am ready.
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore |
17th November 2014, 21:18 | #15 | Link |
Registered User
Join Date: Aug 2007
Posts: 374
|
Actually under 64-bit Windows 32-bit programs can use 64-bit code. I've even halfway written wrapper for 32-bit Avisynth to load 64-bit plugins but that died due to lack of time and interest.
Though that is of course very advanced topic and for newbies it's definitely better to explain "everything must have the same bitness in one process". As for original question: always go with 64-bit OS if not sure. |
18th November 2014, 01:41 | #16 | Link | |
ангел смерти
Join Date: Nov 2004
Location: Lost
Posts: 9,558
|
Quote:
|
|
18th November 2014, 19:27 | #17 | Link |
Registered User
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
|
which Versions of Avisynth and VirtualDub would You suggest for safest and effective Operation?
Lately I have used Vdub 1.10.4 and Avisynth 2.6MT on my WIN7 32-bit PC, and as an Editor AvsPMod 2.5.1
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore |
18th November 2014, 21:41 | #18 | Link |
Registered User
Join Date: Jul 2010
Location: Germany
Posts: 357
|
I'm using this:
- Win7 (64-bit) - AvsPmod - doing everything via GUI: VirtualDubMod (lets you save the "fast recompress" video option) + x264vfw + lame MP3 codec (ACM version) - doing everything via CLI: cmd.exe + x264.exe + lame.exe + batch files (Notepad2 / Notepad++ for editing) If you want the safest option, use 32-bit Avisynth without multithreading and split the video encoding into several parts that run concurrently (dunno if 2.6 is more stable than 2.58). |
18th November 2014, 23:10 | #19 | Link |
Registered User
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
|
i searched for virtualdubmod, but i did only find Releases from 2003. Which Version is the correct one and from where do I get VirtualDubMod?
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore |
18th November 2014, 23:13 | #20 | Link |
Registered User
Join Date: Jul 2010
Location: Germany
Posts: 357
|
http://virtualdubmod.sourceforge.net/
Yup it's old, but since it's only used for connecting data streams with encoders... |
Thread Tools | Search this Thread |
Display Modes | |
|
|