AVANTI - FFmpeg/Avisynth GUI (support thread).

[Chris K]

EDIT: July 1, 2011

AVANTI - Windows FFmpeg/Avisynth GUI


Avanti GUI is a free front-end for FFmpeg with the option to insert Avisynth as pre-processor.
It can be used with almost all Windows OS builds of FFmpeg (with Avisynth support).
It offers user friendly control over all basic and advanced FFmpeg options.
A number of template examples are included. There's no need to be familiar with Avisynth
to use the predefined Avanti/Avisynth pre-processor options.


Features:

+ Easy access to all FFmpeg codecs and basic encode settings.
+ All advanced FFmpeg options are available through user command addition.
+ All settings are saved and restored at the next session.
+ All encoder settings, user additions and scripts can be saved in template files.
+ Display of estimated encode time, remaining time and encode speed.
+ Option to set encode time limit (in minutes) to encode test clips.
+ Option to auto-shutdown your system after encoding and job processing.
+ Re-direction of FFmpeg screen output to Avanti GUI (hides FFmpeg).
+ Option to process system controlled 2-pass encoding.
+ Advanced batch job processing (with dynamic template support).
+ ES option to encode to mpeg2 elementary audio/video streams for DVD authoring.
+ Option to modify mpeg2 header flags (incl. 2:3 pulldown on 23.976 p).
+ Option to modify AVI header fields (FourCC and frame rate).
+ Selectable Avisynth AUTO and USER modes with build-in Avisynth Editor.
... (supports relative source paths that allow scripts to run from templates).
+ Internal Video Preview with Avisynth script preview (debug) option.
+ Option to use advanced Avisynth color correction (with preview).
+ Selectable FFmpeg/Avisynth crop/scale/pad option (with preview and calculator).
+ Support for the VirtualDub (*.vdr) frameserver format.
+ Option to convert PAL video source to NTSC destination and vice-versa.
+ Option to convert audio from PAL to NTSC and vice-versa (with pitch correction).
+ Option to expand luminance level from 16-235 to 0-255.
+ Avisynth SuperEQ (18 bands) preset editor with preview option.


You can download the latest Avanti release and find all other Avanti related links at

http://avanti.arrozcru.org or at http://videohelp.com/tools/Avanti

Chris K

[45tripp]

Great work!

job control is a particularly nice feature.

thanks for the time and effort

tripp

[autodidact]

I love this tool! Thank you for sharing your work.

[ricardouk]

thanks

happy new year

[Chris K]

happy new year

Yeah... we've passed twelve here

Happy New Year to you too and to all other members and visitors here at VideoHelp.com.

Chris.

[wiseant]

Thanks again Chris K - nice to you see back at videohelp.com

[Chris K]

Hi to all,

Uploaded AVANTI 0.2.2 revision 1 to MediaFire.com


This revision has the following changes:

1. Changed FFmpeg/Avisynth combo checking at startup to add compatibility
... with some new FFmpeg builds, other then from Celtic-druids.

2. Added "Skip FFmpeg/Avisynth combo check" to the "preferences"
... to be able to try very non-standard FFmpeg builds.

3. Improved the "Job Control Manager" with the following changes:

a. Changed the way message boxes appear to a more logical order.
... Dialogs are opened automatically when appropriate.

b. Changed the text of the "Warning" message box because it was rather
... cryptic and added a "Don't show this message again." option.

c. Source and destination dialogs now are set to main gui paths when you
... open the window.

d. The window can now be resized in both directions.

e. Changed the font used for the list entries.


Download Avanti 0.2.2 revision 1 at http://www.mediafire.com/?dcj5l9ixtio


Chris.

[Chris K]

Hi to all,


Uploaded AVANTI 0.2.3 - FFmpeg/Avisynth GUI (new version) to MediaFire.com


This version has the following changes:

1. Added Crop/Scale/Pad page with preview (FFmpeg/Avisynth modes)
2. Added MPEG/AVI tools option (2:3 pulldown and more).
3. Added Video TS offset (to correct async audio)
4. Added AVI and ES muxing (avi can also use TS offset).
5. Added FFmpeg threads to the "Preferences"
6. Improved startup check for FFmpeg version options.
7. Improved reporting on gui of FFmpeg encode errors.
8. Fixed bugs in "Demux video" (kept audio and unused commands).
9. Fixed (frame size) bugs in some example templates.
10. Fixed several minor bugs.
11. Updated chm Help for new options.


Download Avanti 0.2.3 at http://forum.videohelp.com/topic343287.html


Thanks again to 45tripp for his advice on Avanti and his successful efforts
to get a number of major FFmpeg bugs fixed.
(Dowwnload the latest FFmpeg version to take advantage of these fixes.)


Chris.

[45tripp]

again,
thanks for the time and effort on this nice tool.

tripp

[GMaq]

Hello,
I thought this project had left the building, I'm glad to see it's back, too much promise to be left unrealized. Thanks for your hard work and continuing this project!

[Chris K]

-
New FFmpeg Windows OS build SVN-r12572 at Celtic-druids (and mirrors).

This is the first version that appears with the "libavfilter" enabled. This should allow to
freely interchange crop, pad and scale commands.

Unfortunately the libavfilter in this version shows unpredictable behaviour on these commands,
even when used in the regular crop, scale, pad order that works well in previous versions.

We also found that "muxing" and even "demuxing" is broken again in this version.
Actually the use of the -vcodec copy command already causes FFmpeg to crash.

This version is unusable where it concerns the Avanti "Demux/Mux" options and the
Avanti FFmpeg "Crop/Scale/Pad" mode (use the Avisynth mode instead).

Chris

[Chris K]

Hi to all,


AVANTI 0.2.4 - FFmpeg/Avisynth GUI (April 2008 release) available.


This version has the following changes:

..1.. Added text window expansion (Avisynth editor, report/log etc.)
..2.. Added framecount to avs scripts to fix m2v source duration problem.
..3.. Added process order option to "Crop/scale/pad" (Avisynth mode)
..4.. Added load/convert option of cqm and xcm matrix files.
..5.. Added FFmpeg warnings log for job processing.
..6.. Improved single process logging (now shows FFmpeg warnings list).
..7.. Improved reporting of invalid process settings.
..8.. Improved mpeg/avi tools on file and process reporting.
..9.. Fixed bug in mpeg/avi tools (broken sequence end code).
10.. Fixed bug in "Crop/scale/pad" which changed source frame size.
11.. Made a number of "cosmetic" gui changes.
12.. Updated chm help for new features and added more context links.


You can read more and download Avanti 0.2.4 here at
http://forum.videohelp.com/topic343287.html


45tripp again kept a critical eye on the additions and changes during development.
Proven being always to the benefit of the final Avanti release and much appreciated.


Chris.

[ricardouk]

Thanks for the new version

Keep up the good work

Will try the new version tomorrow

[ricardouk]

Chris K, what ffmpeg version should i use with Avanti? the latest one? a specific one?

Thanks

[Chris K]

Chris K, what ffmpeg version should i use with Avanti? the latest one? a specific one?

Hi Ricardo,

In the appendix of the help you can call up the FFmpeg version report.
This is updated up to the latest "Celtic-druids" version SVN-r12665.
With this version I had problems with x264 encoding (the quality) and it seems to crash
with the libx264 on Pentium sse2/3 machines.
I run on a old Athlon XP 2000+ which has only sse and this don't crash on libx264.
I often use SVN-r10464 as a reference when I test other versions.

Chris.

[ricardouk]

Thanks Chris i was using version 9133 from here with avanti 0.23:
http://ffdshow.faireal.net/mirror/ffmpeg/

are these versions different from Celtic Druid ones?

[Chris K]

i was using version 9133 from here with avanti 0.23: http://ffdshow.faireal.net/mirror/ffmpeg/
are these versions different from Celtic Druid ones?

No... It is one of the mirrors of "Celtic-druid" builds and all versions are the same.

This is the official "Celtic-druid" link: http://celticdruid.no-ip.com/xvid

Chris.

[ricardouk]

Thanks Chris.

[SWBisbee]

I have a vob file, I'm converting to a mp4 with version 0.2.2 rev.1, it seems to convert it right, however when using version 0.2.3 it gives me an error: Seems stream 0 codec frame rate differs from container frame rate: 29.97 (30000/1001) -> 59.94 (60000/1001). This is the same vob file using the same settings as in 0.2.2 rev.1. Now I'm using version 0.2.4 which gives me even another error: Seems stream 0 codec frame rate differs from container frame rate: 29.97 (30000/1001) -> 59.94 (60000/1001), And No accelerated IMDCT transform found. I'm using ffmpeg version 9767. can you help? As I said version 0.2.2 rev.1 works fine no errors.

Thanks,
Regards,

[SWBisbee]

I found the errors in version 0.2.2.rev.1 also just had to scrool up to see them, can you please explain these errors, so I can understand whats going on?

Thanks,

[Chris K]

Now I'm using version 0.2.4 which gives me even another error: Seems stream 0 codec frame rate differs from container frame rate: 29.97 (30000/1001) -> 59.94 (60000/1001), And No accelerated IMDCT transform found. I'm using ffmpeg version 9767. can you help? As I said version 0.2.2 rev.1 works fine no errors.

These messages are not errors but warnings or even simply notes given by FFmpeg. Often you can ignore them. Because version 0.2.4 catches (and shows) more of the FFmpeg warnings, you didn't get them with 0.2.2 rev1 and you got less with 0.2.3.
I've got the frame rate differ warning (25.00 -> 50.00 in my case) also on mpg sources. FFmpeg sometimes sees things that aren't there or at least are not interpreted that way by other software.
The "No accelerated IMDCT transform found" warning is given on the audio stream. If you disable audio temporarily it should be gone. E.g. one I get on audio is "Invalid new backstep" on a divx (xvid) which is encoded with FFmpeg itself.

EDIT: http://forum.doom9.org/archive/index.php/t-118303.html

There's a option (press <Ctrl><S>) to process in FFmpeg console mode. You then get the full view on warnings FFmpeg eventually generates. AFAIK there's no list of what all FFmpeg warnings mean but as I said, a lot of them can be ignored. In cases they are of importance (e.g. buffer underflow), you have to take some action.
If your conversion goes fine and shows no irregularity when you play it back it's ok.

Chris.

[Chris K]

.
FFmpeg/Avanti newsletter (26-04-2008).


New recommended FFmpeg Windows OS build.

We've gone through a turbulent period the last few month's where it concerns FFmpeg.
A lot of experiments at the developers front and compiling problems at the side of the
(ever praised) Windows OS builds providers.
I recall mp3, xvid and x264 crashes and problems for users of older Athlon CPU's.
Thanks to the concern and efforts of Tripp (45tripp) who keeps up good contacts with both
developers and Windows OS builds providers, there now are stable versions available.
Tripp decided to compose his own builds out of the most recent stable codec libraries
and to leave off FFmpeg bells and whistles that are still at a (too) experimental stage.
Ramiro Polla, one of the major providers of Windows FFmpeg builds kindly offered
Tripp to host his builds and I (Chris K) highly recommend them as the most recent
and reliable to use with Avanti.

EDIT: Tripp's FFmpeg builds are available at: arrozcru.no-ip.org/tripp


Some encouraging Avanti statistics (for a developer).

1. This quiet thread had over 13000 views since it started at 31-12-2007.
2. This led to over 6000 downloads of the Avanti package so far.

Avanti is powered by Gui4Cli (gui4cli.com) and by its own additional dll's which are all
written in C and C++. Therefore Avanti is small and relies only on the basic Windows OS
resources. It should run without problems on W2K, WXP (tested) and Vista (reported).

Avanti can be copied to and run from any location on your system, doesn't write anything
Avanti related to locations other then your install directory and can be easily removed
if desired. It makes minimal use of the system registry.

If you want to read some user comments on Avanti, Google for: "avanti ffmpeg gui"

Avanti 0.2.5 will be available within a few weeks.
Thanks to all who showed their interest.

Chris.
.

[turnkit]

Is there a Bug Forum for Avani - ?

I am loading a quicktime .mov file and it is coming in as 720x496 instead of 720x486. Would like to give a sample file to someone who can look at this and see what's wrong.

Can anyone point me to the right place or person?

p.s. I was able to attach a 3 frame video file that shows the problem.

3f%20720x486nonsquare%20sample.mov

[45tripp]

Is there a Bug Forum for Avani - ?

I am loading a quicktime .mov file and it is coming in as 720x496 instead of 720x486. Would like to give a sample file to someone who can look at this and see what's wrong.

Can anyone point me to the right place or person?

here'a a good place.

it's not an Avanti bug though.
it's a bug with the gui's engine: ffmpeg.
a bug already reported.
something about codec settings for width/height within mov.

anyway...
feel free to report again,
unlikely to be fixed soon...

so,
to fix this now,
either remux to a more reasonable format,
or use Avisynth Force mode in Avanti to overcome this,
or do some cropping in Avanti to remove the borders,
or just leave as is, it's only 10 pixels.


tripp

[Chris K]

Hi to all,

AVANTI 0.2.5 - FFmpeg/Avisynth GUI (May 2008 release) available.

This version has the following changes:

..1.. Added tools menu with option to add user tools.
..2.. Added advanced frame size calculator (crop/scale/pad page).
..3.. Added conversion of VirtualDub trim/cut data to avs script.
..4.. Added support for segmented sources (Avisynth user mode).
..5.. Added line numbers to easier trace script errors (avs preview).
..6.. Improved insertion of Avisynth AUTO scripts (avs editor).
..7.. Improved process logging (now shows warnings immediately).
..8.. Improved file path storage (separate save for all options).
..9.. Changed template save/load protocol (please re-read help).
10.. Fixed bug in Avisynth editor (handling files with tabs).
11.. Fixed Avisynth normalize warning (broken after big changes).
12.. Fixed bug in MPEG/AVI tools that could cause a Avanti crash.
13.. Several minor bug fixes and changes.
14.. Updated chm help for new features and changes.

You can read more and download Avanti 0.2.5 here at
http://forum.videohelp.com/topic343287.html

Users that upgrade from a previous version and saved Avisynth user scripts
in templates, please re-read the help on templates.
There's a change in loading Avisynth user scripts within templates to prevent
overwriting the current script at the editor with undesirable "garbage".

Want to thank Tripp again for all his advice and comments,
especially on the frame size (calculator) and aspect ratio subject.

Comments, suggestions and bug reports are always welcome.

Chris.

[45tripp]

thanks for the release

[wiseant]

Thanks Chris K - I'll have to check out this new version . . .

[Chris K]

Hi Tripp and Wiseant,

Both thanks for your continuing interest in Avanti. I hope some of the new features will come in handy.
Anyway bug fixes and improvements make it always worth while to upgrade.

Chris.

[coolguy1000]

Hello I am new here and I want to report a problem when using the Avanti/Avisynth/VirtualDub/ffmpeg combination to transcode a *.vdr file to e.g. *.avi. I tested with the newest prgram versions.

The file format *.VDR I am talking about is not the VirtualDub frameserver format but the MPEG2-TS format recorded by the Linux VDR Recorder, a system to record DVB-Sat programs. Unfortunately the file ending *.VDR is the same like the VirtualDub frameserver is using and when trying to transcode a Linux VDR file to whatever target format using Avanti I will get the message:

Avisynth reports a VirtualDub[Mod] frame server error

This message also appears when clicking on "show source properties" in Avanti

When renaming the Linux VDR files from *.vdr to *.MPG e.g. then the transcoding starts.
Any idea that could solve the problem (renaming the file is surely one option). I will report if I find out by myself.

thx a lot
kai

[guns1inger]

Renaming it or demuxing the VDR file is the only solution