Log in

View Full Version : MeGUI: bug reports and feature requests


Pages : 1 2 3 4 5 6 7 [8] 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147

Cyber-Mav
20th December 2009, 17:19
whoa is this correct, i can see in taskmanager that megui has now launched x264_64.exe and encoding the same test clip i did with the 32bit version i averaged 10fps, now im getting average of 11.5-12.2 fps, 64bit version seems to have provided around 15%+ speed increase on my q9650 cpu.

what sort of difference are you guys seeing going from 32bit to 64bit version.

JoeH
20th December 2009, 17:34
Hi guys,

One feature I think that would be very interesting now that we are using the new X264 versions would be to allow files other than AVS scripts as input files. As X264 can now read many files directly without an AVS script, that would simplify at least certain encodes.

Cyber-Mav
20th December 2009, 17:54
ok my encode has finished with the 64bit x264 and looks like something has gone wrong here is the screenshots:

input source is vob file segment from starwars dvd short 3 mins 32sec long.

firsly here is what it shoudl look like encoded with the 32bit version of x264:
http://img297.imageshack.us/img297/8981/x26432bit.jpg

now here is the screenshot of the encode done with the 64bit version of x264:
http://img502.imageshack.us/img502/1458/x26464bit.jpg

as you can see its mashed up big time. decoder used was coreavc 1.9.5 in software and in cuda mode and still the 64bit version is mangled up output.

my test clip is 40mb big, if someone would like i can upload both the 32bit encode and the 64bit encode, both at 40mb big, and post links to them here. let me know if its required. im off to test again and see if i happens on other video.


actually after watching the scrambled video im wondering could this be a decoding issue as in when megui is feeding the video to x264? i used the 1059 build version thats 32bit only when i did the 32bit encode, then i downloaded from the first link the updated 1059 aka 1060 which enables 64bit x264 support. im going to try encoding again but forcing it to use the 32bit encoder. (probably rename x264 32bit version into x264_64.exe) and see what happens.

lnatan25
20th December 2009, 18:11
Cyber-Mav, did you have proper 64bit codecs and AviSynth for decoding the source? I also know that there is no 64-bit ColorMatrix for the 64-bit version of AviSynth, so maybe you used some filter that messed up? Perhaps you can post the AviSynth script?

Also, try opening the script in Media Player Classic Homecinema once in the 32-bit version and then in the 64-bit version to see if both decode fine.

Could also be due to some odd resolution, but such errors usually don't look like this.

Cyber-Mav
20th December 2009, 18:17
i use minimal noise filter.

pc is currently doing the 2nd pass of the encode using the 32bit encoder, avs4x264.exe is flagged as a 32bit app during the encoding in task manager.

i will retest again in few mins with no noise filter and then see the results.

as requested here is the avs script:

#Import required DLLs
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\Convolution3DYV12.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\Decomb.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\DGAVCDecode.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\EEDI2.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\FluxSmooth.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\LeakKernelDeint.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\NicAudio.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\TDeint.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\TIVTC.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\TomsMoComp.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\UnDot.dll")
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\VSFilter.dll")

DGDecode_mpeg2source("C:\Video Processing\video\video.d2v", info=3)
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 72, 0, -70)

LanczosResize(720,304) # Lanczos (Sharp)
Undot() # Minimal Noise

lnatan25
20th December 2009, 18:20
Do you see the ColorMatrix function call? Perhaps that is the problem. As far as I know, there is no ColorMatrix with the 64-bit version of AviSynth (could be wrong though).

Zathor
20th December 2009, 18:22
Cyber-Mav, did you have proper 64bit codecs and AviSynth for decoding the source? I also know that there is no 64-bit ColorMatrix for the 64-bit version of AviSynth, so maybe you used some filter that messed up? Perhaps you can post the AviSynth script?

Avisynth 64-bit is not necessary. The avs4x264 is a wrapper between the 64bit x264 and the 32bit avisynth.

i use minimal noise filter.

pc is currently doing the 2nd pass of the encode using the 32bit encoder, avs4x264.exe is flagged as a 32bit app during the encoding in task manager.

i will retest again in few mins with no noise filter and then see the results.

New Build in the first posting. I have finally removed the unnecessary LoadPlugin calls if the filter is not needed.

Can you please try to encode it with the same config with both x264 versions? You can do the trick the following way:
Enqueue your x264 64bit job, run it and then delete the tools\x264\avs4x264.exe and enque the new job and run it again. This time the x264.exe (32bit) will be used. Compare both files.

EDIT: I assume at the moment that your 32bit encoding is rather old and has been encoded without weighted P prediction. Weighted P prediction has some issues in older codecs.

Cyber-Mav
20th December 2009, 18:22
ok the encode just finished with the 32bit version of x264 renamed to x264_64.exe and.... the video is still garbled up. so somethings not right here. i will do few more tests now. first with the noise filter removed, and then with the colourmatrix turned off.


ok scratch the above, let me download the new build and give it a go.

lnatan25
20th December 2009, 18:23
Thanks for clearing this up, Zathor. :)

Zathor
20th December 2009, 18:27
ok the encode just finished with the 32bit version of x264 renamed to x264_64.exe and.... the video is still garbled up. so somethings not right here. i will do few more tests now. first with the noise filter removed, and then with the colourmatrix turned off.


ok scratch the above, let me download the new build and give it a go.

My edit in the post above has been too late..
So here again:
I assume at the moment that your 32bit encoding is rather old and has been encoded without weighted P prediction. Weighted P prediction has some issues in older codecs and will be not properly displayed. You have to disable weighted P in the encoder (not recommended) or have to use a new codec (recommended).

Cyber-Mav
20th December 2009, 18:35
nah my encoding on 32bit is proper hardcore man, here, i dropped the working 32bit video i encoded before i downloaded the 64bit enabled build of megui onto avinaptic. i use everything man, 3 b-frames, weighted p and b etc:
http://img687.imageshack.us/img687/617/x264settingsused.jpg

currently the video is encoding again using new build you linked me to.

the avs script looks lot shorter now:

LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 72, 0, -70)

LanczosResize(720,304) # Lanczos (Sharp)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise



///argh i just noticed i forgot to remove the noise filter this time damn it, its on the 2nd pass now anyways so i will try again without noise filter next, unless this new build you put up has sorted it out.

lnatan25
20th December 2009, 18:36
Two questions,
I extracted the developmental build, but it still says 1059. Is that normal?
Where is the setting to select the 64-bit encoder?

Thanks!

Zathor
20th December 2009, 18:44
Two questions,
I extracted the developmental build, but it still says 1059. Is that normal?
Yes, as soon as I publish it to the update server it will be changed so that everyone get the correct and new version.

Where is the setting to select the 64-bit encoder?
Nowhere. It will be selected automatically if a 64bit OS is detected (and avs4x264.exe is found)

lnatan25
20th December 2009, 18:49
OK, thanks, now a follow up with two more. :P

First, I have .Net Framework 4.0 (in addition to the others), and in the logger, it says ".x (..)" (this is what was causing an exception in the last build before your builds). Is this normal? I assume you do not use the framework version to determine wither the OS is 64-bit or 32-bit.
Second, how efficient is avs4x264 versus a native 64-bit AviSynth w/ codecs? Perhaps an option to select the encoding "path" (32-bit, avs4x264, native 64-bit) would be best, even if only for experimental and benchmarking purposes.

nurbs
20th December 2009, 18:52
The problem with using native 64bit avisynth is that most of the avisynth filters aren't available in 64bit and therefore won't work.

lnatan25
20th December 2009, 18:54
Yes, I understand that, this is why offering a selectable option is best, in my opinion. Filters are not always needed, thus whenever possible, it would be best to use the native. :)

Cyber-Mav
20th December 2009, 18:55
Can you please try to encode it with the same config with both x264 versions? You can do the trick the following way:
Enqueue your x264 64bit job, run it and then delete the tools\x264\avs4x264.exe and enque the new job and run it again. This time the x264.exe (32bit) will be used. Compare both files.

ok im running it now, the video i encoded that used x264_64 and avs4x264 turned out corrupted as in the previous screenshot.
i deleted the avs4x264.exe file and started the job that was queued up. task manager now shows that only x264.exe*32 is now doing the encoding. as soon as it is finished i will post on here letting you know how its gone.

the encode is finished and it plays back perfectly fine. so the issue is most likely avs4x264.exe

im going to run another encode now i restarted megui and the updates downloaded new avs4x264 which i deleted previously. i will now remove the noise filter and see how it encodes in 64bit.

Carpo
20th December 2009, 19:20
i can confirm Cyber-Mavs issue as i am getting it here too using x264_x64, looks like the image is all squashed and going diagonally across the screen, will also try with x264 32bit and see if same happens

Edit: with 32bit x264 picture is fine

Zathor
20th December 2009, 19:24
Strange. I did also several encodings with the 64bit version and my files are ok.

Zathor
20th December 2009, 19:30
OK, thanks, now a follow up with two more. :P

First, I have .Net Framework 4.0 (in addition to the others), and in the logger, it says ".x (..)" (this is what was causing an exception in the last build before your builds). Is this normal? I assume you do not use the framework version to determine wither the OS is 64-bit or 32-bit.
Yes, I have fixed the .NET detection so that there will be no error anymore when an unknown version is found.

Second, how efficient is avs4x264 versus a native 64-bit AviSynth w/ codecs? Perhaps an option to select the encoding "path" (32-bit, avs4x264, native 64-bit) would be best, even if only for experimental and benchmarking purposes.
Native 64bit should be faster, but I cannot test it because nearly all of my plugins are 32bit only. Therefore MeGUI will not support it at the moment. If you want to test it you can write a small batch file.

Carpo
20th December 2009, 19:45
Strange. I did also several encodings with the 64bit version and my files are ok.

is avs4x264 a wrapper to make x264_x64 work? I only seem to have this with interlaced material, will try and find some progressive and test with that

Cyber-Mav
20th December 2009, 19:48
ok i tried again now using 64bit and this avs script:

LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 0, 72, 0, -70)

LanczosResize(720,304) # Lanczos (Sharp)
#denoise



i removed the denoise filter and still the image is garbled up. its deffo something to do with avs4x264 since i tried using avs4x264.exe along with the 32bit version of x264 and it still results in a grabled up image.

Cyber-Mav
20th December 2009, 19:50
ok im trying another encode now using this script:

LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Video Processing\video\video.d2v")
#deinterlace
crop( 0, 72, 0, -70)

LanczosResize(720,304) # Lanczos (Sharp)
#denoise


iv removed the colourmatrix as well now so will see how this effects the output.

and its failed again, image is all garbled up. 64bit is just not ready for prime time i guess.

horvathd
20th December 2009, 19:55
I found the following annoyance/bug in the 0.3.1.1059 version:

When I select the animation tuning then in the command line appears the --ref and --bframes commands with the correct number according to the preset and tuning. As far as I know it's not necessary the x264 will calculate these numbers.
Also when a tuning is selected and I change to preset then a --ref command appears with the number related to the preset without the tuning.

Zathor
20th December 2009, 19:55
Please try the vfw4x264.exe (rename it to avs4x264.exe).

Cyber-Mav
20th December 2009, 20:08
Please try the vfw4x264.exe (rename it to avs4x264.exe).

ok i will try this method now.

ok an update this method works, when vfw4x264.exe is renamed to avs4x264.exe the 64bit x264 encode plays back with no issues.

biggest problem with this is that im unsure if any of the filters will work, also the speed, renaming as the above dropped encoding speed down to 8.5fps.

regular 32bit encoding using the noise filter and colormatrix did around 10fps, and the 64bit version using the original avs4x264.exe did around 12fps (although the video playback was corrupted).

so all in all 64bit version is useless to me. how do i revert megui back to pure 32bit mode?

Cyber-Mav
20th December 2009, 20:42
actually never mind i worked it out i downloaded the stable build posted on the first page and thats sorted it now, its using 32bit mode again with no issues.

Carpo
20th December 2009, 20:54
i just renamed all the files and left 32bit x264.exe alone, nice and 32bit only now :)

Zathor
20th December 2009, 21:07
Thanks for the tests. I will do some tests on my own now and will then decide which 64bit mode will be implemented.

EDIT: AVCSource works with avs4x264, DGDecode_mpeg2source not. Anyone knows why?
EDIT2: New ev build in the first post. It will use vfw4x264.exe until the problem with avs4x264 has been resolved. In my tests it has the same speed as avs4x264 and the encoding is ok.

Cyber-Mav
20th December 2009, 23:03
i will keep my dvd vob file sample on my hard drive. when you have new version of avs4x264 i wll try again for you and see if 64bit encoding is fixed.

i didnt try encoding any hd source material but since you can replicate the problem with mpeg2 then i guess we know its an issue with mpeg2 decoding/frame serving.


since your method uses a wrapper to frameserve to x264 64bit does that mean that the filters can be used since they will be processed before the wrapper frameserves to the encoder?

Zathor
20th December 2009, 23:13
i will keep my dvd vob file sample on my hard drive. when you have new version of avs4x264 i wll try again for you and see if 64bit encoding is fixed.
Can you please try the new build and compare the speed to the 32bit one? For me vfw4x264 is faster than the 32bit one but I would like to have results from other systems.


since your method uses a wrapper to frameserve to x264 64bit does that mean that the filters can be used since they will be processed before the wrapper frameserves to the encoder?
Yes, you can use all filters.

Cyber-Mav
20th December 2009, 23:20
yes i can test this for you, also i just remebered that you have fixed megui so that it doesnt need to use any files outside of its own directory so i can make a new folder called megui64 and use it to do all your testing without effecting my current stable 32bit megui.

im installing now and will provide you with the test results.

Cyber-Mav
21st December 2009, 00:01
ok 64bit version you just updated has been tested the encoded video plays back fine this time with no issues.

64bit speed was between 8.6-9.0 fps during both passes.

yes i is browsing internet in small window and have megui encoding window on the side which im constantly monitoring. wish there was an automated way to do the speed checking. im going to run the 32bit version now and measure speed.

ok the 32bit encoder is finished now, and the 64bit one is faster.

32bit one encoded at 7.6-8fps during both passes. so a small advantage for the 64bit one.

although when the 64bit version was using avs4x264 it was running even faster than vfv4x264, although the final output was all corrupted.

simonb1975uk
21st December 2009, 00:08
Zathor I am getting the same thing happening. Where can I obtain this new build?

Thanks,
Simon

Zathor
21st December 2009, 00:16
Zathor I am getting the same thing happening. Where can I obtain this new build?
In the first posting is a link to the development build.

nakTT
21st December 2009, 01:56
Can you please try the new build and compare the speed to the 32bit one? For me vfw4x264 is faster than the 32bit one but I would like to have results from other systems.
Hi Zathor,

Is there any way for me to turn off the 64bit and only use 32bit? The reason is I want to compare the speed between both of them. As for 64bit, it works like a charm.

Carpo
21st December 2009, 01:58
rename the x64 x264 exe ;)

nakTT
21st December 2009, 02:02
Yes, I understand that, this is why offering a selectable option is best, in my opinion. Filters are not always needed, thus whenever possible, it would be best to use the native. :)
100% agree with you. At least we could have some kind of checkbox to enable it.

Strange. I did also several encodings with the 64bit version and my files are ok.
Me too. No issue whatsoever.

Thanks for the tests. I will do some tests on my own now and will then decide which 64bit mode will be implemented.

EDIT: AVCSource works with avs4x264, DGDecode_mpeg2source not. Anyone knows why?
EDIT2: New ev build in the first post. It will use vfw4x264.exe until the problem with avs4x264 has been resolved. In my tests it has the same speed as avs4x264 and the encoding is ok.
I have no problem at all with avs4x264. Works like a charm.

:thanks:

Mtz
21st December 2009, 03:32
In settings, the button for neroaacenc.exe is not working. For besplit is OK.

enjoy,
Mtz

magic144
21st December 2009, 03:35
great job Zathor - thanks for keeping this project alive :-)

[ReX]
21st December 2009, 04:58
About the AVI Muxer.

If you use input files with some characters such as "ã" or "ó" in the file name you get "No video source chosen!", that's because MeGUI is saving the AVI-Mux GUI job files as UTF-8, but if I save the same job file as UTF-8 signature (that's how AVI-Mux GUI saves it) or ANSI it works.

Edit:
I'm not a programmer, but looks like that changing from
using (StreamWriter output = new StreamWriter(File.OpenWrite(filename)))
to:
using (StreamWriter output = new StreamWriter(File.OpenWrite(filename), System.Text.Encoding.UTF8))
in megui/trunk/packages/muxer/avimuxgui/AMGMuxer.cs did the job (saves as UTF-8 signature).

Zathor
21st December 2009, 06:15
rename the x64 x264 exe ;)
The best way is to delete/rename the vfw4x264.exe. If you do it this way the wrapper will no be used at all and will not interfere with the test results. Btw the update check will notice that the file is missing.

In settings, the button for neroaacenc.exe is not working. For besplit is OK.

;1355335']About the AVI Muxer.
If you use input files with some characters such as "ã" or "ó" in the file name you get "No video source chosen!", that's because MeGUI is saving the AVI-Mux GUI job files as UTF-8, but if I save the same job file as UTF-8 signature (that's how AVI-Mux GUI saves it) or ANSI it works.


Thanks, will change/fix both things later.

nakTT
21st December 2009, 06:27
Strange. I did also several encodings with the 64bit version and my files are ok.
The problem arise when my input file is avi but no problem when the input is mkv (encoded using x264). Any idea why?

How can I easily turn off the x264 64bit option when I'm encoding using avi input?

:thanks:

Zathor
21st December 2009, 06:37
In settings, the button for neroaacenc.exe is not working. For besplit is OK.

;1355335']About the AVI Muxer.
If you use input files with some characters such as "ã" or "ó" in the file name you get "No video source chosen!", that's because MeGUI is saving the AVI-Mux GUI job files as UTF-8, but if I save the same job file as UTF-8 signature (that's how AVI-Mux GUI saves it) or ANSI it works.

New dev build in the first posting, but I had no time yet to test both changes.

Zathor
21st December 2009, 06:40
The problem arise when my input file is avi but no problem when the input is mkv (encoded using x264). Any idea why?

How can I easily turn off the x264 64bit option when I'm encoding using avi input?
Do you have the dev build which uses vfw4x264.exe or the old one which uses avs4x264.exe (if unsure, please redownload the dev build in the first posting and test again)? I'm asking because there seems to be no problems with vfw4x264.exe but I did not test it with AVI input yet.

nakTT
21st December 2009, 06:54
Do you have the dev build which uses vfw4x264.exe or the old one which uses avs4x264.exe (if unsure, please redownload the dev build in the first posting and test again)? I'm asking because there seems to be no problems with vfw4x264.exe but I did not test it with AVI input yet.
I think its avs4x264.exe because it is the first time you implement the 64bit x264 before complains arise.

Any rough idea on speed comparison between:

avs4x264.exe with 64bit x264

vs

vfw4x264.exe with 64bit x264

:thanks:

Zathor
21st December 2009, 11:09
Any rough idea on speed comparison between:
avs4x264.exe with 64bit x264
vs
vfw4x264.exe with 64bit x264

In my benchmarks there has been no real difference between both wrappers.

murtuza
21st December 2009, 13:22
Problem: It keeps erroring out when I try to encode. It doesn't give any error message at all. In the worker it starts the encode but not even a second later, encode stops and worker status changes to say "error". Any way to find out the error or any solution on why this problem would occur?

How to duplicate this problem: Well there's no sure way to duplicate it unless if you're running default settings on everything. I just used the basic blu ray profile that came with this developmental build provided at the beginning of this thread. I changed nothing, tried encoding in mp4 x264.

Now I'm not encode savvy but I'm willing to learn. Could it be that blu-ray type settings cannot be encoded in an mp4 container? Any other info you guys need, just ask ill post as quickly as possible. I tried several things including changing the profile, trying a different container, tried changing resolution from 1080p down to 720p, etc etc. Can't figure it out for the life of me. Ideas?

System Specs:

Windows 7 64 bit
Quad Core 2 Q6600
4 gig 1066 ram

P.S. I lurk doom9 alot for encode information, first time i had any real errors with MeGUI that wasn't already solved. I appreciate your efforts Zathor!


guys i am having the same problem he mentioned , i am trying to rip a DVD not a bluray , i tried Xvid , x264 both , but it is not working , it starts for a second and stops showing error
Well i am on windows XP SP3

[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1051
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Framework used : 2.0 SP1 (2.0.50727.3053)
-[Information] Hardware
--[NoImage] CPU : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
-[Information] Log for job1 (video, 2.avs -> )
--[Information] [12/21/2009 7:13:46 PM] Started handling job
--[Information] [12/21/2009 7:13:46 PM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\xvid_encraw\xvid_encraw.exe" -i "E:\Radio (Live in air) Untouched NTSC DVD9 UDR Exclusive\rip\2.avs" -pass1 "E:\Radio (Live in air) Untouched NTSC DVD9 UDR Exclusive\rip\2.stats" -bitrate 600 -kboost 100 -chigh 30 -clow 15 -overhead 0 -turbo -max_key_interval 250 -nopacked -vhqmode 4 -qpel -closed_gop -lumimasking -imin 1 -pmin 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -bmin 1 -par 1:1 -threads 1
--[Information] [12/21/2009 7:13:46 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [12/21/2009 7:13:47 PM] Job completed


here is the log
plz somebody help , struggling from 2 days on this :(
plz help
thanks
waiting

simonb1975uk
21st December 2009, 13:26
Zathor,

I can confirm that the new dev build works great for me. Excellent work! :thanks:

Simon

JoeH
21st December 2009, 15:29
Zathor,

I just tried the latest development build with vfw4x264.

It works great, and for me runs even slightly faster (between .5% and 2%) than the avs4x264!