It’s always nice to see the continuing evolution (about screen is cool, too). I know this is probably your least favorite question, but when do you expect to have a functional beta? Several weeks, couple months, early next year, etc?

I didn’t know about Monotheka. It works really well for me as I always have hard time remebering who I lent my DVDs. Thanks for all your hacking.

Hey.. diva looks really interesting. I’ll look into the code and try to help out as soon I find a way to :) If you are interested I would like to join the project, but it may take some time to get into everything..

• gaute

Thanks for posting regularly and keeping us future users interested! I am really looking forward to the initial release (more so than any of your competitors). GOOD WORK!

Nice, as always! I really like the idea of the startup dialog. I’m somewhat of a spatial-zealot, so I’d prefer every document window to be directly mapped to a data file on disc. But this always left me with the question what to do if the user starts the application directly. I might just nick your idea for that case in my software. It would be great if you could also support some document oriented properties, like storing settings and window state for each project separately.

Looking really great… I’ve been looking for a simple video editor in Linux similar to iMovie… It looks like you’re filling that gap perfectly, keep up the good work.

@gaute: Sure I’m interested, you’re welcome! The whole thing might look a bit messy right now, but I’m slowly cleaning it. I’m writing some docu now that describes the yet-to-be API, etc. so this will be helpfull.

@Jake Well… that depends on others joining the project. I could release “something” even now, but it will take some time to have “something that works”. The biggest amount of work need to go in to the invisible, boring things – the API/System.

@ Daniel The nice thing is that the splash “transforms” into the welcome dialog. That’s pretty nifty. Don’t waste your windows – recycle them :>

Yeah, that’s what I thought. My first reaction was “eek, a splash screen”, but then I got the idea and I think it’s great. :)

Some small remarks on avisynth 3.0 Avisynth 3.0 uses stlport, boost and freetype. stlport compiles fine with freebsd and solaris Boost compiles fine with solaris. I don’t know for freebsd freetype comiles fine on solaris and freebsd.

I have only tested avs3 on linux, but I think that there is not big problems on solaris. Maybe on freebsd because of boost.

Avisynth may accept all type of input. It suffices to include to plugins that does this job.

For the assembler stuff, if you want fast computations, you have to use it. Nevertheless, in avisynth 3.0, there is always a C++ version of the plugins.

The build filters in avisynth follows always the same rules. Basically, you have a template for yuor filter and you fill your code in it.

I didn’t know your program. I think i’ll give it a try.

regards

Vincent Torri

Seems you came through the slashdotting relatively unscathed - great! I’ve been keeping an eye on this project for a while now, haven’t done much as I’ve been in the process of moving things around since the hurricane shook things up.

I haven’t done anything with avisynth since it was 2.5, and once I made the shift to linux I must say I was missing it greatly. I even dabbled with wine as a way to bring it into my linux desktop. But then I figured out the combination of mplayer and imagemagick combined with any shell script and any other rendering tools you like, and I realized this is what I wanted avisynth to be the whole time I was hacking together its early compisting features.

Can you suggest some reference materials on gstreamer so one might hit the ground running? This looks like a very interesting project.