New version of AVS Proxy GUI (2009-07-22)

[LoRd_MuldeR]

Here is a new version of my GUI for the Avidemux (http://forum.doom9.org/showthread.php?t=126164) Avisynth Proxy:

http://img5.imageshack.us/img5/4038/avsproxygui.png (http://img5.imageshack.us/img5/4038/avsproxygui.png)

Download including sources:
http://www.mediafire.com/file/2kmzaymmkmm/avsproxy_gui.2010-04-19.zip

Install instructions:

Please make sure that Avisynth 2.5 (http://sourceforge.net/project/showfiles.php?group_id=57023&package_id=72557) is properly installed on your system, before you try to use AVS Proxy. Then simply put the "avsproxy_gui.exe" into your Avidemux install folder - that's where "avidemux2_qt4.exe" and/or "avidemux2_gtk.exe" are located. The path depends on the Avidemux install location you have chosen!

Also make sure that FFMS2.dll (http://forum.doom9.org/showthread.php?t=127037) (FFmpegSource2, Beta-10 or later), AVSS.dll (http://haali.cs.msu.ru/mkv/) (DirectShowSource2), DGDecode.dll (http://neuron2.net/dgmpgdec/dgmpgdec.html) (DGIndex) and DGAVCDecode.dll (http://neuron2.net/dgavcdec/dgavcdec.html) (DGAVCIndex) all are located in your Avisynth "Plugins" folder (not Avidemux "Plugins" folder !!!). Usually the Avisynth plugins folder is located at "C:\Program Files\Avisynth\Plugins", but it depends on the Avisynth install location you have chosen. If you don't install all the recommended Plugin DLLs, then AVS Proxy GUI will still run, but certain features (source filters) will not work and throw an error message instead! So I highly recommend to install all of the plugins mentioned...

One remark about Haali Media Splitter and obtaining the DirectShowSource2 plugin: You need to install the "Haali Media Splitter" first. Then you can find the required file AVSS.dll in the "Haali" install directory. So you can simply copy it over to the Avisynth Plugins folder. More experienced users may also use 7-Zip (or Universal Extractor) to extract the AVSS.dll.new directly from the Haali Media Splitter installer executable and rename it to AVSS.dll (this avoids installation of the Haali Splitter, if you don't need it). However be aware that FFmpegSource2 requires Haali's Splitter too, so I recommend installing it!


Usage instructions:

The AVS Proxy GUI was designed to allow everybody to easily use Avisynth-input with Avidemux, especially people who aren't familiar with Avisynth yet. Therefor the GUI does not require the user to learn the Avisynth scripting language. The GUI will automatically generate a simple script, call the required source filter and load your input media file. Note that there is one Tab for each source filter supported by the GUI (FFVideoSource, DShowSource, AVISource and DG[AVC]Index).

Most of the time you will be happy using "FFVideoSource" (FFmpegSource2). It's 100% self-contained and hence doesn't require any additional decoders to be installed on your system (except for Haali's Splitter). Furthermore it supports a wide range of input formats (AVI, MKV, MP4, FLV, WMV, OGM, VOB, MPG, M2TS and TS). In case FFVideoSource fails, you may try "DirectShowSource" (or Haali's DSS2) as your fallback solution. But be aware that DirectShowSource relies on suitable DirectShow decoders and splitters to decode the input file (such as ffdshow and Haali Media Splitter).

For AVI files you may also use "AVISource", but suitable VFW (Video for Windows) decoders must be installed on your system! Most of the time decoding AVI files through FFVideoSource will work just fine and is easier to use than AVISource. For MPEG-2 and VOB files "DGIndex" (DGDecode) is the preferred source filter. And for AVC/H.264 streams "DGAVCIndex" (DGAVCDecode) is the preferred source filter. Note that DGDecode and DGAVCDecode need Index files as input! These Index files (.d2v/.dga) are created by using the DGIndex or DGAVCIndex programs. These are separate applications.

Advanced users may use the "Custom" tab to load or write their own custom Avisynth script. But be aware that the GUI will not check your custom script at all! If you encounter any scripting problems, refer to the Avisynth Wiki!


Feedback is welcome :)

[LoRd_MuldeR]

Same small updates: Added DGIndex/DGAVCIndex support and some code clean-up :)

[buzzqw]

thanks LoRd_MuldeR!

your proxy is much better then old dos proxy..

BHH

[LoRd_MuldeR]

thanks LoRd_MuldeR!

your proxy is much better then old dos proxy..

BHH

The AVS Proxy still is a CLI application (not DOS), my application is simply a front-end...

[LoRd_MuldeR]

Just uploaded another update: Multiple instances are now handled :)

[LoRd_MuldeR]

Now with built-in avsproxy.exe, improved error handling and a few fixes. Hope this is the last update for today ;)

(Download link in first post updated)


<- Sorry for triple posting :o

[buzzqw]

yea, working.. even if you drop avsproxy in a temporary folder ... :p

thanks!

BHH

[flywitness]

My avsproxy_gui always fails when trying to open avidemux:

"Avidemux could not be found in current directory."

Where is it looking exactly, and exactly what file name is it looking for? I would like to fix this.

[poisondeathray]

flywitness - if you install avidemux with the "full install" it includes the avsproxygui in the proper directory

[LoRd_MuldeR]

My avsproxy_gui always fails when trying to open avidemux:

"Avidemux could not be found in current directory."

Where is it looking exactly, and exactly what file name is it looking for? I would like to fix this.

It is looking for "avidemux2_gtk.exe" in the same directory where the "avsproxy_gui.exe" is located:

if not FileExists(BaseDir + 'avidemux2_gtk.exe') then begin
Application.MessageBox('Avidemux could not be found in current directory!','AVS Proxy', MB_ICONERROR or MB_TOPMOST);
end;

[flywitness]

I have avsproxy.exe, avsproxy_gui.exe and avidemux2_gtk.exe (shortcut) in C:\WINDOWS\system32.

The error persists.

[flywitness]

To answer my own question, it looks like it needs the actual exe program file - not a shortcut. The tidiest solution to this problem I think is to put avsproxy.exe and avsproxy_gui.exe in your avidemux directory.

[LoRd_MuldeR]

To answer my own question, it looks like it needs the actual exe program file - not a shortcut.

Shortcut won't work for obvious reasons :rolleyes:

The tidiest solution to this problem I think is to put avsproxy.exe and avsproxy_gui.exe in your avidemux directory.

That's how I intended it to use from the very beginning...

[flywitness]

Thankyou Lord :)

[LoRd_MuldeR]

Just uploaded a new version :cool:

Changes:
* Run the Qt version of Avidemux, if installed. Otherwise fall back to the GTK+ version.
* Added support for FFmpegSource version 2.00, you will need to install FFmpegSource2 (FFMS2.dll) (http://forum.doom9.org/showthread.php?t=127037) now.
* Added support for DirectShowSource2 (DSS2) by Haali, requires "avss.dll" from Haali Media Splitter (http://haali.cs.msu.ru/mkv/) download.
* Added the "Web Links" page, which contains some useful hyperlinks.

[LoRd_MuldeR]

Here's another update :cool:

Changes:
* Make "Custom Script" a fully-fledged script editor, not just an .avs file selector
* Fixed a few minor bugs

[DocMAX]

any way to run multiple instances? i need this feature very bad... =(

[LoRd_MuldeR]

any way to run multiple instances? i need this feature very bad... =(

Sorry, it's not possible. And that's not a limitation in my AVS Proxy GUI. The AVS Proxy GUI prevents the user from running multiple instances for a good reason: The underlying AVS Proxy (derivated from avs2yuv by Loren Merritt) cannot run several instances! It tries to bind network port 9999. If you create a second instance, it will fail to bind that port (because the port is already bound by the first instance) and exit with error. And even if I could assign different ports to each instance of AVS Proxy, then Avidemux would still try to connect to the Proxy only at port 9999...

[jameskerry]

thanks LoRd_MuldeR! for sharing new proxy with us..your given proxy is very useful for me...
:thanks:Thanks again

[LoRd_MuldeR]

Updated the download link in the first post with a less outdated version ;)