avsFilmCutter Ver 2.0 b Video Editing tool for AviSynth [Archive] - Page 2

Ebobtron

27th December 2005, 02:56

@ medp7060
Could you please show me the script and also which tools does the script work in, VirtualDub, MplayerClassic, please? What version of AviSynth?

Do you recieve any warning messages from FilmCutter?

Also after starting FilmCutter without changing the text in the editor press F5, you should get an error message from avisynth. Switch to Video Viewer and right clicking the video window open a script there it should load there also.
With your script loaded in the editor press F8 that should show a short list the output properties for your script.
I see. Please add something above the buttons saying "user defined".

I did use the menu item PreView Script. no video at all although the same script can be played well using other tools. It actually hang and I could not return to the editor by F5.

Thanks for the information, I need more though.

medp7060

29th December 2005, 12:00

LoadPlugin("C:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
DirectShowSource("E:\ccc.avi",30)
ConvertToYV12()

It is palyable by VirtualDub, WMplayer. Version of AviSynth is the latest one 2.56.

I loaded the script and F8 worked. Then "Preview script" failed and I got no warning messages from FilmCutter. It hang.

Ebobtron

3rd January 2006, 22:42

Hello all,
Hope everyone had a nice holiday.
New alpha2 is at http://members.aol.com/avsfilmcutter/fc13alpha.zip

alpha 1 had broken parts everywhere:
no encode from script menu
the scene editor lost its edit row feature, it was really broken and took forever to find. Caused by my adding the filter help dialog. Really easy to fix though.
lots of little things related to focus

"DirectShowSource"Don't you just love things that come along and stop you dead in your tracks? Why AviSynth's output is different when using DSS as compared to any other input filter is beyond me. Maybe the overall environment is different, but as things relate to FilmCutter's viewer, something is different.@ medp7060
You wrote, "It hang." It sure do.
If you right click on the task bar button for FilmCutter twice the program will un-hang, or it does for me.

The program is halting. When the filename(the script in the editor) is loaded into the viewer, the stock windows function that performs the task never returns control to FilmCutter. My system almost always loads the file and shows me the video but never returns from preview without the hang.

The same thing is happening thought, when it loads and fails it closes the file and hangs. When it loads successfully it hangs when you close the file by switching out of preview.

When you ask for the script output properties FilmCutter uses the same functions that VirtualDub uses and they seem to be able to open and close the file without trouble.

My investigation into this will continue, but the facts support no solution at this time, except that I need a different viewer and that is another story.

Thanks again for calling this to my attention.
:thanks:

Ebobtron

11th January 2006, 20:19

avsFilmCutter 0.0.1.3b
http://members.aol.com/avsfilmcutter
or
http://rapidshare.de/files/10860233/FilmCutterVer0013beta.zip.html
Please check the changelog and the user's doc in the zip file.

Fizick

12th January 2006, 23:19

Huge amount of changes! Thanks!
I will try it, but I have not very many time now.

Ebobtron

1st February 2006, 20:44

avsFilmCutter 0.0.1.4b

Version 0.0.1.4beta is on the website. Most of the important changes are internal. Added an optional "Info" window to the Script Preview feature, this information is gathered directly from AviSynth and should be more complete.
As an example ColorSpace will be reported as RGB instead of DIB. "Script Preview" has its own menu to better accommodate future additions to this feature. The Video Editor Source/Project check box has been replaced by two radio buttons Source and Project.

http://members.aol.com/avsfilmcutter
or
http://rapidshare.de/files/12329053/FilmCutterVer0014beta.zip.html

:thanks:

Amnon82

3rd February 2006, 16:36

Ebobtron

3rd February 2006, 19:23

Hi Amnon82,
Thanks for the “Nice App”, I think it is a good idea that needs work.

I will answer the last question first. C++ using “Microsoft Visual C++ Toolkit 2003” with “Microsoft Platform SDK February 2003” both free from Microsoft http://msdn.microsoft.com/visualc/vctoolkit2003/.

As for the second, “Does AVISYNTH only displays RGB frames?”. The answer is no. AviSynth outputs YV12, YUY2 and RGB and I believe a couple more are planned.

Concerning the white screen, FilmCutter will show a white screen if no file is loaded into the viewer. Otherwise it should show the first frame of video, if it is black, then it shall be black. FilmCutter should view any file you can load into VirtualDub.

It is a little hard to tell by your question, is FilmCutter only showing black frames with YV12 and YUY2. Does your script file work in VirtualDub, does it contain DSS as an input source?

Your problem is I think easier to define. If you will let me assume that you are getting the frame data and drawing it to the screen then only the RGB will work without some conversion in between. May I recommend that you look at the source code for two AviSynth plug-ins, avsMonitor and tritical’s TMonitor. I can not really read it very well, but it is clear that colorspace testing and converting is going on.

Thanks again for looking in and for the nice comments. And please if you could calm my fears about the black frames.

Inc

3rd February 2006, 20:41

@Ebobtron: I took a look on your programm. Nice app.

I've two questions for you:
I'm coding in Delphi and use avisynth_c-port for open AVS-files in my newest build of AutoQ2. I coded also an sample app with a preview option. avisynth_c displays only files in RGB. I tried also your app with YUY2, YUV12 and got a black screen. In my apps I got a white one. Only RGB shows the frames. So my first question is: Does AVISYNTH only displays RGB frames?

My second question: In what language do you code?

Your display is rgb, so your graphics cards delivers a rgb signal and so you do use the GDI API routines or maybe delphi native commands to show the image.
To show the image, you have to feed to your code a rgb one.
(If using DirectX then you could pass the yuv image via the hardware on your graphicscard which could do the conversation, but lets stick on straight rgb handling).
Do apply in your delphi avisynth_c example a condition where its asked about the incoming Colorspace from the resulted clip. There are declared functions in the avisynth_c interface which can do that like 'IsRGB32()'.
If its not the case, then do invoke via a "ConverttoRGB32()" , take the clip from the result and use avsiynth's BitBlt() to perform an image blocktransfer to your determined target-imagepointer. Now the frameserved Imagedata is rgb which is easy to handle for your application's video preview routines by just requesting the bitmaps from the mentioned target-image-memorypointer. I do use RGB24 as output with no problems but as I heared its better to serve RGB32 as its DWORD aligned (if I understood right) as most of the GDI API routines do prefer DWORD aligned RGB data.

Amnon82

5th February 2006, 12:25

Thx inc for that answer. It was what I thougth. I wrote you pms, cos I had troubles to do the 'ConverttoRGB32()' using invoke. Please forget those pms. I found the solution:

http://img145.imageshack.us/img145/4881/untitled21ov.th.png (http://img145.imageshack.us/my.php?image=untitled21ov.png)

Sample + Source (http://scifi.pages.at/amsoft/files/avisynth_c_sample_v3.7z)

Fizick

5th March 2006, 23:09

ebobtron,
I try v1.4b.
at start (in new empty folder) it creates files with a strange names "ilmcutter.exe encoder.ini", "ilmcutter.exe filmcutter.ini", and "ilmcutter.exe rowdat.fcr"
And of course then it does not find "encoder.ini", etc. :)

Ebobtron

6th March 2006, 14:53

Fizick,
Sorry your version of 1.4b not work so good. :o

I checked my version and found that all was well.
downloaded the current version from the website and reinstalled here, all was OK. Is it possible that your download is bad, please retry.:confused:

Nothing internal changed enough to cause problems like that.
:confused:

I see you keeping busy with Russian AviSynth Page (http://avisynth.org.ru/) and your many other pursuits. Glad someone is doing good.

Barly able to keep up myself.

Fizick

6th March 2006, 20:39

Sorry for false alarm. Probably somewhat was wrong with my PC. :(
Today all correct.

So, I test a litle more far :).
Filmcutter is still not usable for me. I do not know, how to set the picture size of preview window exactly equal to frame size.
I need in it to control effect of different denoisers etc.
Where is this option? May be I missed somewhat again?

Ebobtron

13th March 2006, 19:28

Sorry for my slow response. I have been ill for about a month and to make matter’s worst I decided to give up my 35 year old smoking habit. So I am not even sure that I am sane.;)

Filmcutter is still not usable for me. I do not know, how to set the picture size of preview window exactly equal to frame size.Yes, I know. I feel like a young student who has forgotten his home work. I could have included this feature in either of the last two versions, but my focus was on the preview window with script editor, which you have failed to comment on, should I assume that without an “actual size” video window this feature is useless too?

In my defense since the beginning of the year my attention to the core project has been deflected by FilmCutter’s need for a more competent viewer. So most of the work in FilmCutter has been “non related” to viewer support, except as needed.

Sadly most of my total time has been completely spent away from FilmCutter as the work to secure a new viewer is not at all related. I have spent some wasted time waiting for mail that never comes, questions that don’t get answered, but I have kept working.

Version 1.5 beta is close but my mental state is still a little too flighty to be relied upon for testing. I want some version of the new direct show viewer testable and I will implement some sort of “source video size option” in “preview“, as well. Documentation changes and updates will take more time also.

Anyway thanks for the help and hopfully by the time I get FilmCutter up to Version 2.0 she'll be a pretty usefull tool.

http://members.aol.com/avsfilmcutter

Fizick

13th March 2006, 21:08

I do not wait quick answer,
and I like your combined preview and mini-script window!

I will wait version 1.9 :)
(2.0 will be new alpha :)

Ebobtron

28th March 2006, 00:03

I do not wait quick answer,
and I like your combined preview and mini-script window!

I will wait version 1.9 :)
(2.0 will be new alpha :)

:( What are you talking about.

I'm sorry I need help now, I can not wait for 1.9 or 2.0. :)

Ebobtron

21st June 2006, 10:35

Hello, hello it has been a long time.

Version 0.0.1.5 beta is up on the website for download.
http://members.aol.com/avsfilmcutter

it can also be downloaded from
http://rapidshare.de/files/23665378/FilmCutterVer0015b.zip.html

You XP user's should be happy, the colors should look like I suddenly know what I am doing and the little round corners should be there too.

More info is on the first and second posts.
http://forum.doom9.org/showthread.php?p=687842#post687842

:thanks:

Ebobtron

18th July 2006, 07:46

Hello to everyone. :)

This thread is one year and a couple of days old and for its birthday I gave FilmCutter a Save Wave function.

Direct Show is available everywhere for all needs and is now the default.

Details are -> http://forum.doom9.org/showthread.php?t=97438
Web site -> http://members.aol.com/avsfilmcutter
Rapid Share -> http://rapidshare.de/files/26144968/FilmCutterVer0016b.zip.html

Thanks Fizick for all the help and support.
Sorry, I have not resolved all the issues related to the script preview with editor and all. But with the viewer thing sort of dealt with I can spend my time with the view layouts using code that will work with the new viewer (tried to make them the same but they behave differently).

A small caution for you wavers out there.When I wrote the save wave function I was concentrating on 64 bit integer math on a 32 bit platform so I can get the thing to properly write a 4 gig wave file. I sort of forgot that someone saving a wave that large might want to pause or cancel the save. Once it starts it will not stop unless you stomp the program externally.

If you going to do much large file wave saving, I'd clean the air holes around you harddrive. Sort of spins them right on up.

I will fix this, next version.

Thanks, enjoy and please let me know. :)

Ebobtron

2nd August 2006, 00:50

Hello there,
I have a new alpha on the website,
see http://members.aol.com/avsfilmcutter/alpha.html

details will follow in the change log (second post (http://forum.doom9.org/showthread.php?p=688196#post688196))
info on the alpha page is correct, it just lacks the information below about the direct show filter interface.

for those interested I have uncovered the direct show filters interface for those filters in use by the viewer in FilmCutter. that of course is not unusual I have seen that in a visual basic interface. What is different this time is that the filters property pages are displayed in a window that can be in the background, but the best part is that they are in their own threads. You may pause the video, jump around in the video.
You can open multiples, even three or four, open them all.

closing FilmCutter will destroy the windows but breaking the filter chain by reloading or loading a different video file will leave non-working filter pages on the screen.

Ebobtron

14th August 2006, 20:05

hello all,
I have another alpha (alphabeta17_b3.rar) loaded, it can be had @ http://members.aol.com/avsfilmcutter/alpha.html

The direct show video player in alphabeta 17b2 would eat your computer 100 Megabytes at a time. AB17b3 should work as advertised. Thanks go to Fizick for catching the memory leak.

Fizick is also responsible (his idea) for the other work I am doing with the filter / functions help dialog window and it's workings.

I have started work to allow AviSynth documentation calls from within FilmCutter.

Select function / filter name in you script then press F1
Sort of works, sort of does not.
Also
Select entire function and parameters then press F1
Select from first letter in function / filter name to the closing ")" no more.
Currently the alpha throws a clip name list which could use testing. Then if the your number of parameters match the filter / functions total parameter list it will try and fill the parameters in the dialog window that pops up.

This is real early so if anyone has some algorithms for this, I'd love to see them. This may be customizable but I really doubt that I could ever write code that parsed all the possibilities or that could recognize them. Because I don’t know what they are.

Have fun and thanks for the help! :thanks:

I am looking for ideas.

Ebobtron,

Fizick

14th August 2006, 20:48

alpha, prealpha, alphabeta ...
Thanks. :)
"Multi pane video viewer" - ?
I am still ask for TWO frames - two subwindows in video editor (previous and currect), to cut between.
That is what I name as "timeline".

more opinions?

Ebobtron

22nd August 2006, 04:29

@Fizick said "alpha, prealpha, alphabeta ... "

Got to call them something. :o

Beta may be ready at end of week. Going to include early imp of your timeline thingy, one extra video window. Just something to play with.

More work was done to the filter parameter helper dialog.
loads your parameters better and loads the clip combo box with a varible list from the script.

Ebobtron

18th September 2006, 09:20

hello hello all,

new version time again.

Some links related the this.

First post this thread (http://forum.doom9.org/showthread.php?p=687842#post687842)

Alternate download site (http://rapidshare.de/files/33530893/FilmCutterVer0017b.zip.html)

Home (http://members.aol.com/avsfilmcutter)

That was easy. :thanks:

vcmohan

19th September 2006, 04:04

My plugins are now at my page. Latest version of TransAll is in this page. May be you can change the link url to my page.

Ebobtron

19th September 2006, 07:50

My plugins are now at my page. Latest version of TransAll is in this page. May be you can change the link url to my page.

If you, Sir, are referencing the link on the page http://members.aol.com/avsfilmcutter/fcwebguideTALL.html. I can, and have done so. I had noticed your new page, but thank you for the reminder, It might have been some time before I updated it (it is over ten months old now).

I read the small bio (http://www.avisynth.org/vcmohan/vcmohan.html) you posted as well.

A funny thing about this is that my wife, just yesterday asked if maybe I was getting a bit too old for this "computer thing" she calls it.

It turns out that you got your "Masters Degree in Applied Physics" the year I was born, I figure I am safe and not too old.

I think we will have to start referring to you as Mr. V.C. Mohan, at least I will.

Thanks for the great plugins. :thanks:
Rob

vcmohan

20th September 2006, 03:51

Well, I think that this computer thing is what keeps me (at least my mind) young.

Thanks for liking my olugin

Ebobtron

1st October 2006, 10:22

FilmCutter can now save the individual channels to .wav files in one pass.

More details here -> http://members.aol.com/avsfilmcutter/alpha.html

Ebobtron

30th May 2007, 19:30

New version
0.0.1.9 beta

Lots of clean up from 1.8b and PSDK R2 change over.
Visa users report more stability with the last alpha.

New:
Tool tip enable/disable moved to Options (old preference) dialog page, this dialog page has tool tips itself.
Script editor line numbers are now an option on the options dialog page.
You may comment out large blocks in code with one click of the mouse. See the "#" on the toolbar "Shift+Ctrl+#". Or just the line the cursor is on.

Here on the form (http://forum.doom9.org/showthread.php?p=687842#post687842)
There (http://www.avsfilmcutter.com)

:thanks:

Ebobtron

13th June 2007, 15:05

:(
I offer an alpha. 0.0.2.0 alpha 1 - 13 June 2007

This has updated code to do properly what I could not seem to do before. (baby steps)

Those who have experienced sudden termination or crashing when attempting to use script preview F5 or the video editor F11, should see improvement. Fizick reports that it works fine (does not crash). :) :)

http://avsfilmcutter.com
http://avsfilmcutter.com/alpha.html

Thanks IanB, Leak, and of course Fizick

Ebobtron

25th June 2007, 15:56

:)
avsFilmCutter version 0.0.2.0 alpha 2 - 24 June 2007 is available for download at the website.

http://avsfilmcutter.com

Thanks to IanB's generous efforts a nasty little crash has been resolved and thanks to his patient tutelage I have applied what I have learned though out the program, which resolved some more.

This is also the first version of the program that is built using M$'s new free development package (VC++ 2005), minus that damn IDE of course.

Version 2.0 beta will be open source for those it matters to.

Now, I hope I can continue work on the worlds first avisynth based NLE GUI minus 1 or 2 maybe even 3, don’t remember anymore. :rolleyes:

:)
Thanks all

Ebobtron

21st July 2007, 21:31

Hello,
There is another alpha to play with while I polish the support files. www.avsfilmcutter.com
:)

Ebobtron

28th July 2007, 00:55

2.0 beta is at the web site www.avsfilmcutter.com, as are the source files.

Enjoy :)

:thanks:
Rob

yawoo

1st August 2007, 03:39

Just let you know that this is the best avs editor tool I have been used. Please keep working.

Ebobtron

6th August 2007, 21:29

@yawoo

Thanks
ebob

anton_foy

22nd August 2007, 18:55

Ebobtron

22nd August 2007, 20:00

Hi!

I have used avscutter just a short while and maybe the function is there but I cannot work it out.
Is it possible to use a specific .avs -script for every individual clip?

If not I personally think it would be a great feature to implement.You are reading my mind
See: very early transitional documentation posted lastnight. (http://avsfilmcutter.com/fcwebguide2a.html)

It is the next logical step in development and although implemented; it is fraught with small mines. This interface should be so much easier to use. I can probably post an alpha in a couple if you what to play

Great program BTW!:) Thanks :)

anton_foy

22nd August 2007, 22:42

Whohoo!

I'd love to play with it. Since I use High Definition footage I downscale to make it easier to edit it and when finished I want to apply all the filters in the correct rez.

This ones gonna be my new favourite, it will make my work a thousand times easier!

Ebobtron

25th August 2007, 05:30

here is the alpha you can play with.

http://rapidshare.com/files/51649814/FilmCutter21a1.zip.html
get FilmCutter21a1.zip (http://www.avsfilmcutter.com/dev_link.html)

Latest alpha is here http://forum.doom9.org/showthread.php?p=1038309#post1038309
and here http://forum.doom9.org/showthread.php?p=1038537#post1038537

some details can be found @ http://avsfilmcutter.com/fcwebguide2a.html

oops sorry, :o new users will need the full 2.0 b package, here (http://avsfilmcutter.com/download.html)

things to look out for older project files will load without rejection but will create junk, the web page above has details about how to fix them. the mod marks (modification markers *) will only be reliable when editing with a single script. also filmcutter will not warn about saving the project if it is not saved. the status bar will show the source file being used and the project output script when viewing your work. f8 will display the output properties of the script in use or your project script if you have clicked view project.
most actions you initiate will cancel what your are doing and proceed, this can cause some trouble if you are in the middle of a row edit or row insert. clicking view project will not cancel the row edit or row insert, use the cancel button, view project will mess the frame numbers in you insert or edit. don't forget to save your work the direct show compression manager interface is not disabled, it is also far from finished, so much minutia.
the command line encoding interface is still available from the script editor menu or f7. is now in the main window menu too. the source for the encoding will be the file name shown on the status bar. click the view project button and press f7

no wizards or genies in there, if your scripts don't have the same properties, filmcutter will only warn you when you click view project.
a complete output script will only show in the editor as part of the total project when the project is saved. view project shows the whole thing but for some reason the last edit will not show up in the script editor unless the project has been saved.
can not delete or remove source files yet, do it manually in the editor with the *.jfc files

things you can do

open a source file and start editing, you no longer have to create or save a project be editing or viewing your work.
single source editing
multi-source editing
add additional sources at any time.
switch between scene and script editors at will, what ever you are viewing in one you view in the other, switch in either.

:thanks:

anton_foy

27th August 2007, 13:31

@Ebobtron

I have tried the new version a while but I cannot do a few things:

1. If I want to change the in and out numbers i cannot do this after i clicked "add".

2. How do I add a new script for each clip with the "a"- button? When I click it only the source .avs is there and I cannot choose another.

3. If i want to change the order of the edited clips in the video editor i can't move them.

4. In the AVSFilmCutter generated avs-script i cannot change anything, afterwards everything is like it was before I changed it.

One good thing to implement I think would be to be able to change the AVSFilmCutter generated scripts yourself if u want to. But I thought you could do that already?

Maybe I did not do these operations the right way so please tell me:)

I can feel it getting more and more powerful, I am really excited about it:thanks:

Ebobtron

27th August 2007, 16:58

@ anton_foyThanks for the feedback
@Ebobtron

I have tried the new version a while but I cannot do a few things:

1. If I want to change the in and out numbers i cannot do this after i clicked "add".
You have many options, when you click the cutter button, which has changed for the next version.
When the cutter is grayed, click the frame start or end windows. Which ever one you click will become active, the viewer and frame count window will jump to that box's numbers and the box will again follow the viewers frame counter or you can edit the numbers in the little box which is kind of messed up ( there is a neglected error in the focus management ). When done in one box click the other and then do it again if you wish. When satisfied click add. Add the scene to the list and then click on the row button to edit. Use the other mouse button while over a row button to delete the scene, insert above or below it or jump to that scenes source and the start or end frames. Preview button lights up with the add button, click it and adjust the end and start frame numbers. This is a little weak, the start and end buttons retain the original numbers. Clicking save moves the new numbers down into the scene start and end frame windows.
I have changed the cutter button's Icon style to a text button labeled to follow along the steps of frame number selection, "Set start frame", "Set end frame" and "add or cancel".

2. How do I add a new script for each clip with the "a"- button? When I click it only the source .avs is there and I cannot choose another.The safe way to add another source script is from the main window's menu,
Project | Add Source Script, currently if you try to use the File | Open Script File, FilmCutter changes the source script unless you have added a scene to the scene list. With a defined scene in the list use of File | Open Script File causes FilmCutter to crash ( a bug I missed in the alpha ). If you use the add Source Script it always works or seems to. I also intend to put a add button on the source list window with a delete source button.

3. If i want to change the order of the edited clips in the video editor i can't move them.
Sorry, I must have lost the move up and move down buttons :)

On the list
4. In the AVSFilmCutter generated avs-script i cannot change anything, afterwards everything is like it was before I changed it.When you ask to view the project, FilmCutter generates the script and then loads the video viewer or loads the script into the text editors window. If you leave the text editor view or go and view a source script FilmCutter will regenerate the script and load the new one when you wish to see it again.

From the text editor, right click the mouse button while the pointer is over the text window, or the one you don't normally click things with, and choose Save Script As
One good thing to implement I think would be to be able to change the AVSFilmCutter generated scripts yourself if u want to. But I thought you could do that already?

Maybe I did not do these operations the right way so please tell me:)If I have confused you with FilmCutter's interface, you are in very good company. I didn't try to be confusing, only different. The context menu thing is to me a god send, to others a cloak. Instead of asking you to search though menus looking for a function or feature I have hidden the programs operation. If you can see it, click it, if nothing happens right click it. Next version do it again.

Another thing I am working on is the little tool tips, they can change as the user progresses though the editing steps as a reminder.
I can feel it getting more and more powerful, I am really excited about it:thanks:Me too.

Thank you for that and thank you for taking the time to share your thoughts with me.

Thank you again :thanks:
Rob

Ebobtron

28th August 2007, 18:50

@ anton_foy el at
FilmCutter21a1082807.zip (http://www.avsfilmcutter.com/dev_link.html) dated: 27 August 2007
www.avsFilmCutter.com

this build of FilmCutter works a little better. the ability to jump from one function to another, even in mid edit, should cover most cases properly.

example: you start to edit a row(click on a row button) but then decide to view the project first, if you forget to click cancel, FilmCutter will just cancel for you; no fuss no data loss.the crash mentioned in the last post has been fixed.

when you are working with a project any way you open a script will add the script to the project, the exception being the single case when you may have switched to the media viewer, the use of "File | Open Media File or Script" from the video window's menu, will only load into the viewer, this allows for viewing source scripts and some media file types without trying to load an mpg file into the text editor.

prior verisons of FilmCutter required the user to save a project to get FilmCutter to generate scripts.
the user now has four ways to triger a project:
add a scene to the scene list
use Project | Add Source Script
use Project | Save Project As
open as save project

FilmCutter will eventually nag when you do something that would result in a lost of project data.

:)
ebt

anton_foy

29th August 2007, 10:29

Wen I Add a new Source Script (containing only the filters I want to apply and no videosource call) the image gets a green too gray gradient all over and no picture.
If I add a videosource to the new script it works but that will just kill the whole idea of adding source scripts in the first place.:p

Sorry Ebobtron but the link for the new version is down.

Great work, keep me updated:thanks:

Ebobtron

29th August 2007, 10:48

I am sorry but you may have me at a disadvantage, that being I don't understand what you wish for.Wen I Add a new Source Script (containing only the filters I want to apply and no videosource call) the image gets a green too gray gradient all over and no picture.
What is a source script?

If I add a videosource to the new script it works but that will just kill the whole idea of adding source scripts in the first place.:p
A source script to me is one that contains a source.

Sorry Ebobtron but the link for the new version is down.
Great work, keep me updated:thanks:
here is a rapidshare link.
http://rapidshare.com/files/52002389/FilmCutter21a1082807.zip.html

anton_foy

29th August 2007, 12:50

Sorry, I wasn't thinking right this morn...

I had forgot to copy the video source line into every new script:

mpeg2source("C:\III.d2v")

Now it is working but I think it would be easier if I did not have to use a new script for every single clip.
But maybe this will be a hard thing to do.
I was thinking more like adding a script similar to adding a preset with filters but the preset is an .avs-script (containing only the filters and the way you would like to use them).

That way you could use the source-script(only containing the footage) and later add the filters for your purpose (e.g. denoise, saturation, sharpening or whatever) in different .avs scripts.

Confusing? It is hard to explain in writing for me, if you want
I can maybe show in a more visual approach.

Another idea I had was to put the filters directly in the AVSFilmCutters generated script like this:

Va = Import("C:\CUT.avs")

t01 = trim(Va,25,112)
Levels(0, .56, 255, 0, 255)
converttoyuy2(true)

t02 = trim(Va,424,695)
AddGrain(15,0)
converttoyuy2(true)

t03 = trim(Va,1049,1263)
Levels(0, .30, 255, 0, 255)
converttoyuy2(true)

t01++t02++t03

Ebobtron

1st September 2007, 04:02

@ anton_foy
:) For the continued feedback. :thanks:
I had composed this long answer that now seems preachy in my current state of mind. So I don't think boring you to death with my philosophy of script writing is an appropriate way to say thanks.

The bad news is that there are many ways to approach script writing.
The good news is that there are many ways to approach script writing.

Where to put filters depends on the filters and where the final result is going. Opinions on this will vary widely, depending of course on the filter. I think that most would agree that cutting and splicing at the very end of the script should cause the least amount of grief.
Looking at your example:Va = Import("C:\CUT.avs")

t01 = trim(Va,25,112).Levels(0, .56, 255, 0, 255).converttoyuy2(true)
t02 = trim(Va,424,695).AddGrain(15,0).converttoyuy2(true)
t03 = trim(Va,1049,1263).Levels(0, .30, 255, 0, 255).converttoyuy2(true)

t01++t02++t03
Will work just as well as:Va = Import("C:\CUT.avs").converttoyuy2(true)

t01 = trim(Va,25,112).Levels(0, .56, 255, 0, 255)
t02 = trim(Va,424,695).AddGrain(15,0)
t03 = trim(Va,1049,1263).Levels(0, .30, 255, 0, 255)

t01++t02++t03Only the frames called would be converted, so you gain nothing converting only the frames you output, but it does not hurt anything, I think.
If FilmCutter could be taught to treat every group of frames defined as a unique object that is then modified by the group of filters defined for that object.

That is a little ambitious for me and out of the current structure, though not completely impossible.

As far as filter presets, look at creating user functions that are stacks of your favorite filters for a given task. Or write your own script templates.

If some of your concern is the way some filters really can make real-time editing a painfully slow thing to endure. Those filters can be disabled manually with the # comment thingy or you can do the following:

Create and put in the AviSynth plug-in folder a *.avsi with the following line in it.

FCFilterEnable = False

Then use the following code in all of your source scripts.

FCFilterEnable = True
function filters(clip c)
{ c
# place your video processing filters starting on the next line
AddGrain(15,0)
Levels()

return (FCFilterEnable) ? last : c
}
FiltersWhen you begin your frame or scene editing with FilmCutter comment out "FCFilterEnable = True" the false definition in the avsi file will kill your filters, when done put "FCFilterEnable = True" at the top of the script FilmCutter writes for you and all the filters will be enabled in all of the source scripts for sending to an encoder.
This is easy to mess up but can work very well. As long as the method of implementation was locked down firm, FilmCutter could rewrite the avsi or add the necessary enabling line in the script.The options for automating filter placement and tweaking is better left to AvsP, that is why I put the buttons that launch external programs next to the editor.

So much for the non boring reply.

My reason for the multiple source interface is two fold, a multiple document editor is more useful that a single editor( notepad ++ is a good example and once I work out its relationship to the project implementation I will implement that as well. The other reason for the multiple source support is a multiple camera support idea I have where with the satellite video windows that are now kind of a waste can contain a separate source synchronized to some main source where FilmCutter does the keeping track of all the frame offsets, this is why the editor needs to be very freewheeling.

How some last minute hype. The next release of FilmCutter will have, besides dissolves and fades, "wipes"; thanks to a mask transition function, that stickboy wrote.

Now doesn't that just leave you wanting more. :)

If you wish to share your ideas in any way, I am up for a listen or look and learn.
:thanks:
Rob

anton_foy

13th September 2007, 14:26

Hi again Ebobtron and everyone!!

What if I want to encode as Quicktime using the QTOutput("C:\vid.mov") -command?

Since Im editing in HD I don't like to export as uncompressed avi and then re-export it as QT in Vdub.

Thanks

Ebobtron

13th September 2007, 22:10

@anton_foy,
hello back at you

What if I want to encode as Quicktime using the QTOutput("C:\vid.mov") -command?
? Ok, what is preventing this ?

If you are questioning if this works ? The answer is yes.

Add your QtOutput() statement to the bottom of the " *_fcprj.avs " file avsFilmCutter writes for you. Of course don't forget that QtOutput doesn't like YV12, FilmCutter will pass AviSynth's objections to you if you forget. Once you have added the QtOutput() statement press F6 to begin the encode.

There is a nigyysob however. Before FilmCutter loads a script into the viewer it opens an interface to AviSynth, which tests your script for errors and grabs a handful or two of script properties. When using a plug-in like QtSource, Tmonitor or SoundOut that have a dialog, GUI popup, interface, the interface window will open during the test before loading into the viewer. With Tmonitor or SoundOut they vanish as quickly as they show because their interfaces are available for use but require no immediate interaction with the user.

QtOut() on the other hand can require setup before it allows the process to continue. Therefore the first dialog window OtOut() will pop will be ignored because as soon as you click the OK button the script is closeed and then opened with the viewer which will pop the interface dialog window again.

If you are instead suggesting a suffix option for statements that could be added at the end of the projects output script? This is on the list although it has been way down, somewhere on the list. It would kind of become a menu item similar to a "Finalize and Save Script" kind of thing.

Since Im editing in HD I don't like to export as uncompressed avi and then re-export it as QT in Vdub.

Thanks
Again I am not sure about the question. Why export avi from FilmCutter, just load the scirpt into VDub. Those big buttons on the side of the script editor are there just for that purpose.

Thanks I hadn’t paid much attention to QuickTime plug-in by tateu http://forum.doom9.org/showthread.php?p=753774#post753774 wish it had sound options. Or did I miss something?
:thanks:

ebob

Ebobtron

27th October 2007, 14:30

Hello,
The results of my latest brain storm or brain fart (:o) is ready to share (maybe). An unofficial alpha version FilmCutter21a2_102707.zip (http://www.avsfilmcutter.com/dev_link.html)
…
If FilmCutter could be taught to treat every group of frames defined as a unique object that is then modified by the group of filters defined for that object.

That is a little ambitious for me and out of the current structure, though not completely impossible.
…
I quote myself to remind some of you about my remark as FilmCutter now does indeed maintain scene information as an array of class objects. The difference in implementation is subtle, but the power and flexibility is kind of wow. No provisions have yet been made to address the idea of a clip based filter stack as suggested by anton_foy, but now the option is possible.
Having all scene data as an array of objects makes the idea of a GUI time-line much easier to wrap my head around. This new interface, although functional, seems overly simple and maybe even crude. I remember telling Fizick that I would rather purchase him a copy of Premiere than write this kind of code. Maybe I should have left it at that, but I like to learn new things or at least experiment with new things. I did prove to myself that this kind of programming is frustrating if not difficult. I am not crying the old “poor me” thing, I have just gained a new respect for the people that write things like this. The frustration is the hours of work and the dorky looking result or if not dorky, at least unsatisfying result.

So let me wring out the crying towel and get back to announcing the new updated look for the web pages.
Oops, sorry, could not resist.

A new alpha is indeed available for download and I changed the web page look. I mentioned that I believe the time line interface is a little crude. Once worked out it will be no trouble to add a sound track interface to the timeline which is the end goal.

So I need your help, please, go ahead complain all you want. I’m suffering a brain freeze and could use some fresh ideas. Like what color should clips cells really be and how about a color when highlighted. I am sure someone out there knows how those clever little audio waveform graphics are done.

www.avsfilmcutter.com/alpha.html has some details and snaps.

:) thanks for looking in :)