Progress update...

Version 3.2 is a big update for Frameline, addressing 4 out of 5 of the main feature requests that we get. Top of the list are full finder behaviour and fully user customisable indexing, these are moving forward well, but have been a lot more complex than we first expected, so a bit of delay.

Look for version 3.2 some time in August, it will be worth the wait.

Safari 4 Beta & Esellerate update

We are still have problems with Esellerate when the Safari 4 Beta is installed. Currently it is not possible to activate, de-activate or purchase a license from within the application when Safari 4 Beta has been installed. The official response from Esellerate is as follows;

'Unfortunately, at this time we have not completely tested the eSellerate SDKs with Safari 4.0 since there hasn't yet been an official release and the product is still in beta. It's possible there might be problems with the Webkit components that could have issues with the eSellerate SDK, but which either Apple might correct or else perhaps we might have to adjust the SDK for in the future, when Safari 4.0 is released.'

Therefore, for the time being, to activate Frameline, it will be necessary to un-install the Safari 4 Beta. We will keep you posted when we have some more information on this issue.

Version 3.1 released

Very pleased to let you know that Version 3.1 of Frameline 47 is now available. A really solid update that adds a number of features and improvements. Many thanks to the team for all their hard work.

Additional Features of Version 3.1

• Network File Checkout/Locking
• Network Database Syncing
• Revised Application Preferences
• Drive Indexing Switch
• MPEG4 Re-encoding
• MPEG4 Capture Resolution
• JKL Support

Fixes and improvements in Version 3.1

• Improved Poster Frame Processing
• Improved start-up processing
• Updated file window
• Clip filter criteria updated
• Consolidate Improvement
• Updated and simplified Menu
• Minor bug fixes

Version 3.1 news

We are now testing the Beta of Version 3.1 - its a really nice update that addresses quite a few usability issues and adds some general polish. Our new network functionality is taking more testing than we expected, with different wireless combinations proving laborious. We also have new background database updating functionality that is proving tricky to test.

For these reasons we will be postponing release till the end of January/early February to make sure we have everything ironed out.

Seasons greetings one and all : )

Interface Gallery

We have just completed a set of interface screenshots and posted them up on flickr. We will also be using this gallery to put up a history of the interface; from early prototyping, through version one to the current release.

Back to work

After a well earned break the development team are now excited to be back to the project. First up is a small point release, 3.0.3 to fix a few bugs and usability niggles, and then we are on with two bigger updates 3.1, then 3.2, which add some powerful new features, including full Finder behavior.

My favorite new feature in 3.2 is the media filter which enables files to be found via combinations of criteria, ie: DV files that are less than 20 minutes that are un-tagged, or mono sorenson video files at 320x240, MPEG2 files over 2GB etc etc (I think you get the idea) When combined with the content filter, this will provide some incredible functionality.

After 3.2 we will fix the Notate window (which has been a little neglected of late) then move on to our full Leopard transition, leaving Tiger behind, but bringing in core-animation, a dynamic clip library, background encoding...etc....

Look for the next update to be here early in the new year.

Perian 1.1.1

Great to see that the 'swiss army knife' Quicktime plug-in Perian has been updated to 1.1.1

The previous version 1.1.0 had a few bugs that could crash Quicktime, particularly with some Flash Video files, and this caused us some trouble with Frameline's initial database scan which could crash when it encountered one of these files.

This problem prompted us to put up a dialogue at start-up to encourage users to deactivate Perian before continuing with installation. Pleased to report that with Perian 1.1.1, this is no longer an issue, so if you read this before first install (and are up to date) just click continue. In the next service release of Frameline (3.0.3) we will update the Perian warning dialogue accordingly.