AVSGenie v0.2 GUI

[neily]

For those that are interested, I have put up an update to AVSGenie, significant enough I think to call it v0.2.

AVSGenie Homepage (http://www.neily.demon.co.uk)

No change to the basic functionality (or lack of it depending on your point of view). But the main window has been reworked. Now the preferred interface has all the elements arranged vertically. This is because the multiple line tabs have gone forever. Various elements of the interface can be hidden, there is an MRU list, and the visible tabs are also configurable.

I really don't think I can rework the main window much more. I will see if I can tidy up the video window. I am keen to try to keep seperate source and target controls, and to keep seperate trackbars and buttons, so I'm not sure what I can do. Though AVISource and mpeg2source always seem to work very well, the buttons seem to work much better with DirectShow sources. I thought about having a single centrally located trackbar and buttons, switchable between source and target, but don't know whether this would reduce functionality, and make visual comparisons between source and target more difficult. And I have never been a great believer in having to remember shortcuts. If I could remember all the avisynth filters and parameters, I wouldn't have needed the program in the first place.

Then after that I'll see what I can do making the target tracking more sophisticated, and about parsing in scripts, though it will probably only work effectively for scripts written with the program.

Once again, any feedback would be appreciated, and any bug reports too. Despite checking that everything works OK time and time again, I still come across little things. With so many filters and parameters, and so many elements in the program to each, I suppose it is inevitable.

PS If installing over an old version, I'd delete the old .ini file as well. The new one generated when the program is run has better defaults, slightly different entries, and improved legibility.

[sh0dan]

It looks absolutely fanctastic! Great work.

I do have two problems:

I can't get AviSource to work. It doesn't show up in the box below, AviSynth complains (the scripts return value was not a clip), and I get a "VideoSource Path not found" messagebox.

The other problem is, that I use comma as a float point seperator, so my internation settings is set to use "," anstead of "." in float values. AVSGenie seems to use this value in the boxes, and therefore, if I use Blur for instance it writes "Blur(1,000)" instead of "Blur(1.000)".

[neily]

shOdan

My apologies about the AVISource bug I introduced. I have fixed this. I hope not too many people downloaded v2b1.

I have to say that I had not considered people using , as the FP separator. As it's you, I will try to fix this too.

[LigH]

What, you only change it because it was sh0dan who was complaining?! :p Probably, I misunderstood the subtle parts of the english language here! :D

Well, if a programming language (in this case, "AviSynth-Script") always uses the English number format, and you want to "remote control" it (here, by creating a script), you shall not use Locals-dependent numeric conversion functions; many people other than English/American citizens will have problems if you do so (e.g. in most continental European countries). As a Delphi programmer, living in Germany, I know these problems as well - either using 'Format()' or 'Str()'.