AutoFF (FFmpeg Gui) 0.99.7 - 14/08/2008

[buzzqw]

here my last bugs!

http://www.64k.it/andres/data/autoff/autoff1.jpg
http://www.64k.it/andres/data/autoff/autoff2.jpg
http://www.64k.it/andres/data/autoff/autoff3.jpg
http://www.64k.it/andres/data/autoff/autoff4.jpg
http://www.64k.it/andres/data/autoff/autoff5.jpg
http://www.64k.it/andres/data/autoff/autoff6.jpg
http://www.64k.it/andres/data/autoff/autoff7.jpg
http://www.64k.it/andres/data/autoff/autoff8.jpg

full package http://www.64k.it/andres/data/autoff/AutoFF0997_Full_win.rar

the application is at beta status

feel free to suggest / tell me bugs / missing tooltip..

BHH

[buzzqw]

update to 00.3

now works even without profile folder


@Mods

if you think to move this thread to another forum.. feel free!

BHH

[bond]

looks good :)

btw ffmpeg now also supports mkv output ;)

[buzzqw]

the container support is editable... feel free to write mkv (it will use as extension and for -f mkv ) (anyway in next update i will add it)

i have update to 0.04, some minor glitch with x264
and found a ffmpeg build that work with x264 http://www.64k.it/andres/data/autoff/ffmpeg_ok.rar
pay attention to modify the codec from libxvid/libx264 to h264/xvid if yoiu use this build

BHH

EDIT 005: added version of ffmpeg to title
EDIT 006: added threads parameter

[glb]

I think that the URL should probably be http://www.64k.it/andres/data/autoff/ffmpeg_ok.rar

[buzzqw]

@glb

thanks! corrected the url

feel free to post any errors!

BHH

[glb]

The acodec in the Xvid for Avi profile is mp3 but that caused errors when I tried my first encode and did not change it. No such codec or something similar. I had to manually select libmp3lame.

When I did not set the output folder my encode ended up in the AutoFF program directory instead of the input file directory as advertized.

Looking good so far!

[buzzqw]

When I did not set the output folder my encode ended up in the AutoFF program directory instead of the input file directory as advertized

fixed ! download the 0.07

about libmp3/libxivd/libx264 the problem is that old version of ffmpeg used mp3, new version libmp3lame

... i suggest to create your profile for your used version of ffmpeg.exe

btw anyone that want collaborate building profile (ipod/zune/apple tv... ) feel free to post!

BHH

[Sharktooth]

hint:
get the megui profiles and extrapolate the codec options

*** OR ***

create a megui profile parser and use the megui profiles

[buzzqw]

now that mencoder and x264 encoding is fixed i hope for a ne ffmpeg build that works

so i could do more test and update the x264 section of gui :)

BHH

[leiming2006]

seems useful.
I think I will have a try after I take my own computer to the university.

[buzzqw]

update to 0.07
the application is now working "well" :)

link in first post!

BHH

[weaver4]

Buzzqw: Are you doing this as well as AutoMKV and AutoMem? Do you ever sleep?

[buzzqw]

sometimes not..

anyway it's an hobby, and so.. we i have free time (maybe at work..) i code something... just to keep mind focused

also.. i need a ffmpeg gui.. so i do it!

BHH

[weaver4]

You ever seen a program call MPEG Mediator? It uses ffmpeg. It is very impressive when other apps won't keep audio in sync that program does (also AutoMEM does now too). I like it because it lets you get to the codec dialog box for the settings like VD. Anyway I think that the author quit work on it 3 or 4 years ago, but it still works.

I think it is still Sharktooth's favorite tool.

[weaver4]

What does it mean when I select an *.ifo file and it says "Please, check the Media properties."?

[buzzqw]

@weaver4

mpeg mediator don't use ffmpeg.. use flask plugins .. and it's SeeMoreDigital favourite ;)

What does it mean when I select an *.ifo file and it says "Please, check the Media properties."?
ffmpeg don't support ifo. only single file as input

BHH

[weaver4]

Your right it was SMD favorite. I thought it used ffmpeg, thanks.

So I need to combine all my Vobs before I use it? Now I see.

[buzzqw]

yes.. you need to merge it to one big vob

btw ffmpeg do it best when converting from some strange source to ... other strange source ;)

i personally prefer the d2v+avisynth approach for dvd related material

BHH

[an0n1m0us]

this software looks very interesting buzzqw

Congrats!

Is it open source?

[buzzqw]

@an0n1m0us

YES!

the windows build is a little old.. BUT the LINUX build are up to date AND compilable for Windows too.

http://forum.doom9.org/showthread.php?t=137044

here is the autoff 0.9 for windows (same build as linux)

http://www.64k.it/andres/data/autoff/AutoFF09.exe

BHH

[rkalwaitis]

Buzz This is nice, I like it so far. Where can I get the different setting for snow and what they mean? Your my hero, I wish I could work a computer like you do.

Thanks

[rkalwaitis]

Buzz it made a gorgeous snow codec avi file :) impressive for an experimental codec.

thanks

[buzzqw]

thanks for your kind words! )

if you have any link on snow&ffmpeg.. please post it

BHH

[buzzqw]

update win build to 0.99.7 full package here http://www.64k.it/andres/data/autoff/AutoFF0997_Full_win.rar

fixed snow encoding

BHH

[rkalwaitis]

You da man. How about these settings for a HQ CQ setting for snow. It rocks. Not the fastest but hangs in there. -vcodec snow -f avi -threads 2 -qscale 2.50 -cmp 12 -subcmp 12 -mbcmp 1 -qpel -vme=8 -refs 8 -last_pred 2 -strict -2 This is monster quality but at about 1-2 fps. Good compression and nice vid. For those who really dont care about file size.

good quality with a more respectful fps of 9-10 can be obtained with -vcodec snow -f avi -threads 2 -qscale 2.50 -cmp 1 -subcmp 1 -mbcmp 1 -qpel -vme=4 -refs 8 -last_pred 2 -strict -2

My experiments with 2 pass bitrate encoding produces green blocks. Ill let you know what is causing it if you didnt fix it with the latest build.

[rkalwaitis]

It does not work Buzzqw for snow. The problem may be that snow being an experimental codec will not work with ffmpeg unless you have the command -strict -2 in the mix. I noticed in your xml file that it is not present.

Thanks
Robert

[buzzqw]

the xml isn't important at all. Just select mpeg4 for avi, then change codec to snow, set your final size, and start it.

yuo will see in command line the strict 2 too

BHH

[rkalwaitis]

buzz i used the profiles from an earlier version as your updated didnt have them. Looks like its working. I still have no control over options do I?

[buzzqw]

no, i don't added any specific options for snow , just the strict parameters

i will check snow and will evaluate if add a panel for configuring it :)

BHH

[rkalwaitis]

thanks

[rkalwaitis]

Buzz the options I see for snow are:

vqscale 0.0 to 255.0 0 is lossless, anything over 10 is useless, around 3.0-2.25 produces nice looking files.

vpass activates internal passes, up to 3 of them **havent had much luck with multiple passes.

vbitrate used to specify CBR for 1 pass, ABR for 2 pass, no info no third pass that I could find. The codec default is 800 kbit/s.

lmin all codec not snow specific.
lmax all codec not snow specific.
vqcomp all codec not snow specific.
vrateol all codec not snow specific.
vrc_eq all codec not snow specific.
vrc_override all codec not snow specific.

cmp, subcmp, mbcmp
Set the comparison function, default: 0 (SAD).
useful values = 0 (SAD), 1 (SSD), 2 (SATD), 11 (5/3 wavelet), 12 (9/7 wavelet).
SAD is fastest and lowest quality.
SSD is the only function that makes correct decisions about intra vs
inter (mbcmp) when using fast motion estimation, but is not the best for
the actual search (cmp, subcmp).
The wavelet functions (use the one that matches pred) are best quality,
especially with vme=8, but are very slow.
SATD is a good balance.
You can add 256 to any of the options to enable chroma motion
estimation for that comparison (e.g. mbcmp=257 for SSD with chroma),
but it doesn't seem to help much for the moment.

pred=<0-2>
Wavelet type.
0 = 9/7 wavelet, default.
1 = 5/3 wavelet.
2 = 13/7 wavelet.
9/7 is probably better for for lossy coding, and 5/3 for lossless.
NOTE: 9/7 wavelet doesn't work with lossless mode.

qpel
Refines motion estimation, default: off.
This setting always helps compressibility, but costs some CPU time
both while encoding and decoding.

v4mv
Allows smaller motion partitions, default: off.
v4mv is theoretically good, but in practice isn't really working yet.
The current MB decision algorithm doesn't make very good use of this:
It improves quality, but also increases bitrate. (You could get
more quality per bitrate by reducing quantizer instead.)

vme=<4|8>
The default EPZS (4) is the same as in other formats.
Snow also supports iterative motion estimation (8), which jointly
optimizes adjacent blocks to make the most of OBMC. This significantly
improves compression, but is very slow.
Iterative ME currently does not perform scenecut detection, so should
be used only in the second pass of a two pass encode.

refs=<1-8>
Allows each block to choose which of several reference frames to
motion compensate from. Default: 1. Larger values always improve
compression, but cost lots of CPU-time when encoding and extra
memory when decoding.