AutoX264 (Multi Encoder GUI for X264) v.18

[buzzqw]

Here my new creation.. AutoX264

AutoX264 is a cross platform application (avaiable for windows and linux) that can use several h.264 encoders to deliver outstanding encoding on mp4, mkv or m2ts

On its basic way AutoX264 use mencoder , mplayer, xterm and MP4Box.

AutoX264 can decode/encode, using mencoder, ffmpeg,X264.exe, DGAVCIndex, DGIndex, FFmpegSource , near all files, from m2ts to avi, to mkv

AutoX264 also support MeGui X264 profiles

WARINING FOR UBUNTU USER: make sure you select options avaiable in your mencoder build.
b_adapt=2 isn't actually avaiable in ubuntu 's mencoder build (for example...)

here the link to AutoX264 0.18 version

Linux : http://www.64k.it/andres/data/autox264/autox264.tar.gz

Windows : http://www.64k.it/andres/data/autox264/AutoX264_v0.18.171.1640.rar
windows update : http://www.64k.it/andres/data/autox264/autox264.exe

AutoX264 Manual: http://www.64k.it/andres/data/autox264/manual/AutoX264%20Guide%20(Windows%20v.%200.15).html

The windows link (rar) is a FULL inclusive BUT remember to update with the executable autox264.exe

For Linux User: make sure you have installed mencoder/mplayer/mp4box.
You should already have installed xterm and gtk2 libs

Optionally you can install mkvtoolnix (for mkv muxing), and wine (and avisynth).. for using the windows full package (already tested and working)
For using MeGui profiles, just create a "profiles" folder and put here the xml files

Linux user should install mediainfo/mkvtoolnix/tsmuxer using repository

I have also tested linux autox264 windows with Wine, and it's fully fuctional (remember to install avisynth, and download applications pack)

Autox264 also support MeGui X264 profiles

WARINING FOR UBUNTU USER: make sure you select options avaiable in your mencoder build.
b_adapt=2 isn't actually avaiable in ubuntu 's mencoder build (for example...)

here some image

http://www.64k.it/andres/data/autox264/autox264-1.png
http://www.64k.it/andres/data/autox264/autox264-2.png
http://www.64k.it/andres/data/autox264/autox264-3.png
http://www.64k.it/andres/data/autox264/autox264-4.png
http://www.64k.it/andres/data/autox264/autox264-5.png
http://www.64k.it/andres/data/autox264/autox264-6.png
http://www.64k.it/andres/data/autox264/autox264-7.png
http://www.64k.it/andres/data/autox264/autox264-8.png
http://www.64k.it/andres/data/autox264/autox264-9.png
http://www.64k.it/andres/data/autox264/autox264-10.png

the application is tested on Ubuntu 8.04 Fedora 10 64bit, Windows XP SP3

BHH

[microchip8]

Good job buzzqw! :)

[mocham]

Kewl! I'll try it today!

The 0.7 version is just seg faulting on an Ubuntu Intrepid box, the 0.6 version is starting though.

[buzzqw]

@mocham
maybe corrupted file ?

try this http://www.64k.it/andres/data/autox264/autox264.07.linux.tar.gz

BHH

[Adub]

I can confirm. That link in the first post segfaults on Sabayon 3.5.1 x64bit.

The second link appears to be working.

Couple of things.

1) It would be nice to be able to resize the main window, as currently much of the options are half cut off.
2) Switching between crf and 2 pass does not cause a change in the crf or bitrate selection box.
3, but not so important) How about a little more color? It's pretty white.

But all in all, an excellent start!

[talen9]

Segfault confirmed here too (Ubuntu 8.10 64bit), here's the strace output:

# strace ./autox264e ./autox264

execve("./autox264", ["./autox264"], [/* 39 vars */]) = 0
[ Process PID=6436 runs in 32 bit mode. ]
brk(0) = 0xa041000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xfffffffff7eff000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xfffffffff7efe000
set_thread_area(0xff820300) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 6436 detached

[mocham]

@mocham
maybe corrupted file ?

try this http://www.64k.it/andres/data/autox264/autox264.07.linux.tar.gz

BHH

That one works, thanks!

[buzzqw]

thanks all for feedback and nice words :) !

some answers

It would be nice to be able to resize the main window, as currently much of the options are half cut off.
yep.. on purebasic isn't to so easy to do "dinamyc sizing" box.. but let me search about

Switching between crf and 2 pass does not cause a change in the crf or bitrate selection box.
when you select the 1 pass or 2 pass, you must simply edit the value reported on "Final MB (or CRF)", autox264 will compute bitrate to fit the specified MB size.
The "manual bitrate" is to "override" the compute of bitrate

, but not so important) How about a little more color? It's pretty white.
:p , any suggestion ?

BHH

[Henrikx]

Tested on Debian Lenny.
Works fine!!

:):cool:

[Adub]

when you select the 1 pass or 2 pass, you must simply edit the value reported on "Final MB (or CRF)", autox264 will compute bitrate to fit the specified MB size.
The "manual bitrate" is to "override" the compute of bitrate

Ah, okay. I am just used to a straight "Bitrate" interface. However, this way works to. Leave it like this.


:p , any suggestion ?

I will have to think for a little while. Mostly the biggest thing is color variance. When everything looks the same the human eye has trouble discerning difference in content. A deeper grey color for the background is not a horrible idea with some a slightly different shade for the buttons, as right now they blend in with the background, except for the shadow.


Also, is there a reason why all of my test videos are scaled? I inserted a basic 1280x720 video, that needed no cropping or resizing, and it automatically calculated a new resolution of 1152x632. However (1152/632)= 1.822784810126582278, which is nearly equivalent to the DAR presented in the information box, 1.8234.

And here I thought that the DAR was supposed to be 16:9. What am I missing here? Are you getting the DAR from some entry in the input file's metadata?

[buzzqw]

Also, is there a reason why all of my test videos are scaled? I inserted a basic 1280x720 video, that needed no cropping or resizing, and it automatically calculated a new resolution of 1152x632. However (1152/632)= 1.822784810126582278, which is nearly equivalent to the DAR presented in the information box, 1.8234.

the ar is computed by mplayer, you can always change the ar displayed to 1.7778, and autox264 will use this value

BHH

[Adub]

Okay, I thought it was something like that. Odd that it would choose 1.822.

[Adub]

Small bug report. When choosing the no_fast_pskip option, the generated commandline says "nodfast_pskip".

[buzzqw]

update the windows and linux build

thanks for the bug!

(also added support to subtitle)

BHH

[Adub]

Okay, we are getting there.

1) I don't think mencoder supports ssa/ass subtitle hardcoding yet. I just tested with an .ass file containing "This is a test!!", and the end video shows no output. I don't think that feature has been fully implemented yet. I would like to say I am wrong.

2) Feature Requests:
---Ability to save log.
---Ability to delete intermediate files, ex "autox264.h264", etc.

3) small bug, when in the subtitles tab, and the "mux to mp4" radio button is selected, if you select a subtitle file, the radio button jumps to "encrust in video"

[buzzqw]

autox264 will switch between encrust and mux if subtitle isn't compatible with mencoder ...
ssa subtitle isnt' directly supported by mp4box so is "encrusted" by mencoder
srt can be muxed and encrust
same fo ass

Ability to delete intermediate files, ex "autox264.h264", etc
already present, "Program Path"

Ability to save log
.. to be done (but not so easy, since application aim to be cross compiling..)

BHH

[Adub]

Quote:
Ability to delete intermediate files, ex "autox264.h264", etc
already present, "Program Path"
Ooops, my bad.

autox264 will switch between encrust and mux if subtitle isn't compatible with mencoder ...
ssa subtitle isnt' directly supported by mp4box so is "encrusted" by mencoder
srt can be muxed and encrust
same fo ass

Ah, it seems I was misunderstanding the meaning of "encrust". I thought it hardcoded the subtitles onto the video. I see now that it doesn't. The file that I tested with earlier just needed the subs (which I didn't know where there) enabled in the player.

[buzzqw]

encrust mean hardcode ... try with a srt

BHH

[Adub]

Weird. Because with a .ass it just muxes to the final output, even though "encrust" is selected. What I mean is that I have to select the subtitle in my player when playing the resulting video.

Okay, now I can't get any subs to burn in, be them ass or srt. The only way I can get srt to display is if I use the mux option, and even then they are only on for around 3 seconds.

[buzzqw]

could you please post the encoding bat (add to queue and post it (copy&paste)) ?

BHH

[Adub]

mencoder -vf harddup,crop=320:176:0:0,scale=288:160 -sws 2 -aspect 1.7727 -of rawvideo -o autox264.h264 -nosound -ovc x264 -x264encopts crf=18:threads=auto:bframes=3:direct_pred=auto:me=hex:subq=6:frameref=3:weight_b:trellis=2:mixed_refs:level=4 -sub "/home/****/Desktop/test.srt" "/home/****/End of the World 1.MP4.m4v"
mencoder -mc 0 -noskip -aid 1 "/home/****/End of the World 1.MP4.m4v" -ovc copy -oac faac -faacopts br=96:mpeg=4:object=1 -channels 2 -af volnorm=2 -of rawaudio -o autox264.aac
MP4Box -add autox264.h264 -fps 30.000 -add autox264.aac "/home/****/Desktop/test.mp4"

And it seems that my player was reading the subtitle files from the same directory, because the name was the same for both files. That would explain why I thought it was working earlier. I just have to rename my output mp4 to something different and the subs are no longer picked up externally.

[khaoohs]

I get an error when trying to pass a VIDEO_TS.ifo file to autox264.
http://pastebin.ca/1279739.

offtopic:
I'm just setting up a linux box for x264 encoding, so I"m new to this. I'm looking for single app encoding, so I'm also playing with handbrake.

Thanks

[buzzqw]

your mencoder build is probably outdated
please add the job to queue, then paste here the job
maybe b-adapt or psy-rd

BHH

[khaoohs]

buzz,

Sorry for not explaining it better. My initial problem was that I selected a VIDEO_TS.ifo file I had previously ripped to my hd. Then it autocropped the enitre frame, taking 720 from the top and 480 from the right. I have now manually cropped it am running an encode. We'll see what happens.

This may have *too* many options for me as I'm a noob to x264 encoding.

Is it possible for me to select a mkv container instead of mp4?

[buzzqw]

autox264 "actually" support only mp4

maybe in a future update i will support even mkv

BHH

[buzzqw]

update windows AND linux version (same link as above)
a little better resizing
added mkv support
added info on mencoder build used

BHH

[buzzqw]

(actually for windows.. later for linux)

added support for MeGui X264 profile's

in the same place as autox264.exe create a folder "profiles", copy in "profiles" all xml files from megui x264 profiles's

BHH

[buzzqw]

windows update
rearranged gui
added support for saving program path

linux build will follow later

BHH

[yeye69]

is it open source? :)

[buzzqw]

yes, gpl v3

source code, in purebasic, is avaiable on request

BHH

[buzzqw]

update the linux build too

BHH

[Adub]

Sweet!! Thanks for the MeGUI profiles support. I can't wait to get back home after break and play with this thing on my 64-bit Sabayon build.

[buzzqw]

please report any errors :)

BHH

[mocham]

Thanks for the MeGUI presets addition. Why aren't the presets listed in alphabetical order in your drop down list?

[buzzqw]

.. maybe i must rework the parsing profile directory ;)

EDIT: update the linux build, fixed the alphabetical order of profiles

BHH

[yeye69]

If I create a shortcut on the desktop and/or run autox264 from other directory than where autox264 installed, there is no profiles. This is a bug or a feature?

[buzzqw]

This is a bug or a feature?
it's look like a bug to me

windows or linux ?

BHH

[mocham]

If I create a shortcut on the desktop and/or run autox264 from other directory than where autox264 installed, there is no profiles. This is a bug or a feature?

Same issue here. Linux version, with Gnome desktop environment. If I make a launcher in the Gnome menu then I don't see the presets, if I run it from the directory I put the binary then the presets are there.

Thanks for fixing the preset drop down sort order! This is an awesome frontend!! :thanks:

[buzzqw]

update the linux build

fixed not profiles found when lauching auto264 from a link (thanks to yeye69 and mocham)

BHH

[yeye69]

It works, thanks!

But I'm confusing with a cropping. If I want to omit crop values, do I put 0 in these values or width x height? I need some clarity on this question.

[buzzqw]

update the linux build (again), just some gui glitch (and fixed the Donate button ... :p)

But I'm confusing with a cropping. If I want to omit crop values, do I put 0 in these values or width x height? I need some clarity on this question.

yes, for NO CROP but 0 on all values

BHH

[buzzqw]

fixed muxing on No audio (both for linux and windows build)

BHH

[Selur]

@buzzqw: did you find a workaround for http://forum.doom9.org/showthread.php?t=140261 ? (strange connection between sample rate and bitrate when encoding to aac audio)

[buzzqw]

well.. i don't pass sample rate to mencoder , i let mencoder select it (or can be selected by user) (and i use only mencoder, not ffmpeg)

can you use sox as a prefilter for sampling ?

BHH

[yeye69]

How about multiple sound tracks?

[buzzqw]

autox264 can handle input file with multiple audio tracks (change pid in audio options) , BUT can output only one audio track at time

BHH

[Selur]

can you use sox as a prefilter for sampling ?
one could, but the problem is this:
say you got a stereo source with 380kBit/s@48kHz and you want a 60kBit/s@48kHz stereo aac file with you end up with 96+kBit/s instead of 60kBit/s. So the problem is that the output bitrate strongly depends on the output sample rate if you just take the sampel rate of the input (48kHz) you can't get a bitrate around 60kBit/s you always end somewhere between 80kBit/s-160kBit/s and as far as I could test it then there's no way of knowing what the output size will be.
All in all it isn't really a problem if it doesn't bother you if you get a 60kBit/s or a 132kBit/s audio output. (doesn't kill you for normal dvd encodes aiming for 1CD+ but it's really a pain if you want some low bitrate encodes for the net; that's what I needed when I stumbled over this problem. :()

Haven't found a workaround for it myself and for low datarates I now use neroaacenc, just wanted to know if you were aware of the problem and may be knew a way to fix it.


Cu Selur

[buzzqw]

understud, that a pita

i will encode some sample files at different audio bitrate with autox264... just to look at audio bitrate

thanks for the input

BHH

[buzzqw]

update windows build
now autox264 propose the same input folder as output folder
when saving with extension "mkv" autox264 set automatically mux to mkv

BHH

[buzzqw]

update the windows build (later for linux)

added support for multi audio

BHH