Also old article to see https://web.archive.org/web/20230601203800/https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/d9029891-25e5-4ed1-ab31-9cae7c6c8eae/why-does-the-system-device-enumerator-report-different-list-for-the-video-compressor-category-on-a?forum=windowsdirectshowdevelopment
https://web.archive.org/web/20120709085619/http://doom10.org/index.php?topic=2135.0 In short {D76E2820-1563-11CF-AC98-00AA004C0FA9} AVI Compressor interface doesn't exist in 64-bit version of qcap.dll so only DMO filters are available and not VFW. It only shows DMOs registred in HKEY_CLASSES_ROOT\CLSID\{33D9A760-90C8-11D0-BD43-00A0C911CE86}\Instance\ 64-bit VFW codecs are only available in VFW supporting apps like VirtualDub64 not in DirectShow.
The reported x264vfw version belongs to me. But it also doesn't work with the x264vfw version of BugMaster (VFW codecs don't appear in GraphStudioNext x64). Explanation: a part of the Google AI answer to the "is there qcap.dll 64 bit version" questioon: Limitation: Many legacy VfW codecs (like x264vfw) are only accessible via DirectShow using the 32-bit version of the (qcap) DLL. So it's a limitation of the Win OS, not a codec registration problem.
64 bit version of x264vfw.dll is not properly registered
Solved it adding at the bottom (Extra command line): --sar 10:11
No. The previous information should be enough if they really want to fix a bug in their product. I doubt that the place in the x264vfw code (codec.c:1881) where the memory access violation occurs will be useful to them.
Thanks for the info, if there's anything more you can share by way of info I can share with Adobe, i'll re-open the dialogue and try and get them to change. Thanks for the time.
Hi. I tried to export using Adobe Media Encoder and it failed. This is Adobe's bug: they send a broken memory pointer (icf) in the ICM_COMPRESS_FRAMES_INFO message and therefore the codec crashes due to memory access violation. Ignoring this message is a bad idea because it signals the frame rate and therefore if you ignore it, all bitrates will be incorrect (as if it is always 25 fps). I also tried exporting to Xvid but it fails for the same reason.
Thanks for the reply. Selection is absolutely fine and shows up no problem, but did you try exporting in any of PP, Ae or Media Encoder? I'm forever greeted with this error on anything past v23.3 of their builds. Likewise with their latest big yearly update of software to V24.
ps. installed both versions of the codec (32 & 64) and tested across multiple PC builds.
What do you mean no longer supported? I tested Adobe Premiere Pro 2023 (23.6) and Adobe Media Encoder 2023 (23.6), both still support x264vfw codec selection when using the AVI output format. Have you installed the full version of the codec, both 32-bit and 64-bit?
What do you mean no longer supported? I tested Adobe Premiere Pro 2023 (23.6) and Adobe Media Encoder 2023 (23.6), both still support x264vfw codec selection when using the AVI output format.
Hello, In Adobes wisdom the latest versions of their software no longer seem to support this codec when exporting. It works fine to edit with, but refuses to export using x264 past the v23.3 iterations of their software. I've spoken to their customer support and they always come back with the same '3rd party codecs' line, and say any issues need to be resolved by the original author. Is there any chance this could be investigated? Many thanks
x264vfw even says in its name that it is a VfW (Video for Windows) codec, not DirectShow. in GraphStudioNext it is visible in Video Compressors as ACM/ICM type with category "DMO Video Encoder" and category GUID={33D9A760-90C8-11D0-BD43-00A0C911CE86} make sure that your application has the same bit depth as the installed x264vfw, or install the full version (both 32-bit and 64-bit).
Hi, I have installed the x264vfw encoder on my 64-bit Windows 10 machine, and I've written a small program using DirectShow APIs to detect all the available video compressors (Based on their "FriendlyName" tag ) installed on my system. However, I've noticed that x264vfw is not being detected. Can someone please assist me with this issue? Thank you in advance for your help.
There is a new version from 2020.
Output file lacks color range information ("Color range: limited/full" is missing)
Old post but in any case, with Nvidia you can do it, just look this https://www.youtube.com/watch?v=3UUR8cu3op8 & so search the samething but for AMD.
How do I send the anonymous usage data for x264vfw?
x264vfw should have been updated for a very long time. I have x264vfw (libx264_core_152_r2851bm_ba24899), and x264vfw is still not up-to-date. https://i.imgur.com/KNeIxrz.png
If by "dropped" you mean that capture side starts capture in 5 fps instead of 30 fps because your CPU is not fast enough to capture and encode simultaneously than x264vfw can't do anything about this (it encodes every frame it gets but can't encode something it doesn't get because it wasn't captured) and all you can do is to choose faster preset which will need less CPU to encode.
Sorry, but I don't under stand what you mean by "The problem is that the video is very dropped" or "the image is sharp but the movements are dropped." . Can you be specific (screenshots or sample) what exactly are your settings and what wrong with output? Preferably also post mediainfo text output for you encoded sample (like this https://pastebin.com/adD6qZRM).
I'm sure I am doing everything as I've always done when I used XP 32bits. The codec x264vfw is chosen in the app and Gspot always shows H.264 as codec with a ratio over 10000 thou I change the value in the codec settings.
Update: Skype and Evaer just work with the x86 version of the x264vfw codec. This way the bitrate can be set and limited. The problem is that the video is very dropped. When using the h.264 codec included in Evaer the video runs fluently, but there's no way to configure it to set a higher bitrate and the quality is very poor. That's why I want to use again the x264vfw codec. I tried to use the default settings of the codec, moved the bitrate, changed the preset from very fast to very slow but the...
Are you sure that x264vfw codec was used at all? "10Gb per minute " sounds like it raw uncompressed video without any codec i.e. x264vfw wasn't used at all. Check your output video in mediainfo and if it is not H.264 video than something is wrong with how you used x264vfw in you app (i.e. it wasn't choosed).
The codec worked fine when I captured Skype videocalls live with Evaer on Windows XP and W7, but since I moved to Windows 10 x64, the bitrate control seems to be disabled. It creates a file of tons of Gb (about 10Gb per minute recorded) and doesn't matter the value I set. I tried to capture video live with other software using the x264vfw codec and it happens the same, no way to set or limit the bitrate.
Bitrate control bug whe recording live.
Bitrate control
installer
I have selected following settings for for x264vfw for Camstudio. I'm sharing these settings so that if anyone can help me better it then please let me know.
codec doesnot work after install
1 detect by noname chinese antivirus out of 65 total, you're doomed brother
x265 vfw "Sample Aspect Ratio" not working
Hi. Are you planning to release new revision of x264vfw or is there a possibility? If it is Yes you can do it? It seems that x264 r2901 was released. When will new revision of x264vfw release? We are waiting to be released near soon. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary EDIT: Updated and Changed.
Hi. Are you planning to release new revision of x264vfw or is there a possibility? If it is Yes you can do it? It seems that x264 r2901 was released by videolan. When will new revision of x264vfw release? We are waiting to be released near soon. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary EDIT: Updated and Changed.
it does if you add the .dll to system32 and sysWOW64
it does if you add .dll to system32 and sysWOW64
it does if you add it to system32
virus on 64 bit
Thank you. I thought the small file produced by the first pass ("Premiere.avi") was actually the stats file itself and I got confused, because Premiere will overwrite it on the 2nd pass. I now see the extra files (x264.stats and x264.stats.temp).
Hi. There is no real video output during "Multipass - 1st pass"/ "Multipass - 1st pass (fast)" as like you used --no-output option. That is why you didn't get x264vfw.avi file (or would get empty/dummy output if you have used VFW output mode). 1st pass is only used to create stats files (x264.stats/x264.stats.mbtree) so encode output is discarded. After encoding "Multipass - Nth pass" you will get resulting x264vfw.avi, no need to change file name between passes (but you can if you want). If you...
Hello and thanks again for your wonderful work. Using Premiere and x264vfw in File Output mode for a 2-pass operation. In 1-pass CRF mode, I always get two resulting files, the one entered in Premiere (let's call it "Premiere.avi") and the one entered in x264vfw ("x264vfw.avi"), the latter being the final video file. In 2-pass mode (Multipass-1st pass) I only got one file: Premiere.avi which is a bit confusing. For the second pass (Multipass-nth pass) do I leave the filenames as is, or do I have...
Windows does not use x264vfw for thumbnails. You should use Icaros for that.
thumbnails for 10bit (high10) mkv files
Hi. Are you planning to release x264vfw with the latest commit on main or sandbox, or is there a possibility? If it is Yes you can do it? commit is below. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary latest commit: 2017-12-24 Cosmetics commit b00bcafe53a166b63a179a2f41470cd13b59f927 x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2018-01-06 Remove compatibility workarounds commit df90bdd7e931b498ae48f24b51284f62ef31d54a...
Hi. Are you planning to build x264vfw with the latest commit on main or sandbox, or is there a possibility? If it is Yes you can do it? commit is below. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary latest commit: 2017-12-24 Cosmetics commit b00bcafe53a166b63a179a2f41470cd13b59f927 x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2018-01-02 Remove compatibility workarounds commit de58a0decb29250525711bb75d920f3da59ab8d4...
Hi. Are you planning to build x264vfw with the latest commit on main or sandbox, or is there a possibility? If it is Yes you can do it? commit is below. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary latest commit: 2017-12-24 Cosmetics commit b00bcafe53a166b63a179a2f41470cd13b59f927 x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2017-12-24 Remove compatibility workarounds commit 794d351c523393c8de29daed03d63b5f2042c1b5...
Hi. Are you planning to rebuild x264vfw with the latest commit on sandbox, or is there a possibility? If it is Yes you can do it? commit is below. main commit: http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2017-10-26 Remove compatibility workarounds commit de281381ceed2c9f5e8756aa59349f6af5828e44
Hi. Are you planning to rebuild x264vfw with the latest commit on sandbox, or is there a possibility? If it is Yes you can do it? commit is below. http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2017-10-26 Remove compatibility workarounds commit de281381ceed2c9f5e8756aa59349f6af5828e44
Why is it not possible to use a qpfile for iFrames?
Hello, I've made an x265 video for windows encoder codec, based on the x264vfw and the x265 encoder library. Homepage is: http://mpxplay.sourceforge.net Discussion & new release informations can be found here: https://sourceforge.net/p/mpxplay/discussion/219198/thread/01da6315
Thank your for reply BugMaster, problem is solved when I set Preset: Ultrafast but then the file size went up ultra crazy. That video had only about 10MB recorded and CPU was not even being used. I wanted to find a way to keep that file size and fix that stuttering. So increasing Preset does it but at the cost of huge amount of video space. I am switched to AMD AMF and it's working properly once set the values also using lower disk space for same quality I think. It's about 100MB per 1 minute for...
Thank your for reply BugMaster, problem is solved when I set Preset: Ultrafast but then the file size went up ultra crazy. That video had only about 25MB recorded and CPU was not even being used. I wanted to find a way to keep that file size and fix that stuttering. So increasing Preset does it but at the cost of huge amount of video space. I am switched to AMD AMF and it's working properly once set the values also using lower disk space for same quality I think. It's about 100MB per 1 minute for...
Thank your for reply BugMaster, problem is solved when I set Preset: Ultrafast but then the file size went up ultra crazy. That video had only about 25MB recorded and CPU was not even being used. I wanted to find a way to keep that file size and fix that stuttering. So increasing Preset does it but at the cost of huge amount of video space. I am switched to AMD AMF and it's working properly once set the values also using lower disk space for same quality. It's about 100MB per 1 minute for an acceptable...
Thank your for reply BugMaster, problem is solved when I set Preset: Ultrafast but then the file size went up ultra crazy. That video had only about 25MB recorded and CPU was not even being used. I wanted to find a way to keep that file size and fix that stuttering. So increasing Preset does it but at the cost of huge amount of video space. I am switched to AMD AMF and it's working properly once set the values also using lower disk space for same quality. It's about 100MB per 1 minute for an acceptable...
Hi. It is due to hardware resources i.e. not enough CPU to simultaneously play game and make encoding in realtime. You should find the slowest "Preset" which would be still fast enough for your CPU i.e. probably something around "Veryfast" or "Faster". Also you should set "Zero Latency" tuning if you output in VFW mode in anything else than VirtualDub. And imho "Fast Decode" is not needed for you as you should optimize encoding here and not decoding.
Hello everybody, Recently, I am trying to find a good way to record games and I found out MSI Afterburner is what I want. It has support for x264vfw and I found out a nice compression size with good quality. But my problem, video is freezing and speeds changing while recorded. It's not due to hardware resources. Please take a look at my recorded video. I am also uploaded my current settings so could you please tell me which settings do I need to change? Current Settings: http://imgur.com/a/zhAnY...
Thank you for your reply. Indeed it seems that it seems that way. I think that there is no choice but to give up if it is behavior on x264 specifications. There is this in the log of the commit of x264. LZCNT implies SSE2 AVX2 implies BMI2 It seems that these two are involved in my environment. If this is the way it is probably LZCNT is actually used or I think that the same process is being done. And it also becomes as follows. Skip printing LZCNT under CPU capabilities when BMI1 or BMI2 is available,...
Thank you for your reply. Indeed it seems that it seems that way. I think that there is no choice but to give up if it is behavior on x264 specifications. There is this in the log of the commit of x264. LZCNT implies SSE2 AVX2 implies BMI2 It seems that these two are involved in my environment. If this is the way it is probably LZCNT is actually used or I think that the same process is being done. And it also becomes as follows. Skip printing LZCNT under CPU capabilities when BMI1 or BMI2 is available,...
Thank you for your reply. Indeed it seems that it seems that way. I think that there is no choice but to give up if it is behavior on x264 specifications. There is this in the log of the commit of x264. LZCNT implies SSE2 AVX2 implies BMI2 It seems that these two are involved in my environment. If this is the way it is probably LZCNT is actually used or I think that the same process is being done. And it also becomes as follows. Skip printing LZCNT under CPU capabilities when BMI1 or BMI2 is available,...
Hi. That probably was changed in this commit of x264. Not showing of LZCNT and BMI2 together now is normal. But probably due use of XP (where AVX is not supported) it now detects BMI2 but don't show it also without AVX while already have hidden LZCNT. IMHO it should show LZCNT without BMI2 in your case.
I tried using this revision, but I have a doubt so I will report it. When using the previous revision 43_2694bm_43159_fix, use of LZCNT and BMI2 was observed when checking with info log. It seems that use of LZCNT and BMI2 can no longer be seen in info log using this revision. Although I do not know if LZCNT and BMI2 were actually running in the previous revision, though. Of course, there was no problem with the previous revision. It becomes as follows. 43_2694bm_43159_fix: MMX2 SSE2Fast SSSE3 SSE4.2...
I'd also love to see this feature so we can use batch encoding in Magix Vegas and Adobe Premiere
oh! god apps... thank you very much. thank you your works. I will report if there is a problem.
I can't control what video info show (except really changing bitrate which it do) or how Sony Vegas mux output file. Do filesize correctly change when you change bitrate in x264vfw or filesize also always the same? Also your bitrate looks like uncompressed video bitrate. Are you sure Sony Vegas really use x264vfw during output?
X264 raises brightness when converting
codec for power riect 14 to burn and playback windows 10 64 bit
Hi. I have released new version: 44_2851bm_44825
Bump dates to 2017
yes it is possible with correct render settings, here is how you can do this https://www.youtube.com/watch?v=muNDIzNrB1s for any other assistance can read here https://www.downloadwab.com/sony-vegas-free
When will new revision of x264vfw release? current x264 is revision 2851.
When will new revision of x264vfw release? now revision 2851.
I've resolved this disconnecting and connecting the input / output pins
codec for power riect 14 to burn and playback windows 10 64 bit
Just got this with the latest 32bit GraphStudioNext and x264vfw: x264vfw [error]:...
That'll never happen. Ever! This is about x264vfw. Which is a codec. It has nothing...
Virtualdub: Append AVI Segment support
If you mean report like this (5 / 57) than this false positive. As for more proof...
I want to be able to encode to h.264 using Virtualdub. I understand installing x264vfw_full_43_2694bm_43159_fix.exe...
I'm using x264vfw as part of the K Lite Mega Codec pack build date 8. May 2016, 12:19:31....
Videoinfos not correct
Hi! I want to announce that I modified x264vfw to include it with modified VirtualDub...
Ok.. I got it working... just call setup with /S with capital S... I tried with non-capital...
By the way, sorry for multiple posting... I tried posting over e-mail but it was...
Hello Is there a way to install the codec package silently? We need to ship this...
Hi! I need to ship this encoding with our software, is there a way to make the installation...
Hi Is there a way to install the codec package silently? We have to ship it with...
Hi Is there a way to install the codec package silently? We need to ship the codec...
I think it's mostly about visual quality against compression speed. File size depends...
Hello everyone, just wondering if there's an x264 option that, alongside the target...
Hi, I have a question about the profile setting, it says in the tooltip that the...