code a java avs writer?

jjamriska · Post by **jjamriska** » Wed Dec 08, 2004 10:43 pm

heres a good question for all you, newbies or amv making gods. i program in java for college classes, and next semester i have a software engineering course. i know that one of the most frustrating things for new creators is learnig the plugins for avisynth and writing the scripts. if a java application/ applet that wrote the scripts from gui input was created, would you use it? it would allow for direct editing as well...

Kalium · Post by **Kalium** » Wed Dec 08, 2004 10:49 pm

There's already AVSEdit.

The thing is, a lot of the stuff is heavily dependant on the plugins. Unless you want to be generating most of the GUI on the fly by parsing documentation, you're probably screwed there, too.

jjamriska · Post by **jjamriska** » Thu Dec 09, 2004 12:04 am

i was going to set the plugins to work fro buttons in the gu, and have it generate the scriptinto a text box where it can be hand edited before writing it to the file- a good gui could support tn plugins using java popups- and the import plugins will be from a drop down box.- ill draw up a pic of the planned gui and post it for more info- this is just an idea since java is os independent...

rose4emily · Post by **rose4emily** » Thu Dec 09, 2004 12:18 am

Java may be platform independent, but AVISynth is, most unfortunately, not.

If you really want to get into using Java to edit video, I'm working on an app that handles the frames from scratch (by which I mean it does all of the processing and compositing within the Java code). It's more of a long-term project (I'm guessing 2-3 years before I'd call it a functionally complete "1.0" release) - but I will (in the near future) be opening the source for people who'd like to make use of or submit contributions to the codebase. That should be happening in about 10 weeks, after I've worked through the last of the architectural models, requirements documents, and the project management infrastructure.

The performance tests I've run so far (for things like populating and running mathematical operations on the in-memory frambuffers and repainting an AWT window using a custom implementation of ImageProducer) suggest that it can actually be every bit as quick the existing commercial and open-source video editing apps I've seen - and the design I'm using will be a hell of a lot more flexible to work with. All things considered, I think this might turn into a very slick application by the time I'm done with it.