avsFilmCutter Ver 2.0 b Video Editing tool for AviSynth

[Ebobtron]

avsFilmCutter version 0.0.2.0 beta, version date 27 July 2007

avsFilmCutter is an AviSynth script editor with a built in viewer / player some of the included features are:

filter function documentation lookup
filter function parameter dialog, parameter look-up direct from AviSynth
Syntax Highlighting
One button/click script check with AviSynth error reporting (very much improved thanks to IanB)



Main page (http://avsfilmcutter.com)
More information some screen shots (http://avsfilmcutter.com/filmcutter.html)

The guides are being rewritten
Using the Script Editor (http://avsfilmcutter.com/fcwebguide1.html)
Using the Video Scene Editor (http://avsfilmcutter.com/fcwebguide2.html)
Using V.C. Mohan's TransAll plug-in (http://avsfilmcutter.com/fcwebguideTALL.html)
Using the Encoding application interface (http://avsfilmcutter.com/fcwebguideEncod.html)




Get avsFilmCutter version 0.0.2.0 beta:
http://www.avsfilmcutter.com


For trouble with viewing YV12 try a different decompressor or maybe you need one.
www.xvid.org You can install xvid on your computer.
The Xvid encoding package has a good YV12 vfw (video for windows) decoder. Just download and install the package.

http://forum.doom9.org/showthread.php?s=&threadid=56972
Helix YV12 / I420 VFW Codecs

The beta designation has remained to warn the user that the program is under heavy devolopment, very heavy. I try to release stuff that works. Everything is subject to change however. Therefore save your last version, you may like it better.

avsFilmCutter is free. Freeware, free software, I'll let the experts decide.

[Ebobtron]

Changes in version 0.0.2.0 beta - 27 July 2007

New:

For the video editor, two new items in the row button menu, Jump to Start Frame and Jump to End Frame. Another great idea from a user, thanks towtruck, aka Andy
Clip preview / edit dialog allows you to trim or extend the clips frames in a seperate pop up window, more from Andy.
In the main window menu you will find "Compression dialog" this will show the same video and audio codexs installed on your computer. The ability to save an *.avi should come soon.
avsFilmCutter released under an OpenSource license.

Fixes:

Huge bug in my method of reducing memory leaks when using AviSynth API. Some users would experience sudden program termination when switching to a viewer. Fizick, IanB

Script syntax or AviSynth error should prevent loading the video display. Error text displayed in Test box, last error retained see AviSynth Options | Display AviSynth Version

Loading Script with an error directly using media viewer terminated FilmCutter after reporting error.

When using the function lookup in AviSynth documentation feature with the path to the documentation incorrect, the SafeString update and pointer audits broke this. Only a new user or new installations would ever see this. If you did see it you had trouble. List of outcomes is very long.

Found the cause of encoder dialog window title haveing the encoder path almost off the page.

FilmCutter has had a string white space stripping ghost for sometime. Exercised one in the function parameter parser in mydlg.h

Encoding interface code had a few unintentional message boxes, sorry.

For those that edit using projects, if you had occasion to use the tabs on the editor they should work ASAP instead of waiting for the mouse to move.

Alpha video window poped a message box when closed

An illegal resourse assignment has been fixed 98 & ME and nt4 users, sorry I didn't know, rejoyce.(IanB)

Another issue with dynamic memory allocation resolved in the video interface.(IanB)

FilmCutter would choke on a corrupted ini file and loop endlessly.

Dialog bug in alpha 1 options dialog help button opens lots of help windows. Wow!

Ever wonder what your screen saver keeps coming back. You turn it off, it comes back. Oops, FilmCutter can disable screen saver and power saver settins but always restores them. If now checks the states and preserves your system settings.

Play was activate-able without a loaded video.

Script writing options dialog proc had some window errors.

Video scene editors time display could become inaccurate. Or sink the ship.

Found another divide by zero (they still crash). Syntax error could cause framerate to be zero. Total time amd scene time function go poof.

Changes:

More pointers to buffers corralled up so the memory associated can be reused or Released.

Moved many local variable definition statements out of conditional branches in WinMain with much care taken to make sure that memory allocated is reused not recreated.

FilmCutter would warn the user about needing SciLexer.dll and then go on to crash. FilmCutter now warns the user then terminate gracefully.

If the video viewer was in play mode when the user exited FilmCutter the system values for the following items remained false. Oops!
SETSCREENSAVEACTIVE
SETPOWEROFFACTIVE
FilmCutter how issues a play stop command before exit, which changes the values to true.

If you change the file filtering in the file saves / open dialogs FilmCutter remembers your last file type, i.e. *.txt, *.avs. Believe it or not that is not automatic.

While bug hunting the parameter help dialog I added code to prevent parameter strings from exceeding 260 characters (max path length).

Some very old code died today, the checkstate of a hidden button is kind of unreliable. Because, you can not check it till it changes and windows will change it when it wants to.

Changed the way preview with script editor updates. If, when the user press F4 or clicks the update button, an error occurs the error (likely syntax) will display and the update will not be done. Current frame and state shall remain.

Small changes to the source / project switching. Scene list remains active but the row buttons become disabled when project radio button is selected.

Finally remembered to put the max and restore things on the main menu list so you can maximize the window while using the video scene editor without having to be all tricky back though the script editor menu.

Rearranged the scene editor view / mode. Added a scene preview button, added the third window to "mutli-frame editor". Big rewrite to the video veiw code, also changed trackbar style to move frame# tool-tip to above frame slider.

Changed the way the source / project radio buttons work. FilmCutter will prompt you if it needs the project data saved.

The AviSynth interface has been completely rewritten. Along with his help to resolve a nasty crash issue I introduced, Ian Brabham's generous code contribution to FilmCutter gives it vastly improved error handling capabilities. Ian added three Safe AviSynth functions that simplify and standardize error trapping and reporting. See "AviSynth Error Reporting" in the user's guide.

The "filmcutter.ini" file write routine has been completly rewritten. A little faster I hope, much simpler.

Added the code needed for the save wave function to be able to read wave format WaveFormatExtensible when the format is used in AviSynth.

[dr.Prozac]

Seems nobody is interested so I decided to write something.
I really appreciate your effort. I appreciate you want to share your application for free. Doesn't matter if it works perfectly or it doesn't. This is just the beginning and I can see you have many new and great features to create in the future.
I was just testing your soft. In my opinion you did a very good job. Just think also about more comfortable gui so that every, even less advanced users will be able to use it intuitivly. Also, when it is the first run, many various windows, confirmations ect. appear. is it neccesary ? Next thing, every user is able to run AVSEdit even if this tool is not installed in the system. So, then we can see the Message (Create process failed).
These are the things I have noticed for the time being. Of course don't think it was my purpose to find fault your work. No. Programming is also one of my interests and I also develope my own free application writen in Delphi. I just know that it's quite difficult to find every bug and to judge your own program. Nothing is more helpful than users opinions :)

good luck!
Prozac

[Ebobtron]

@dr.Prozac

Thanks for the kind words and for showing an interrest.
Just think also about more comfortable gui so that every, even less advanced users will be able to use it intuitivly.I noted in the original “know issues” list that the trim edit view had problems. However, I did not see how horrid it was to anyone but me till after I had it out. Version 0.2b is better. I hope more feedback will lead to a better working layout.
Also, when it is the first run, many various windows, confirmations ect. appear. is it neccesary?I also warned about stray popup message boxes. I left those in the program for the first release because I would know where the program was crashing if FilmCutter did not startup on some systems. In addition, I wanted the user to know that the program was going to write to his hard-drive. Not very elegant but it works and they are temporary. Moreover, there are a few I have forgotten about so let me know please.Next thing, every user is able to run AVSEdit even if this tool is not installed in the system. So, then we can see the Message (Create process failed).I left the Launch AVSEdit feature in the script edit menu because I wanted feedback on whether anyone would like it. I am sorry that for those without AVSEdit that it is not included. Version 0.3b will add a tool bar of six user-defined buttons so you can add or change to suit your needs
Nothing is more helpful than users opinions :)Absolutely, much of the programs structure depends on the features so feedback from users will definitely define the program in the future.

There are many ideas yet to implement and I have held back to see if it will run on other systems. I would like to know if the program runs on 98, ME, Win2K and other configurations than just mine before I continue with the project.

Again, thank you for the feedback. I hope you can find use for the program

[Ebobtron]

Some people say, no news is good news. Others remind that if you cannot say something nice, say nothing at all.

I wonder which applies here.

For all of you who have looked the program over and are still shaking your heads, I am sorry. I also would like to thank anyone who has tried the program. This version should provide enough features that a person could do something with it.

Version 0.4b is a fix for 0.3b.

Version 0.0.0.4b is up on the website.
http://members.aol.com/avsfilmcutter/

Going to California to visit the Mouse, August 7 thought the 13th. If you post a comment to the forum or email. You will not get a response during that time, I will be with my granddaughter.

Don't really think it will be a problem.

Changes in version 0.0.0.3b 7/30/2005


filmcutter.ini is not compatable between versions 0.2b & 0.3b/0.4b. Please delete filmcutter.ini or place version 0.4b in a new folder.

Select/Add encoder now handles cancel from the add encoder dialog
properly(will not add a NULL encoder) no more NULL encoders.

"Script Write" now has a dialog box allowing selection of Aligned or
UnAligned Splice.

Script edit view has a six button tool bar on the right. Button six is shared
with trim edit view and is meant for your external viewer.

Quick internal preview of unsaved script available thought menu or F5.
External viewer will also display unsaved script when launched from script editor.
Pressing F5 will play the current viewed script.

Script editor and viewer windows both track the source/project checkbox.


Thanks
Ebob

[Ebobtron]

Adding F5 shortcut key to the script editor window resulted in the 't' key being ignored by my message loop.

Cannot tell you why. Did a quick rewrite and now the F6 button play/stops the video and the F5 key works as well.

Other little fixes too, look at the change log in the downloaded file.

[nnigam]

It appears to be a very useful tool. I tried it today. Under NT 4.0 the buttons are missing their text, and the video does not go into preview. Althouugh vdubmod opens it just fine. I will try tonight at home where I have XP sp2 and see how it goes.

Thanks for making the effort to write a useful product.

[Ebobtron]

@ nnigam
Thanks for the bug report and the kind words.

“Under NT 4.0 the buttons are missing their text”
Can I assume that the buttons you are talking about are the “encode“, “write script“, “delete” and “insert” buttons used in the trim edit view?. If that is indeed the case, the “Ok” and “Cancel” buttons in the dialog boxes should be blank as well. For the sake of others that may read this, all other buttons are iconic and most all start out blank.

The blank buttons should be the six tool buttons to the right of the script edit window in the script edit view. The preview window has no buttons at this time. The trim edit view sports eight iconic buttons beneath the video viewer window, two are always blank in this version. To the left of the frame window the checkbox should be grayed out to start and the label should be “Source”. Above the checkbox the button will start out blank, this button is shared with the script editor and is iconic. Continuing to the left is “insert” and “delete”. In the top left corner is a static iconic window that displays the icon of the selected external encoder. Right of the corner is two buttons, which should be labeled “encode”, and “write script”.

There is a reference in the “Microsoft Platform SDK February 2003” documentation, which follows.
If you specify Microsoft Windows® version 4.x or later when linking your application, its windows cannot have caption buttons unless they also have window menus. This is not a requirement if you specify Windows version 3.x when linking your application.

Well my windows do not have menus so maybe that is it. However, the note shown above is vague at best.
"and the video does not go into preview".
This is a little more bothersome and prompts the following questions.

Did you receive a MCI error popup message box?
Did the status bar show the correct file name for your script?

[nnigam]

No need to bang your head. NT 4 is outdated now, and we should be upgrading to XP in the next month or so. I got busy with a couple of tasks this weekend, and so completely forgot to test under XP pro sp2 and media center at home, but will test and let you know.

As for the buttons, I get a window with no menus, and six buttons on the right which when clicked open a lauch tool dialog with the message untitled, and an ok button which closes the diallog box.

Right clicking, I can open an avs file. Then from rightclicking for preview, I am unable to get the file to play back. However, If I hit f5, then I do get the preview.

When my avs file is in the editor window, All buttons are still blank. When I press f5 for the preview all the buttons are gone.

In the trim/Edit window, only the encode, write script, delete, insert, play and 4 movement buttons are visible. There are 3 other buttons that do not have anything in them.

Let me play around it with some more and then I will be able to give a better idea. I tried to paste the image here, but somehow am unable to.

[danpos]

@Ebobtron

Is your website down? :(

Cheers,

[Ebobtron]

@Ebobtron

Is your website down? :(

Cheers,
It has not been down; tracking has been reporting hits all week though 12 August. Please try again if you already have not.

[Ebobtron]

@ nnigam

No need to bang your head. NT 4 is outdated now, and we should be upgrading to XP in the next month or so. I got busy with a couple of tasks this weekend, and so completely forgot to test under XP Pro SP2 and media center at home, but will test and let you know.I would generally agree with that. It would be nice to know if there are issues unique to NT 4.xx or any version for that matter.

As for the buttons, I get a window with no menus, and six buttons on the right which when clicked open a lauch tool dialog with the message untitled, and an ok button which closes the dialog box.That message box is a stray used to debug the program, sorry. Open an existing script or save one and the box will display the file name. Right click the button and you will get a dialog box for that button allowing you to select which external program you would like to launch with that button. Once an external tool has been selected for a button the icon for that tool will show in the button. Clicking that button will launch the tool which should open the saved file( not the viewed data ) after clicking OK in the message box showing the file name. Oops. Next version will trap the modified flag and ask the user if they would like to save the viewed data before launching the tool. F5 will play the viewed data and tool button six will not ask but send the viewed data in the script edit window to your external viewer or whatever program you desire.

Right clicking, I can open an avs file. Then from rightclicking for preview, I am unable to get the file to play back. However, if I hit F5, then I do get the preview.This is my fault. The three view choices are not clearly described in the menu as view choices and will be addressed in ver 0.5 of the program. At this time the script loading into the veiwer is sort of up in the air due to the video viewer’s ability to crash the program if the script crashes AviSynth. Untill I come up with a way to prevent the crash or trap the crash and report it so that the user has some warning that the script is the problem, this is going to be a little confussing.

When my avs file is in the editor window, All buttons are still blank. When I press F5 for the preview all the buttons are gone.Yup that is what is going to happen. The program changes views to do this. Press F5 again to return to the editor or F6 to stop and start play.

In the trim/Edit window, only the encode, write script, delete, insert, play and 4 movement buttons are visible. There are 3 other buttons that do not have anything in them.Yes, that is correct. The button above the check box is a repeat of button six from the edit view. Meant for your external video-viewer choice, the button should display the icon of the external viewer once it has been configured. The other two buttons do nothing but latch down or up in the current version and will be programmed as scan forword and scan reverse in a furture version of the program. The far right button which sends the frame numbers to the list windows should display filmcutter’s icon.

Let me play around it with some more and then I will be able to give a better idea. I tried to paste the image here, but somehow am unable to. Hope the above info helps you, help me. For which I am very grateful.
Images posted to the forum must be reviewed by the forum before they can be viewed, it can take a day or so.

Once again, thank you, for your time and interest in the program, any info positive or negative is helpful. It is very easy as the programmer to have tunnel vision and miss how misleading a few poorly chosen words can be.

[Nic]

ebobtron: Would you consider making it opensource? Wouldn't mind adding some bits. Been wanting to write something similar for ages, but as dragongodz points out, I can't start another project I won't finish... ;)

-Nic

EDIT:
ps
On windows2000 I have the same problem as is reported on NT4. Strange. I could fix it if only the source was available..... ;) lol

[Ebobtron]

@Nic
I‘d love some help.

As far as open source, she is nowhere near ready for that; nor do I think my ego is either.

Version 0.5b is underway let me finish that and do some cleanup, I‘ll send you details on the source when 0.5 is done. I think I can put all that together in about two weeks, currently resting from my vacation.

As far as the issues with NT 4.x and Win2000.

Nnigam’s last post suggests that he can see the text in the buttons that have text.

I think my menu structure is so poorly written that intuitive is the last thing it might be called. My wife clams that communication is not one of my skills. If you select the “Preview” window view from the script editor the script will not automatically load, which at this time is by design. If you load a script from file or save the script you are working on the “Trim Edit” window will load the video and because I use the same instance of the video viewer for both “Trim Edit” and “Preview” the video will already be loaded. Furthermore, if you load a script while in one of the views with a video window, the script will load.

F5 or view script (see how dumb my labels are, sounds like script view) saves the text in the script editor window and then loads the saved file “preview.avs” into the viewer and again it uses the same video viewer and view as “Preview“. Just switching views will not load the script. So I added the shortcut.

As for the rest, the program has no title or menu bar. I am shooting for menus that apply to the task and so they are right under my finger.

If there is more than I have been able to gleam from nnigam’s posts please elaborate.
The program is cookie dough and we can make it what we what it to be.

Version 0.5b should contain the following enhancements.

Cleaned up menus, which should make more sense.
Editable tool button dialogs and a button click will prompt the user to set the button up if it has not been configured to launch a tool.
Prompt the user to save the script before launching the tool from a tool button.
Program will test the script output before loading to detect script errors and resize the video window to make error reports from AviSynth easier to read.
Crash detection for really bad scripts.
Script properties display.

I want to get working on the parts of the program that made me start this thing.

So if you have time to help I would be honored and I have many questions.
If you do not OK. Your software has been a great aid to me. You showing an interest in FilmCutter has made my day.

Thanks Nic

[Nic]

Good luck with it :) I'll keep an eye on the thread to see how you progress.

Don't be afraid of releasing source code early...can help progress bits your having trouble with by someone else doing them. Your code can't be any worse than DVD2AVI when it comes to manipulation. Neuron2 must be going mad dealing with that mess on a regular basis.

-Nic

[danpos]

@Ebobtron

I wanna try your app but I don't get a successful download from your website (and the guilty is my crap ISP ...http://www.geocities.com/pcdanpos/smilies/furious3.gif http://www.geocities.com/pcdanpos/smilies/thumbsdown.gif). Could you host it in another place as rapidshare.de for instance? Forgive me for any inconvenience! http://www.geocities.com/pcdanpos/smilies/worried.gif

TIA,

[Ebobtron]

@danpos

Ok, here is the link.

http://rapidshare.de/files/3992969/FilmCutterVer0004beta.zip.html

[danpos]

@ebobtron

Thank so much for your attention and support, mate!! http://www.geocities.com/pcdanpos/smilies/klanjamse.gif

http://www.geocities.com/pcdanpos/smilies/cheers.gif

[Ebobtron]

Mostly a bug release.

http://members.aol.com/avsfilmcutter/
Finally got the trim edit view closer to where I what it. I have renamed it to video edit view.

For the next version, I am working on color space detection, audio stream info and a draft mode for the video editor view to speed up (maybe) preview.

As for future feature additions. Anyone have a preference?
Batch encoding or an input Wizard. Or something else perhaps?

[Ebobtron]

Mostly a bug release.

http://members.aol.com/avsfilmcutter/

Select New Project did not reset the check box or all the source/project flags.

You may delete an encoder from filmcutter's encoder list.

Script output properties now displays the audio sample rate and the color space output by AviSynth. It displays "YUY2", "YV12", and "DIB ". DIB shows up for either RGB32 or RGB24 (guess I will have to dig deeper). Soon you will be able to tell FilmCutter which color space your external encoder expects to see.

In addition, I think my idea about a draft mode preview may be very lame.

Thanks again for looking in,
Ebobtron

[Ebobtron]

Version 0.9 beta has a reworked status bar. You can save your project output scripts without messing up the current project. The encoder application dialog box has been reworked to allow color-space testing before launching the encoder. Max number of unique encoder configurations increased from nine to 99. I have also enabled very basic avi viewing (note the retro file open dialog box with preview). See the change log at the top of this thread.

http://members.aol.com/avsfilmcutter

http://rapidshare.de/files/6795203/FilmCutterVer0009beta.zip.html

[Ebobtron]

Hello all,

Version 0.0.1.0 beta is up and ready for download.

More work done to the encoder dialog box to fix and improve.

Added tab control to the script editor. When a project is open the user can switch between source and project scripts in the editor window by clicking on a tab. see the change log (http://forum.doom9.org/showthread.php?p=688196#post688196) in this thread.


http://members.aol.com/avsfilmcutter
or
http://rapidshare.de/files/7103415/FilmCutterVer0010beta.zip.html

Wish everyone has a happy and safe holiday season.
ebobtron :thanks:

[Fizick]

Ebobtron,
May you consider to implement in AVS script editor:
1. select avisynth function from menu list:
2. select parameters for selected fuction from list

see here:

http://forum.doom9.org/showthread.php?p=729114#post729114

[Ebobtron]

Hi Fizick,

You have given me an early Christmas present, thank you. I have always considered such a feature far too difficult to maintain.

I have been thinking about an implementation of the TransAll plugin for FilmCutter’s scene editor. If the plugin is in the directory, the feature is available.

This certainly changes my thinking.

There is one problem though; you people are about eleven years ahead of me. I could use a little help in catching up. I have no clue how to read data from the dll.

Can someone volunteer to catch me up?

Update:
As of 11/10/05 I know how to access avisynth.dll to obtain filter lists and the like.
Ebobtron,
May you consider to implement in AVS script editor:
1. select avisynth function from menu list:
2. select parameters for selected fuction from list

see here:

http://forum.doom9.org/showthread.php?p=729114#post729114
Thanks again,
Ebobtron

[Ebobtron]

@Fizick

Your alt left and right keys jump (fps * 2).

FilmCutter's jump buttons jump by default 300 had planned to assign up-arrow jump reverse and down-arrow jump forward, what would you think alt up and down arrows should be. Should we think in minutes, 1 min and 10 mins respectfully?

Anyone have an idea of useful numbers.

Ebobtron
http://members.aol.com/avsfilmcutter

[Fizick]

Please, try get some VirtualDubMod compatibility with this and other fuctions !
Thanks! :)

[Fizick]

I repost some my (old :)) suggestions here:
0.Fades and dissolves (cross-fades ?) will be very interesting!
1. Can we not close script windows when switch to preview ?(I like use VDMod F5 key for refresh frame preview after changing the script).
2. Full frame size option in editor for detailed preview. And may be option with small quarter-frame size with a few frames for fast but precise navigation - I often check if I exactly put trim to right place or i missed 1 or 2 frames.
I wrote this and understand now, that i want timeline option like Adome Premier or Ulead MediaStudio
3. Also I want scroll forward and backward by 50 frames with keyboard (ALT-arrow keys in VDMod).

[Ebobtron]

HI,

Please, try get some VirtualDubMod compatibility with this and other fuctions !
Thanks!
You make my life too easy VDMod 1.5.10.2 9 (build 2540) does nothing with the up/down arrows.
Thanks, I can do that. ;)
0.Fades and dissolves (cross-fades ?) will be very interesting!I quote the following source. "A gradual fade from one shot to the next is known as a crossfade, mix or dissolve".
http://www.mediacollege.com/video/editing/transition/crossfade.html
FilmCutter uses FadeIn, FadeOut, FadeIO and Dissolve to generate scripts. What do you think cross-fades are? :confused:

As you can see from an above post the alt up and down arrows will advance and reverse frames 2 seconds any framerate. It is coded in "ver 0.0.1.1".

As for the rest, coding an alpha of your item number 1. My thinking is the full size video window is best used with the script editor for filter tuning, or am I wrong. When I am done I will let you all take a peek.

I wrote this and understand now, that i want timeline option like Adome Premier or Ulead MediaStudio :D I am still laughing.

@Fizick
Concerning your post http://forum.doom9.org/showthread.php?p=732432#post732432 I have downloaded VDMod's source and sent PM to shOdan, from the source I can see that in practice env->GetVar() looks like....

avisynth.dll Class object = env->GetVar("$InternalFunctions$"), I need to track down where the data goes.

As for my end of a filter pick list, it is not going to be very hard, I can see most of the code in my head. The params feature is a little tricky but very doable.

Alpha update:
Sorry, but the alpha I promised is a total bust, I just hated it. Looking at other programs for ideas is good and bad, I very much like VDMod's script editor with the F5 feature. Looking through my idealist, I have come up with the following.
Menu select script preview options
auto play
return to same frame
Dual video windows, left (source) and right (edited source), they will not play but will be frame locked together.
Preview window in dual mode will have editable frame number window (go to frame), three-display option buttons (dual, left only, right only) and slide bar, only nav feature disabled will be the play button.
Maybe an Alt+F5 toggle to invoke the dual window mode without using the menu to preselect it.

If that does not help with script development I am not sure what will, once implemented I may consider small script editor window.

Still need to add the undo functions to the editor menus, how many levels of undo do you like.

Later,
Ebobtron
http://members.aol.com/avsfilmcutter

[Ebobtron]

Hi all,

I put an alpha up on the website which demos the filter picking popup idea from Fizick.

http://members.aol.com/avsfilmcutter/fcAlpha.zip

As FilmCutter creates itself it has a little chat with avisynth.dll (http://avisynth.org) and collects the keywords for the external plugins in the external plugins directory.

You may activate the popup window from the script editor menu (right click the editor window) or by the keyboard shift+tab.
When the window is up you may use arrows or mouse to navagate the list, double click or enter to select. Once up, it will stay till you use it though.

When you select the filter you want, it is inserted at the current caret position or it replaces any selected text.

The alpha is 0.0.1.1 a and as far as I know a direct sub for 1.0 b except for the feature described above.

Ebobtron
http://members.aol.com/avsfilmcutter

Nic,
Thank you for being a sounding board and for the good advice.

[Fizick]

Ebobtron,
It works! Thanks. It is nice.
Small comment: I see two MVAnalyse, etc. It is becaurse of i have mvtools0953.dll and mvtools0991.dll in my plugin dir.
To use them prorerly, i must to use function name like mvtools0953_mvanalyse(param).
Forget about it now, but please recall it in some time in future (for stable version).
Right now i wate exited version with plugin parameters selection!
Probably we can select function name in script (not from your list!) by mouse or arrows, press F1 and get some form (table) to fill parameters.
But if fuction exist in scipt with parametes, we can select parameters values too, and fill the form.
But so you must parse this string. it is not easy task. some parameters are named, some are not.
So, probably more simple solution is popup window with all parametes list (with type) for current function, with possibility to press on it and put it to script line. (as you implement for functions names)
What anybody think about it?

[Ebobtron]

Hello all,
If anyone would like to see the progress of FilmCutter's new feature or more importantly like to help. I have uploaded a new alpha at http://members.aol.com/avsfilmcutter/fcAlpha.zip.

With the current release of AviSynth only internals are working, but the good news is that Fizick found the bug. The info concerning the bug and the test build are here: http://forum.doom9.org/showthread.php?p=737974#post737974.

If you want to try the test build you’ll have to modify filmcutter.ini

Make this:
main window
1 156 86 752 526

write script
2 0

button 1
Look like this:
main window
1 156 86 752 526

write script
2 0

ForceEFP
1 change the one to a zero to go back to using the release build of avisynth.dll

button 1

Either way, to invoke the list press shift+tab, select a filter / function and press tab to open the function help dialog box.

The string from AviSynth.dll is shown on the bottom and the data should be parsed out into the boxes above (scroll is working).

The other change between the two alphas is I removed the alternate name filter for the list box (plugin_function name). Now every external plugin function is listed twice "Mpeg2Source and DgIndex_Mpeg2Source" are an example.

There is also a script menu function that will display the filters, internal and external and the parameter strings returned by AviSynth, runs very slow but that is not a bug, it is a very slow function.

If you see a string parsing problem please let me know.

There is a lot more to do, but the overall framework for the api, related to this feature, is about done.

One more thing, FilmCutter is set to limit these features to avisynth versions 2.55 and above. It is the oldest version I have to test with.

Thanks for looking,
EBobtron

[Fizick]

Link is wrong. probably this must work:
http://members.aol.com/avsfilmcutter/fcAlpha.zip

[Ebobtron]

Hello all,

One more alpha before the big offical release. :rolleyes:

http://members.aol.com/avsfilmcutter/fcAlpha.zip

Everything about this "filter/function lookup / help feature" mentioned in a pior post (http://forum.doom9.org/showthread.php?p=739704#post739704) still aplies, except add the following info.

After you have opened the dialog box ( select filter/function in the list then press tab ) please note.
Use the tab button to move forword though the data windows, no shift+tab for reverse navigation yet. The tab button will advance the vertical scroll and jump to the top if you tab past the last data field.
Data windows are now appropriate for the data type.
Only data presets are TRUE and FALSE loaded in the bool list boxes.
There are no defaults, the data windows start out NULL.
For the moment you can not load a scripted function into the dialog box.
You can preview the output string before you insert it into the script.
Clicking Insert closes the window and inserts the entire string into your script whereever your caret was or inplace of any text you may have selected pior to calling the list and dialog box.


Lots of work still to do, but I thought some might like a look see.

Ebobtron
And of course FilmCutters website and webguides are located here: http://members.aol.com/avsfilmcutter

[Fizick]

Thank for your works.
I will try it.
By the way, I replaced test build avisynth.dll by version with number 2.5.7 . Link above.

[Ebobtron]

Hi,

Went to test with avisynth.dll ver 2.57 ala Fizick and caught a buffer use error in FilmCutter, that caused instant program termination.

I have corrected the error and updated the Alpha on the website.
http://members.aol.com/avsfilmcutter/fcAlpha.zip
The error only affected the alphas, when used with versions of avisynth pior to 2.57 with ForceEFP set to 0.

@ Fizick,

Thanks for the new Avisynth build. I was able to test FilmCutter's version trapping and I guess I can remove the ForceEFP functions from the released beta. User's who follow this thread will have the new build away, if they want.

:thanks: Thank you for your work.

Ebobtron

[Ebobtron]

Hi,

Well I did it again, released a little too early, look for 1.2b next week.

Did you know that “Audiodub(clip=v, clip=a)” does not work fortunately d2v = “” works, I didn’t even give it a thought. Someone please slap me. :stupid:

The only thing that will not be obvious is the right click on the data windows in the filter parameter dialog-box. The right click should get you a file name dialog box that will insert the file name into the little window.

Went back a little and downloaded all versions of AviSynth 2.5 and tested each with FilmCutter the results follow.

2.50 no filter name export.
2.51 no filter name export.
2.52 external filter function names attempting param read throws exception or at least it does not crash.
2.53 external filter function names attempting param read crashes.
2.54 external filter function names attempting param read crashes.
2.55 internal and plug-in function name lookup working can read internal function parameters attempting to read plug-in function params causes instant and fatal error. Alternate names for externals added in 2.55.
2.56 same as 2.55.
2.57 all working in Fizick's build.FilmCutter will provide the proper amount of support depending on the version of AviSynth your using, preventing the crashing. Probably a waste of time, but I did find some bugs in my version trapping.

I wish I could say the filter picker and param dialog is 100% stable but I can not say that, testing continues of course.

http://members.aol.com/avsfilmcutter
or
http://rapidshare.de/files/8361518/FilmCutterVer0011beta.zip.html

I am now going to go sulk for a while, get some sleep and try again tomorrow.

[Fizick]

Will try on weekend.

[Ebobtron]

Hello all,
That old last but not least stuff gets old so.......

@Doom9
Thank you for this place where I play and learn.
@all
Thanks you for making this forum such a great place to play and learn.
@Nic
Thanks for your time, when you have none.
@Fizick
Thanks for the great ideas and then coming though with a fix so I can pursue them.

As promised 0.0.1.2 b.
http://members.aol.com/avsfilmcutter
or
http://rapidshare.de/files/8673247/FilmCutterVer0012beta.zip.html

FilmCutter is not crash free yet but the filter / function popup list and parameter dialog should not be so deadly.

I kind of think it is a pain to type a little then mouse a little or try to do both. I have tried to setup FilmCutter so you can keep you hands on the keyboard if you like. Therefore I have made some changes to the filter / function popup list and dialog they include.

Changed “shift+tab” to “ctrl+tab” to display the filter / function list. Seems more comfortable to me.
Once the list is up keep typing, note the far right column of the status bar will display “Filter search = M“ if you type a ‘M’, the list highlight will move to the first ‘M’. don’t worry about case just keep typing, as you get close the filter / function you want will show. Lots faster than arrowing down though the list. Backspace works if you type the wrong character, and alt_names work as well. If the highlight lands on your filter press enter or tab for the dialog box.
Once your in the dialog box pressing “Ctrl+Shift+O” will open a file dialog box for filename selection that will insert into the data cell that your in. Tab navigation still works. Press enter and your done.
You should be able to write the following script without touching the mouse, I can.
vid = MPEG2Source(d2v="E:\your.d2v", iPP=TRUE)
aud = WAVSource("E:\your.wav")
AudioDub(vid, aud)
Normalize()

There are three recently discovered issues with FilmCutter.
FilmCutter’s video viewer / player does not work well with audio only scripts, not that there is anything wrong with that Mr. Gates. It is just that I have not properly trapped the exceptions, my bad.
Along the same lines the script output property routines assume there will always be a video stream, again my bad.
If you have selected a display aspect ratio of 16:9 the player will refuse to play with some window sizes. Slightly moving the window edge solves the problem. I have not seen the problem when using 4:3 but do not know why.The audio only issues will be addressed by next version.

Going to come at FilmCutter as a user for the remaining days of 2005 and hopefully come back with a much improved program in 2006.

I wish all a happy and safe holiday.
Keep the cards and letters coming.

Ebobtron

[Fizick]

Ebobtron,
Many thanks for your works.
At last i try it.
But i will report bug report and suggestions. Did you really ask it :)

1. severe bug: I can not use two or more trims - some "unexpected characters" apeears instead of "+" at end of script:
t01 + t02
Please, anybody confirm it. (may be it is for Russian codepage only ?)
2. small bug: If I use loadplugin("filter.dll") instead of loadplugin("c:\plugindir\filter.dll"), script failed. You must use default dir, where script.avs is placed, but not filmcutter itself.
3.semi-bug: Where are windows controls ? Why i may not move filmcutter window ? :)
4. Avisynth function selection in Script window is nice. But how i can exit it without selection (cancel selection)?
4.1 IMHO, use it as simple name and parameters reminder window will be quite fine.
It may be not obligatory to select from list and put to script something. It may be done by hand too.
5. View select switching is a little complex. Why not place it directly on list (without tree)? Faster switching.
6. Preview window is very fast! It is very good (unlike AVSEDIT). 4:3 and 16:9 aspect is good idea. But it is missed the MAIN feature: direct AS IS output without any resising, (scale 1:1), pixel by pixel, precise view. And it must be default option! Probably, window resizing by mouse is bad idea (IMHO). It is very hard return to 1:1 scale later.
7.1 IMHO, preview window must start with stopped (paused) frame (not playing).
7.2. It will be very good, if after switching and editing in script window, the Preview was returned to not to start frame, but to same last frame. Filmcutter must remember this position. It is very useful virtualdubMod F5 feature (and to tune avisynth script parameters (like filter strength).
7.3. IMHO, previe window must not be closed after switching to script window, for easy contral above filtering changes.
8. I still want 2 frame window (aka timeline) in Video editor view. So we can see exact trim position (see both frame before trim and frame after trim).

Best regards!
I like to see othe opinions too. By the way , thanks for source code of your program.

[Fizick]

In addition I see interesting info about VirtualDub and reopen badly edited scripts
http://forums.virtualdub.org/index.php?act=ST&f=15&t=11178&
[phaeron wrote:] "The Reopen (F2) option deliberately opens a new version of the script without releasing the old version first. This ensures that if an error occurs on the reopen that VirtualDub still has the old script to fall back to. If the reopen fails, the new script is dropped; otherwise, the old script is dropped and replaced with the new one. This means that avisynth.dll will not unload when a reload occurs, since it always has at least one object outstanding."

[Ebobtron]

Ebobtron,
Many thanks for your works. At last i try it.
But i will report bug report and suggestions. Did you really ask itIt is very nice when someone likes your work. We get a better program when they don’t. I will not alway agree but I listen. :goodpost:
1. severe bug: I can not use two or more trims - some "unexpected characters" apeears instead of "+" at end of script: t01 + t02
Please, anybody confirm it. (may be it is for Russian codepage only ?) :( Everything in FilmCutter is “ASCII”, “+” = 0x2B.

if(spliceType == 1)
sprintf(spliceChar,"+");

if(spliceType == 2)
sprintf(spliceChar,"++");

Then later in the process:

while(t < i)
{
sprintf(bb,"%st%02i",spliceChar,t);
lstrcat(aa,bb);
t++;
}
ofile << aa;

Should I use:
sprintf(spliceChar,"%c%c",43,43);
2. small bug: If I use loadplugin("filter.dll") instead of loadplugin("c:\plugindir\filter.dll"), script failed. You must use default dir, where script.avs is placed, but not filmcutter itself.I can see where that is a problem “windat.avs” needs to reside in the source script directory. By having “windat.avs” in FilmCutter’s directory I don’t have to delete it and I have a backup of the last script loaded prior to any crash. An oversight by me otherwise. Can fix and I’ll rename it to fctemp.avs so you know where it came from. Intended to put a header in the file also.
3.semi-bug: Where are windows controls ? Why i may not move filmcutter window ?Because I am Lazy, I killed the title bar and killed the automated move from windows. I am sure that I can write something that allows you to click on the main window frame and drag it around, I just have not done it. I gave you a minimize selection in the menus, what more do you need. ;) I might be lazy, but I can drag the edges around. I will add it to the list.
4. Avisynth function selection in Script window is nice. But how i can exit it without selection (cancel selection)?
4.1 IMHO, use it as simple name and parameters reminder window will be quite fine.
It may be not obligatory to select from list and put to script something. It may be done by hand too.This one I did not miss. Just did not tell you about it. Menu select to show list / menu select to hide list. Ctrl+Tab to show list / Ctrl+Tab to hide list. Guess I can hide it with the escape key too. As for 4.1, I have a thought about having a “save last used parameters” option, could be useful.
5. View select switching is a little complex. Why not place it directly on list (without tree)? Faster switching.Did that mostly for organization instead of “Script Editor Window View”, it seem to make a little more sense. Been thinking about short cut keys but can not decide which to use. Any ideas.
6. Preview window is very fast! It is very good (unlike AVSEDIT). 4:3 and 16:9 aspect is good idea. But it is missed the MAIN feature: direct AS IS output without any resising, (scale 1:1), pixel by pixel, precise view. And it must be default option! Probably, window resizing by mouse is bad idea (IMHO). It is very hard return to 1:1 scale later.
7.1 IMHO, preview window must start with stopped (paused) frame (not playing).
7.2. It will be very good, if after switching and editing in script window, the Preview was returned to not to start frame, but to same last frame. Filmcutter must remember this position. It is very useful virtualdubMod F5 feature (and to tune avisynth script parameters (like filter strength).
7.3. IMHO, previe window must not be closed after switching to script window, for easy contral above filtering changes.
I have begun the rewrite of all of this, that you list above, I think you will like. I have kind of had my head in the function list and param help dialog. When done you will be able to select from a list of preview options that should set F5 on it’s ear.
8. I still want 2 frame window (aka timeline) in Video editor view. So we can see exact trim position (see both frame before trim and frame after trim).See above, all part of the same functions except for the additional video windows, which should nest in nicely.
Best regards!
I like to see othe opinions too. By the way , thanks for source code of your program.Yes, yes more opinions please..... and..... Your welcome, just return it when your done.
In addition I see interesting info about VirtualDub and reopen badly edited scripts
http://forums.virtualdub.org/index....T&f=15&t=11178&I have dropped phaeron‘s post for brevity. Not sure what your trying to tell me about, a way of dealing with bad edits or multiple instances of avisynth.dll causing a memory problem, both issues are in my head, we will see. The no video or audio only script issue FilmCutter has is my fault and will be fixed in the next release. Probably will not play but should not terminate the program at warp 10.
:thanks: for spending the time with FilmCutter
Ebobtron

[Fizick]

I am still do not understand, does Ebotron or somebody else has this problem with "++" for two trims?

[Ebobtron]

Hi Fizick,
Sorry for my poor attemp at an answer above.

I am still do not understand, does Ebotron or somebody else has this problem with "++" for two trims?I can not duplicate bug.
I checked the project output script in a hex editor and all was ok. This is what it should look like. t 0 1 + t 0 2 + + t 0 3
74 30 31 20 2b 20 74 30 32 20 2b 2b 20 74 30 33To repeat from above post.
Everything in FilmCutter is “ASCII”, “+” = 0x2B.
if(spliceType == 1)
sprintf(spliceChar,"+");
if(spliceType == 2)
sprintf(spliceChar,"++");

Then later in the process:
while(t < i)
{
sprintf(bb,"%st%02i",spliceChar,t);
lstrcat(aa,bb);
t++;
}
ofile << aa;

Should I use:
sprintf(spliceChar,"%c%c",43,43);I was trying to show you how the code is written, and if you thought a change would help your problem. If you are having trouble with "++", I am concerned about other charactors such as "(" ")" like "trim(xxx,xxxx)".

Sorry for my poor answer.
Ebobtron

[Ebobtron]

Hi all,

Fizick truly found a bug, easy to fix.

+ = 1;
++ = 2;
whatever happens to be in 4 bytes of memory = 0;

When FilmCutter first runs it has to create filmcutter.ini which it fills with blank data. If you never access the write script dialog you will never write over the zeros in filmcutter.ini "write script" field. To access this dialog box right click the scene list window in the video editor. This problem is very old.

Let me just remind everyone to right click everything you see, there could be or will be a popup or menu that could be adjustable

Great catch Fizick :thanks:
Ebobtron

[Fizick]

O.K.

About next:

I can see where that is a problem “windat.avs” needs to reside in the source script directory. By having “windat.avs” in FilmCutter’s directory I don’t have to delete it and I have a backup of the last script loaded prior to any crash. An oversight by me otherwise. Can fix and I’ll rename it to fctemp.avs so you know where it came from. Intended to put a header in the file also.

Renaming to fctemp.avs is fine. Putting it to script dir will work, but
you can consider two other possibility, when it resides in Filmcutter (or TEMP) directory:
2. OR you may try to add "SetWorkingDir (original path)" to beginning of project avs.
3. ELSE you may set working dir for filmcutter.exe (by some Windows API command).

[Ebobtron]

Renaming to fctemp.avs is fine.That is what I did. Putting it to script dir will workWorks great but
you can consider two other possibility, when it resides in FilmCutter (or TEMP) directory:
2. OR you may try to add "SetWorkingDir (original path)" to beginning of project avs.Works just as well but could be more confusing to user I think.
3. ELSE you may set working dir for filmcutter.exe (by some Windows API command).This does not work in simple form and could be a lot of work when the two above always work.
This could be revisited later.

I did look though the API functions could not find the one I need like below.
Class GodLike
{
bool readUsersMind(void);
};Then I could write:
if(!lstrcmp(fName,"Untitled")
{
readUsersMind();
}"When there is no path, there is no solution."
:thanks:
Ebobtron

p.s. Next

[Fizick]

Good news about fixing a bug.
(do not forget always set default case to any conditional block! :))


I will like filmcutter.exe soon :)
But I dislike, if in every directory we will have fctemp.avs. :(
Or you will delete it on exit?
Way "2" with Setworkingdir("xxx") temporary line is better in my opinion.

best regards

[Ebobtron]

@Fizick

Good news about fixing a bug.
(do not forget always set default case to any conditional block! )
Yes of course.
I will like filmcutter.exe soon
Start liking FilmCutter sooner, please.
But I dislike, if in every directory we will have fctemp.avs.
Or you will delete it on exit?
fctemp.avs is gone. windat.avs returns to FilmCutter directory.
Way "2" with Setworkingdir("xxx") temporary line is better in my opinion.
Yup, that is what I have done.
When source = untitled && load*() is used
if(createPreviewAvs())
Warn user that script may have to be saved to resolve search path for file componetsStill lots of ways for user to get into trouble d2v =“my.d2v” instead of d2v = “d2vpath\my.d2v” If script is untitled (unsaved) lots of errors are possible.

No easy fix for file descriptions that contains no drive\directory information.

Next was window controls: != 1.3b

1.3b will have new preview window options

video rightside, script properties from AviSynth leftside with frame lock
video top, script editor bottom with update button and frame lock
dual window saved source left, edited left, script editor at bottom
original size for sure and maybe scrolable zoom or full screen toogle

Lots to do
Happy happy,
TTFN
Ebobtron

[Ebobtron]

Hello everyone and Merry, HO HO.
Made some small progress on 0.0.1.3b., but lots still to do.
If you'd like a preview of the new preview?
http://members.aol.com/avsfilmcutter/fc13alpha.zip

The script preview functions now have two modes the first or standard has a frame counter with frame advance and reverse buttons. Also a jump to frame window. The second or w/script editor has the script editor text window displayed in the lower portion of FilmCutter's window and an update button for loading the edited script data into the viewer. Preview w/editor uses the same editor, it has the same menu and all functions of the editor are available for use.

Entering preview can be done by menu or the F5 key. F6 will jump to the preview and begin play from wherever the preview window last was, and then control play/stop in the preview window.

You can jump to any frame directly by entering the frame number into the jump window and pressing enter.

You can change the preview mode while in preview by using the video window menu preview mode selector.

This and future versions will draw a more defined line between the script preview feature and the video viewer.

I have included the current changelog with the alpha.

Oh yea, ever sense the idea of an imported filter/function list was thrust upon me by Fizick, the gray stuff between my ears has been churning the stock edit control functions and I have proven to myself that I could write some code that would draw a colored overlay for the keywords. I am not overly please with the results. You can see it by clicking the syntax highlighting item under script options in the script editor popup menu.

If your new to avsFilmCutter the main page is here:
http://members.aol.com/avsfilmcutter

[medp7060]

I tried 0.0.1.3b. As reported before, all the buttons on the initial windows are missing their text, and the video does not go into preview. I am using XP SP2.