AVANTI - FFmpeg/Avisynth GUI (support thread).

[bromberg]

Chris,

I never have a problem copying to & from the install folder & I am not running it frolm a cd/dvd drive. Also, I have no problem entering the AVSYSTEM folder.

Thanks anyhow but looks as if I'll have to move on. Do you know of another GUI fro FFmpeg that you would recommend?
Dan

[Chris K]

Do you know of another GUI fro FFmpeg that you would recommend?
Dan

So many! It depends on how "deep" you will go, starting of with WinFF up to probably something like Hybrid.

Take look here ... http://videohelp.com/tools/ffmpeg

Edit: Bingo, Hybrid isn't a FFmpeg gui ... LOL!

[bromberg]

Chris,

Thanks for your recommendation of other software comparable to Avanti. But before I totally give up on Avanti it occurred to me that since you'd mentioned this is an unusual error that perhaps I am missing a basic point. Do the FFmpeg files have to be located in a particular folder in order for Avanti to find them and install correctly? Do either Avanti or FFmpeg write to the (Vista) Registry?

Dan

[Steve(MS)]

Dan, I suppose you do know that you have to download ffmpeg separately and then place the ffmpeg.exe in the ffmpeg folder in the Avanti folder so it will work.
Now I have had an issue where I can't get the current versions to work on either Vista or Windows 7 but it might just be something I haven't figured out yet, may have something to do with having more than one version on my computer at one time.
Anyhow, the version that is working for me is is AVANTI - Version 0.6.6, along with the same time period ffmpeg static build.
Also I haven't used the avisynth with what I was doing....at least I don't think I was.
Anyway, you could back up to the version I have working and see if you have any luck with it.
I like Avanti for its speed, when I want a quick conversion but I am sure it will work for other situations too.
Oh, yeah, I drop a js32.dll file in the user tools folder also.
maybe you already knew all of this but thought I would write it out.

[Chris K]

Do the FFmpeg files have to be located in a particular folder in order for Avanti to find them and install correctly? Do either Avanti or FFmpeg write to the (Vista) Registry?

Dan

As Steve(MS) already mentioned... when you copied the whole Avanti zip contents to a folder, there's a folder in there named "ffmpeg". That's where Avanti expects a static or shared FFmpeg build. When you right-click on the "Start Process" button you'll find "Use other FFmpeg version..." on a menu. With this you can point to any location for Avanti to find FFmpeg but that supports only static builds.

FFmpeg doesn't write to the registry. Avanti only writes window positions to the registry.

[Steve(MS)]

Yes, I think I read only 32 bit static ffmpeg builds will work.

[Chris K]

Now I have had an issue where I can't get the current versions to work on either Vista or Windows 7 but it might just be something I haven't figured out yet, may have something to do with having more than one version on my computer at one time.

Do you mean with Avanti or don't they work at all, e.g. when used from the command prompt?

I have a whole bunch of versions on my system in a separate directory which I all renamed as ffmpeg_xxxxx.exe, where "xxxx" is the version number. When I'm testing Avanti I point to the desired version with the "Use another FFmpeg version" option and that always works. But I develop on Windows XP.

I never checked things out on Vista but on Windows 7 this gives also no problems. That is to say, when I found a location (drive, partition, folder) from where it runs stable.

[Steve(MS)]

Actually I have 2 different Avanti versions with their own ffmpeg.
For instance, I just placed Avanti version 069 in XP compatibility mode as well as its ffmpeg version.
It opens and says "system ready" at bottom but when I press "start process" after selecting input and output
the button presses inward, Like it is activated but it doesn't do anything, just as if i hadn't press the button.

Like I said, it is probably something that I need to do different but at this point, i don't know what.

[Chris K]

It opens and says "system ready" at bottom but when I press "start process" after selecting input and output the button presses inward, Like it is activated but it doesn't do anything, just as if i hadn't press the button.

Well, it's known that there are problems with Avanti on Windows 7. Didn't had much feedback from Vista users in the past but I know there was a problem with the use of Icons (ICO type) after I replaced them for gif strips it was solved.

I'm currenly testing a new version of the Gui4Cli language interpreter on which Avanti runs and hope to get it more stable on Windows 7.

[Steve(MS)]

I can still use the slightly older one so no harm there, the 066 is from Feb. 2012 so it isn't that old.

[bromberg]

Steve,
Thanks for your reply, however, even when moving the 3 FFmpeg 'exe' files ('ffmeg.exe', 'ffplay.exe' and 'ffprobe.exe') into Avanti's own 'ffmpeg' directory, I still get the same permissions error when starting Avanti-GUI.exe.

I'll take your advice and back off to the 0.6.6 version (from my current 0.6.9 version) and get back to you. Since I've never used Avanti or FFmpeg it's not like I'll be missing anything

Thanks again for your thoughts and taking the time to reply.
Dan

[Chris K]

I still get the same permissions error when starting Avanti-GUI.exe.

I looked into the code again which triggers this error message. Here's something you can do...

Look in the avanti/avsystem folder if there are two files named "codecs.dat" and "formats.dat". If not, rename "codecs.000" to "codecs.dat" and "formats.000" to "formats.dat". Then Avanti should continue the startup procedure.

It looks like if your system is slow in disk operations? This message shows up when Avanti fails to rename these files and waited five seconds for them to appear. Note that it always takes some time before a disk operation becomes visible for a application.

Please let me know! I could increase these five seconds in the next version if this is the probem.

EDIT: By the way, Avanti don't need "ffplay" and "ffprobe". Saves some diskspace

Chris

[Steve(MS)]

Dan, not that I am very astute with certain computer situations, but more or less I am curious as to what exactly is the permissions dialog box message say?

Before I used 066 version, I was using 062 version along with a contemporary ffmpeg static 32 bit version, no longer than it takes to download and try out, see what happens when you try these older versions, I haven't been able to get these newer versions to work.

Chris, no offense meant as I have enjoyed using Avanti, look foward to whatever you do in the future.
I know it took a lot of work for you to get the program up and running and making it better over time, thanks.

[bromberg]

Chris,

As you suggested, I renamed codecs.000 & formats.000 to codecs.dat & formats.dat but I still get the same permissions error window when I start Avanti-GUI.exe.
My system is slow to boot however, once fully booted it behaves reasonably well regarding I/O (i.e., my wait time is not noticeable once I am up and running).

Dan

[Chris K]

I don't know about Vista but these are the notes I give for Windows 7 users...

http://avanti.arrozcru.org/windows7.htm

For testing I'm running Avanti from seven different locations (long paths, short paths, shortcuts etc.).

There are always one or two locations that fail which varies with every new version or changes I make in the source code. Problem here is that it is totally unpredictable on what stage the program will hang during startup. It's hard to trace because on Windows XP it never fails.

[Steve(MS)]

Chris, what changes were made to the overall program between version 069 and 066?
In other words, I would assume you didn't make changes to many things, perhaps just a few.
Were changes made to the exe only or was there others?
Now both my computers are 64 so I understand that there is no guarantee with them but 066 plays on both
my Vista and Windows 7.
I have tried different compatibility settings but still can't get 069 to work.

Probably Just a wild misguided thought that parts of the old program can be blended with the new program?

[Chris K]

Chris, what changes were made to the overall program between version 069 and 066?
In other words, I would assume you didn't make changes to many things, perhaps just a few.

No, there were made many changes. Partly attempts to improve Windows 7 compatibility but also many to add, fix and improve features. I cannot revert that changes.

Were changes made to the exe only or was there others?

Actually the executable is a third party script interpreter with the Avanti scripts integrated. I did change the interpreter version in the mean time. Version 066 - 068 use the same interpreter. Version 069 uses an update. You could try 068 to see if it still works. I'm now working on 070 with just another update. I'm also testing a dll version of that interpreter which looks more stable on Windows 7. I might be switching over to that.

Now both my computers are 64 so I understand that there is no guarantee with them but 066 plays on both
my Vista and Windows 7.
I have tried different compatibility settings but still can't get 069 to work.

I have in general the most succes in the native Windows 7 mode but that's on a 32-bit version.

Probably Just a wild misguided thought that parts of the old program can be blended with the new program?

That would be a dangerous job that easily could corrupt the whole functioning of the program. Currently the main script is 14932 active lines (comments excluded). And all the *.gc files in the avsystem folder are also scripts.

[Steve(MS)]

Chris, I believe the change that caused the problem on Windows 7 and Vista was between 67 and 68 if this thread is any indication.

https://forum.videohelp.com/threads/347056-ffmpeg-version-N-41465-g53dfc38?p=2169668#post2169668

The reason I bring this up is if that may be helpful in some way if you ever want to look into the matter any further.
But since you are working on a new version, there may be no reason to worry with past versions.

Just for good measure though, I will see if version 68 will work on my computer, let you know a little later.

[Steve(MS)]

OK I tried version 68 on Windows 7 64 bit and it did seem to work converting m2ts to mpeg2, I only converted a minute of video/audio.

I couldn't get a conversion however anything to mp4, it may not be Avanti's fault however, it stop conversion and says something codec is experimental but experimental codecs are not enabled...something to that regard.

I haven't tried it on Vista, that was where I couldn't get the version back in June to work...I think that was this 68 but not sure hence I stepped back to 66.
No matter, we can try out new version whenever you get it done, no hurry.

[Chris K]

Chris, I believe the change that caused the problem on Windows 7 and Vista was between 67 and 68 if this thread is any indication.

I'v checked it out. It was between 066 and 067. I then rearrange the order of the startup procedure. I think I can revert it for the next version. For XP it doesn't do any harm but there's no guarantee that it will fix all of the Windows 7 problems.

[bromberg]

Many thanks to all who have replied to my install question but even after trying earlier Avanti versions I still get the frustrating 'permissions' error as I described earlier.

Now it's time to move on to new frustrations so whoever is in charge, feel free to close the issue.

Thanks once again,
Dan

[Chris K]

Now it's time to move on to new frustrations so whoever is in charge, feel free to close the issue.

OK! Just a last note that might be useful to other users with problems too.

Don't install Avanti in a very deep file path. The total path length including the filename should not exceed about 256 characters. Why not for a first try put it in "Program Files/avanti_gui_069" or something. Then if it works you can always move it to somewhere else and see what it does. If it fails already there, just play around a bit with the folder name like e.g. "Program Files/avanti_069". Or make it a bit longer. I know it's weird, but that's how it is.

Avanti isn't stable on Vista and Windows 7 and also not advertised that way. Those who get it running without issues on these OS are simply lucky.

Chris

[ricardouk]

Thank you for the new version Chris.
Haven't tried it yet but thanks for the subtitles "enhancements"

[Chris K]

Thank you for the new version Chris.
Haven't tried it yet but thanks for the subtitles "enhancements"

You're welcome!

There's a demo preset included for animated subs. You probably have to change the font size a bit because it depends on the destination frame size. And I had to use a standard font that is available on all OS'. It shows the use of ASS tags. There's a link in the Avanti help file to a description of all available tags.

Avanti isn't stable on Vista and Windows 7 and also not advertised that way. Those who get it running without issues on these OS are simply lucky.

I have good hope the problem is fixed or at least that stability is much improved. There was a memory leak in one of the dll's that never showed up on XP (and still doesn't).

Chris

[Paradox64]

Is there a way to batch process Avanti project files (.apj)? Or a way to run avanti-gui.exe with a switch so I can make my own batch file? I'd like to be able to set up several vieos files, save project files for each, then run them all when I'm not on my computer.

[Chris K]

Is there a way to batch process Avanti project files (.apj)? Or a way to run avanti-gui.exe with a switch so I can make my own batch file? I'd like to be able to set up several vieos files, save project files for each, then run them all when I'm not on my computer.

Hi,

Saved project files contain absolute source and destination paths so will not allow to batch process arbitrary source files but you can make modified copies of templates and switch to them at the "Job Control Manager".

There are also command line switches that perhaps can be of help.

  -s1     "Source_1_file_path"
  -s2     "Source_2_file_path" (optional)
  -dest   "Destination_dir_path"
  -dest+  "Destination_dir_path" (create if not exists)
  -tpl    "template_name"  (optional)
  -autostart (optional)
  -autoexit (optional)

You can find some more details in the chm help at index "Launch Avanti with command line args" (very last item in the index).

[PowerFalcon]

I've recently begun to get an Error message that Avanti seems to have limited Disk I/O permissions, I never change anything since it's last use which worked perfectly ?

[Chris K]

I've recently begun to get an Error message that Avanti seems to have limited Disk I/O permissions, I never change anything since it's last use which worked perfectly ?

Your profile says you're on Windows XP. Avanti should be stable there but this message is triggered on a simple test if Avanti is able to read the "codecs.dat" file at the "avsystem" folder. Please check if this file is still there.

If not, you can restore the "codecs.000" and "formats.000" files from the install package to the "avsystem" folder. You can also delete the "AVANTI.ini" file to restore the default settings.

[PowerFalcon]

I've recently begun to get an Error message that Avanti seems to have limited Disk I/O permissions, I never change anything since it's last use which worked perfectly ?

Your profile says you're on Windows XP. Avanti should be stable there but this message is triggered on a simple test if Avanti is able to read the "codecs.dat" file at the "avsystem" folder. Please check if this file is still there.

If not, you can restore the "codecs.000" and "formats.000" files from the install package to the "avsystem" folder. You can also delete the "AVANTI.ini" file to restore the default settings.

A simple, re-install solve the problem. I need to update my OS, I'm on Windows8.

[Paradox64]

Is there a way to batch process Avanti project files (.apj)? Or a way to run avanti-gui.exe with a switch so I can make my own batch file? I'd like to be able to set up several vieos files, save project files for each, then run them all when I'm not on my computer.

Hi,

Saved project files contain absolute source and destination paths so will not allow to batch process arbitrary source files but you can make modified copies of templates and switch to them at the "Job Control Manager".

There are also command line switches that perhaps can be of help.

  -s1     "Source_1_file_path"
  -s2     "Source_2_file_path" (optional)
  -dest   "Destination_dir_path"
  -dest+  "Destination_dir_path" (create if not exists)
  -tpl    "template_name"  (optional)
  -autostart (optional)
  -autoexit (optional)

You can find some more details in the chm help at index "Launch Avanti with command line args" (very last item in the index).

Seems to me that, if Avanti allows you to save a project file, it only makes sense they would also allow you to load it as part os a command-line option. Otherwise the project files really serve no purpose at all. I understand youe "workaround" but that's a lot of work for something that should be very simple.

I found that the program TEncoder does everything Avanti does and much more, including saving jobs to batch files so my original question is mute. Avanti is hereby uninstalled.