View Full Version : MultiX264 - exploring X264 encoding! (was MicroX264) - 08/10/2010
buzzqw
11th December 2009, 09:34
Hi all
MultiX264 is a simple gui, aimed for encoding with x264 codec in any way users wants
MultiX264 offers automatic encoding i 1 pass, 2 pass, CRF, QP,
Offers Preset and Tuning and custom x264 options
MultiX264 offers autocrop, denoisers, deinterlacers and powerful queue
It offers also the possibility to encode audio using ac3to or avisynth or ffmpeg
MultiX264 will automatically load all dll present in \filters folders
The input file can be processed using automatic avisynth decoder (ffmpegsource, dss, dgsource..), direct encoding using x264 (lavf, ffms, dss, auto...), or piping ffmpeg or mencoder
MultiX264 is bundled with beta release of x264 with filter support.
The filter support is used to apply crop and resizing when using direct x264 decoding
http://www.64k.it/andres/data/microx264/multix264-1.png
http://www.64k.it/andres/data/microx264/multix264-2.png
http://www.64k.it/andres/data/microx264/multix264-3.png
http://www.64k.it/andres/data/microx264/multix264-4.png
http://www.64k.it/andres/data/microx264/multix264_rev675.rar
update exe : http://www.64k.it/andres/data/microx264/MultiX264.exe
BHH
Guest
11th December 2009, 14:44
What development environment did you use? One of the downsides of MEGUI (IMHO) was the managed code and WinForms.
buzzqw
11th December 2009, 15:33
I develop all my applications with PureBasic http://purebasic.com/
very fast and clean code :)
BHH
Brazil2
11th December 2009, 22:13
I like it, light and easy to use :)
I had troubles when using the crop syntax of Avisynth + resize though, I got only a distorted top of the image at the end.
And also a suggestion: let us choose the format of the output, raw h264 or MKV or MP4. It would be nice to have the audio muxed as well since you are using MKVmerge it shouldn't be hard to do. And you could also use MP4Box for muxing video + audio in MP4 ;)
buzzqw
11th December 2009, 22:29
avisynth use is a little tricky .. i know.. but wasn't mean to be used "seriously"
about your distorted image.. please post the crop and resize values (or a image of the configure)
BHH
Brazil2
11th December 2009, 22:59
The source is 1920*1080 but the 'real' image part is 2.21:1
Crop 0,102,0,-102
Spline64Resize 704,320
Which is working fine in Avisynth. But at the end with MicroX264 I got only the top of the image vertically stretched.
And also I've just noticed that the final framerate is wrong: the source is 23.976 FPS but the final file is 25 FPS. Take care that you must send the FPS info to MKVmerge otherwise it will assume 25 FPS by default.
buzzqw
11th December 2009, 23:03
dont' add the "-" minus, just write as in example 0,102,0,102
thanks for fps hint
BHH
Brazil2
12th December 2009, 00:19
dont' add the "-" minus, just write as in example 0,102,0,102
That did it, thanks :)
amgeex
12th December 2009, 07:16
I suppose this gui will be actively mantained? Nice work so far!
Atak_Snajpera
12th December 2009, 19:02
@buzzqw
I think you should finally focus on one GUI. You've created so many guis but in fact all are more or less the same. Maybe it is time to go one step further and learn how to redirect console output to gui. Each your gui simply executes console which is a little bit lame in my opinion. If this is not possible in VB perhaps you should switch to Delphi. Also I see no percentage progress in console output. Take this as constructive criticism and not as personal attack.
Betsy25
12th December 2009, 20:00
I'm not will to be nor sound rude, but this also means HDConvertToX has (just like the previous one) reached the point where most open bugs are "too hard" to fix, and this one is (once again) started to silently lay the previous one to rest (once again) only to do the very same thing with this one once you get to the same point where fixing the same bugs is too hard ?
Sorry, It's also meant as a positive criticism, although it may clear sound otherwise, but I'm starting to see a pattern here.
prOnorama
13th December 2009, 02:30
+ simple .avs input accepted (without the program trying to override it)
- no (custom) x264 profiles (OK just 1 command line option), also after closing the program the custom x264 command line is forgotten;
- no ETA/progress percentage shown on x264 console;
- GUI doesn't let you set/remember default mode (always CRF while I'd want 2 pass as default);
- no possibilty to keep original audio (like AC3 from DVD)
- no x264 log saved after encoding
sreg0r
13th December 2009, 04:58
I guess all programs have their pros / cons. The most direct comparison I can make is to SimpleLauncher and for me I agree with most of prOnorama in that it would be good if it displayed an ETA, saved your settings from the last run and saved a log. I generally do my avisynth script manually first so being able to process them with this tool using a queue is really great and must commend you on a great new tool.
Sharc
13th December 2009, 09:35
Sorry to say that I see no justification for this GUI, I would rather prefer to see HDC being properly maintained - I hope HDC won't be silently abandoned. Of course it's entirely up to buzzqw how he wants to spend his time, but I am afraid users will have to report similar issues all over again......
medp7060
13th December 2009, 09:49
I recently start to test x264, hoping eventually I will use it in replace of xvid in my encoding. In the last few days of research, I just found there are so many GUIs overthere. I have tested a few and none of them are simple and easy to use. I come to a question: if only all the developers worked togther and got a GUI well-maintained and documented, like Xvid!
Dark Shikari
13th December 2009, 09:53
I recently start to test x264, hoping eventually I will use it in replace of xvid in my encoding. In the last few days of research, I just found there are so many GUIs overthere. I have tested a few and none of them are simple and easy to use. I come to a question: if only all the developers worked togther and got a GUI well-maintained and documented, like Xvid!Xvid never had an official well-maintained and documented GUI either, unless you mean AutoGK, which was hardly good either and certainly not official.
And if you think Handbrake, Staxrip, and Ripbot264 are all harder to use than any of the various crappy Xvid GUIs, you're pretty much nuts.
buzzqw
13th December 2009, 09:54
@Atak_Snajpera and others
Dont' warry Atak, since i am not a professional developer i don't get it as personal attack :)
i code for fun (not my profession) i and like to build something around x264/ffmpegsource/avs2yuv. Nothing more or less (btw i can read stdout/in .. i a am just a little lazy ;) )
I want create something that will no need update for x264 changing
Someone could accept it as a simple gui for x264 (as it want to be), or can see the another gui without the top features
this is a simple gui for x264. isn't aimed as fully replacement of HDC.
Never more isn't aimed as fully features x264/audio/dvd/whatelse gui.
Users should see it as way to encode file with x264.
So you will never see in this gui these :
- no (custom) x264 profiles (OK just 1 command line option), also after closing the program the custom x264 command line is forgotten;
- no ETA/progress percentage shown on x264 console;
- GUI doesn't let you set/remember default mode (always CRF while I'd want 2 pass as default);
- no possibilty to keep original audio (like AC3 from DVD)
- no x264 log saved after encoding
I actually have 2 project HDC and AutoMen, and both are fully in active development.
BHH
medp7060
13th December 2009, 10:14
Xvid never had an official well-maintained and documented GUI either, unless you mean AutoGK, which was hardly good either and certainly not official.
And if you think Handbrake, Staxrip, and Ripbot264 are all harder to use than any of the various crappy Xvid GUIs, you're pretty much nuts.
Sorry you missed my point. Lots of good developers worked togther and eventually produced the best xvid codec, which beats the DIVX! Gknot was one of the best Xvid GUI. it is for all levels of users, even for nuts like me!
prOnorama
13th December 2009, 10:21
@ buzzqw: Sorry but the points I listed above are hardly dependent on x264 features changing.
Anyway I thought this might be aimed at a bit more experienced users but like this it's not very user friendly. Or maybe it's aimed at newbies but I think they might find it too hard to use and too "non automated". So it's stuck in the middle I think...
I actually have 2 project HDC and AutoMen, and both are fully in active development.
But there are 5 programs listed in your sig (not counting this one) so :confused:
Anyway I'll leave on a positive note:
+ I really like the simple layout and looks of this GUI
Atak_Snajpera
13th December 2009, 10:52
I just found there are so many GUIs overthere. I have tested a few and none of them are simple and easy to use.
If RipBot264 is too complicated for you so you better stop thinking about video encoding at all! Even monkey knows how to encode in ripbot264 ;)
@buzzqw
Dont' warry Atak, since i am not a professional developer i don't get it as personal attack
I'm not a professional developer either. I just like things to be done properly. I was always wondering why HDC has to have such crazy version numbering??? v.2.2.525.3836 (HDC) Are you obsessed with number or what :) Even Windows has simpler version numbering.
I will say it again. Lord_Mulder made better gui and I see no reason to invent a wheel again. Just Focus on ONE project at time.
medp7060
13th December 2009, 11:12
I did not test Ripbot264, but I am doing it now. The first impressions is the font is too small to see. Played it for a few mins and my conclusion is you may be right, it meant to be for monkey. So I have to delete it form my HD. Not mean to be rude, it is not just what I am looking for.
nakTT
13th December 2009, 11:17
I did not test Ripbot264, but I am doing it now. The first impressions is the font is too small to see. Played it for a few mins and my conclusion is you may be right, it meant to be for monkey. So I have to delete it form my HD. Not mean to be rude, it is not just what I am looking for.
Why don't you give ASXGui a try? Or perhaps you can give "MeGUI Patched" version another try too.
ricardo.santos
13th December 2009, 11:45
And if you think Handbrake, Staxrip, and Ripbot264 are all harder to use than any of the various crappy Xvid GUIs, you're pretty much nuts.
@Dark Shikari:
You were all upset and started a new website when Neuron had a go at you here and you complained about his attitude but let me tell you something...your attitude towards newbies stink... you know more about x264 than the average person...so what? Is that sufficient to take a "jab" at every single newbie...enough is enough...why do the mods let this go unpunished?
Megui easy? lol, Staxrip? (it used to be), the only understandble x264Gui nowadays is in my opinion asxGUI
@Buzzqw
Congrats on the GUI, finally a Simple GUI, this way we dont have to put up with the not so funny comments made by Shikari.
Dark Shikari
13th December 2009, 11:58
you know more about x264 than the average person...so what? Is that sufficient to take a "jab" at every single newbie...enough is enough...why do the mods let this go unpunished?What does x264 have to do with it? You can make a bad x264 GUI or a good x264 GUI. Knowing about x264 hardly helps you use a bad GUI. I have no idea how to use MeGUI.
Megui easy? lol, Staxrip? (it used to be), the only understandble x264Gui nowadays is in my opinion asxGUIWhere in the world did I ever call MeGUI easy?Congrats on the GUI, finally a Simple GUI, this way we dont have to put up with the not so funny comments made by Shikari.Where in the world did I flame this perfectly good simple GUI?
Stop putting words in my mouth. Attacking people is bad to begin with, but attacking them for things that they didn't even say is even stupider. Don't attack others for the splinters in their eyes when you're sitting on a pile of lumber.
Furthermore, stop trying to derail this thread. This is a perfectly good "simple GUI" and is by and large constructed correctly. It uses the Preset/Profile/Tune concept and isn't covered with custom x264 option checkboxes. There is no reason to fill this thread with stupid flames. If you want to whine at me, do it via PM.
Atak_Snajpera
13th December 2009, 12:09
the only understandble x264Gui nowadays is in my opinion asxGUI
you must be joking ,right?
you call this understandable?
http://img690.imageshack.us/img690/1691/new1j.png (http://img690.imageshack.us/i/new1j.png/) http://img690.imageshack.us/img690/new1j.png/1/w628.png (http://g.imageshack.us/img690/new1j.png/1/)
I have no idea how to use MeGUI.
I have the same feelings. That's why I created my own GUI.
morphinapg
13th December 2009, 14:55
you must be joking ,right?
you call this understandable?
http://img690.imageshack.us/img690/1691/new1j.png (http://img690.imageshack.us/i/new1j.png/) http://img690.imageshack.us/img690/new1j.png/1/w628.png (http://g.imageshack.us/img690/new1j.png/1/)
1. That version of the GUI is outdated, use the default view: Click File - Use Wizard GUI. Much nicer interface.
2. Visual Crop is coming in 3.0, along with a few more visual processing capabilities.
3. Inverse Telecine is done by selecting "Deinterlace" and "Convert Frame Rate" this is explained in the Guide, and many files can be set to automatically detect telecining and check deinterlace and convert frame rate.
4. Not sure why the tabs are hidden. As I haven't used this version of the GUI regularly in over a year I don't usually pay too much attention to it when updating ASXGui. In fact, the "classic" interface will be gone as of 3.0. I'll fix the tabs in the next version (2.5) in case anybody still uses the classic gui, though I hope people will learn the other gui as I said, the classic gui will be gone in 3.0.
ricardo.santos
13th December 2009, 18:07
@Dark Shikari,
please stop pretending and dumb people down, its time that you stopeed that, and the messages in my inbox
from fellow users of this forum confirm what i said, please i repeat please stop your stinking attitude towards newbies if you feel you're too important to help them just politely shut up, whats the point of your attitude?
Now down to your cleverly disposed web/answer:
Where in the world did I flame this perfectly good simple GUI?
Stop putting words in my mouth. Attacking people is bad to begin with, but attacking them for things that they didn't even say is even stupider. Don't attack others for the splinters in their eyes when you're sitting on a pile of lumber.
First of all did i say you were flamming the GUI? english might not be my first language but im pretty sure i never said that...what i said was:
...your attitude towards newbies stink...
dont put words in my mouth, like i said and this might get me banned but your attitude towards newbies "stink", do i need to say it in another language so that there are no doubts of what im saying, in my personall opinion and the fellow users that sent PM's supporting what i said is that if you're going to be like this all the time just politely shut up if you feel you cant be bothered to help newbies...furtherwore the comments you make towards first time useres speaks for itself...
ricardo.santos
13th December 2009, 18:11
@Atak_Snajpera
i dont need visual crop for my video sources, i open the file with asxgui, setup the video tab, audio tab, container, and convert, the way you inserted the screenshot here makes it look like a big window with all those options in it when in fact its several tabs, one for video, audio etc...
Im not saying yours is bad but for what i need asxgui is the best for me along with Minicoder
medp7060
13th December 2009, 23:45
Everybody is different. Some are clever, some are dumb (?), some are helpful and some are arrogant…Although I have been on this forum for many years, most of time I look for helps, I would say in most cases, I was helped by people out there. However, I am still a newbie and I am not a programmer. Developers write programme, I test them and see if they are the one I want. When I started to look for a X264 GUI and simply found there are too many, I tested a few, either failed to work for various reasons, or too complicated. Of course, I am learning x264 and I have not tested all. I expressed my wish that all the developers of all the GUI worked together and presented users a GUI that will suit all levels, e.g. simple for beginners, powerful for advanced ones, through a ways e.g. hide advanced options for beginners, but they can be accessed if you want. One of the GUI I tested was MeGUI, unfortunately, the recent built has all sorts of problems.
...
Stop putting words in my mouth. Attacking people is bad to begin with, but attacking them for things that they didn't even say is even stupider. Don't attack others for the splinters in their eyes when you're sitting on a pile of lumber.
@ Dark Shikari , x264 developer
@ Atak_Snajpera , RipBot264 author
I think it is not appropriate to call newbie “Nuts” and “Monkey”!!!!!! Everybody is good at something if not all.
morphinapg
14th December 2009, 01:28
I expressed my wish that all the developers of all the GUI worked together and presented users a GUI that will suit all levels, e.g. simple for beginners, powerful for advanced ones, through a ways e.g. hide advanced options for beginners, but they can be accessed if you want.
My GUI ASXGui was written specifically for this purpose. If you want, you can just drag and drop your file and click encode, or you can do basic processing or even advanced processing, all dependent on how much you know how to do. The advanced and basic options do not show by default. If you double click your video in the job queue you get the basic options, and if you click "advanced x264 options" from there you get the advanced options.
medp7060
14th December 2009, 05:25
Thanks, morphinapg. Will give it a go.
buzzqw
14th December 2009, 09:59
update exe (first post)
fixed framerate signaling
added support for leaving stream in h264,mp4 or mkv
little change on crop layout
BHH
ricardo.santos
14th December 2009, 11:02
Hi buzzqw, thanks for the update!
Any chance of custom audio and audio sample bitrate option? Where in the GUI can we find the option to change container? Is it when we are naming the output file?
buzzqw
14th December 2009, 11:31
about audio.. i will see.. i don't want to overhaul the gui
container can be selected only when saving output file. microx264 will ask for output file when you select input fle
BHH
Brazil2
14th December 2009, 15:00
My report:
FPS value is now correct for MKV :)
Audio and video are now muxed together for both MKV and MP4, great :)
but
container can be selected only when saving output file. microx264 will ask for output file when you select input fle
Actually this doesn't work as you expect. If I only select a file extension in the drop down list it always output to MKV. I have to manually add .mp4 or .h264 to the file name.
In this case output to .mp4 is working only after I have added MP4Box to the Application subfolder, because it's missing in your original package.
When you select a .h264 output, the .h264 file is not created in the selected output folder but in the temporary folder, the one which is created with the same name as the source file.
And the exact same WAVI command line appears twice in the job list instead of copying and renaming the output file to the selected output folder.
buzzqw
14th December 2009, 15:50
thanks
all fixed :) (apart mp4box that you should manually put in \application folder)
please update MicroX264
BHH
ricardo.santos
14th December 2009, 19:33
hi, buzzqw, the queue CMD has the first pass command twice when converting to MP4.
http://img31.imageshack.us/img31/816/microx264.jpg
RiCON
15th December 2009, 04:21
And with the latest update it just puts "--fps 0.000" in x264 command line.
Why not just use y4m output from avs2yuv and "--stdin y4m" in x264? That way you don't have to worry about knowing the fps nor the resolution.
buzzqw
15th December 2009, 08:16
@ricardo.santos
thanks, fixed!
@RICON
i don't know about this features, thanks, quite usefull
anyway microx264 must know the framerate because of muxing...
BHH
buzzqw
15th December 2009, 15:06
update microx264 added support for configuration file
create a file named microx264.ini in the same folder as microx264.exe
this is an example
Encoding Mode=2 pass
Preset=ultrafast
Tuning=Film
Bitrate=1500
Audio Codec=Aac
Audio Quality=50
Custom x264=--subme 3
MT Mode=1
MT Value=2,0
Resizer=PointResize
Before Resize#
After Resize#
BHH
Brazil2
16th December 2009, 00:23
update microx264 added support for configuration file
create a file named microx264.ini in the same folder as microx264.exe
Great idea, that helps :)
There is a little annoyance though: I have added ColorMatrix to the filters and I have added a line to the INI like this:
Before Resize=ColorMatrix(mode="Rec.709->Rec.601")
But when I run the program a part of this line has been cut off and it appears like this in the Before Resize box:
ColorMatrix(mode
Notice that typing the full line in the box is working fine and it's correctly sent to the AVS file. So it's just the program that stops reading the line at the = sign.
buzzqw
16th December 2009, 08:09
thanks, fixed
now use the # as separator
so the microx264.ini can be like this
Encoding Mode=2 pass
Preset=ultrafast
Tuning=Film
Bitrate=1500
Audio Codec=Aac
Audio Quality=50
Normalize=1
Custom x264=--subme 3
MT Mode=1
MT Value=2,0
Resizer=PointResize
Before Resize#ColorMatrix(mode="Rec.709->Rec.601")
After Resize#
BHH
Brazil2
17th December 2009, 12:32
fixed
now use the # as separator
Nice, thanks, it's now working fine :)
Little feature request: a box for setting up the audio delay (ms, negative values allowed).
buzzqw
17th December 2009, 13:40
sorry pal.. why this request ?
decoding is done via DSS..
BHH
dwrbudr
17th December 2009, 15:59
Open D2V, crop doesn't do anything. Preview shows this output from avisynth: The script return value is not a video clip. When I removed the last two lines from preview.avs I can play it in MPC.
last = isRGB(last) ? ConvertToYV12(last) : last <= remove
last = isYUY2(last) ? ConvertToYV12(last) : last <= remove
autocrop.avs: There is no function named autocrop?
buzzqw
17th December 2009, 16:23
please put autocrop.dll in \filters folder
i missed it
will put it in next full package
BHH
Brazil2
17th December 2009, 16:32
why this request ?
decoding is done via DSS..
Not for MPEG2.
FFMS2 is used for the video (VOB and DVB captures) and DSS for the audio which leads to huge A/V sync problems.
Or is there a way to force the use of DSS ? Because with FFMS2 and interlaced material bobbed with Yadif mode=1 the video is playing at like half speed. With Yadif mode=0 I'm getting the right speed but it's out of sync with the audio by several seconds.
buzzqw
17th December 2009, 17:11
understand
please update microx264.exe
and add in microx264.ini this line
Force DSS=1
BHH
Brazil2
17th December 2009, 19:46
and add in microx264.ini this line
Force DSS=1
I did that and now I'm getting this error:
Avisynth error:
I don't know what "movie" means
(F:\HAM\MicroX264.avs, line 13)
"movie" is not defined in the AVS file, the line is missing, but audio is there though.
buzzqw
18th December 2009, 07:59
thanks, fixed.
please update microx264
BHH
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.