Slideshow conversion Via On2 Tech Flix Pro (Flash 8)
Notes on On2 Technologies Flix Pro - the good and bad of it in my experience:
With a little help from many testers across the web I've finally got a demo working correctly using Flix Pro. The original slideshow test file was created with a PC and ProShow Gold. The file was output as an MPG then converted via Flix Pro to a Flash 8 FLV movie at 640x480 screen display size and a 512K bps bitrate with audio.
The up side of Flix Pro with Flash 8 is that it produces a very good quality video at very low bitrates vis a vis earlier Flash implementations. Formerly I used Riva Producer Lite to create similar quality output but it took nearly three times the bitrate and four times the file size to create similar quality. This made web play quite problematic. The Flash 8 implementation is very good with VP-6.
The Flix Pro user interface is fairly easy to understand, but there are some serious "niggles" about it which need attention in later revisions. In order to use Flash 8 the "client" side (the viewer over the web) must have the Flash 8 player installed on their computer. So to avoid issues a Flash Detection pop-up is desired. The Flix Pro software can create this, but unfortunately only for an SWF export. Obviously, with the 16,000 frames per instance limitation of SWF and the issues with syncing video beyond two minutes, most who produce video slideshows will prefer the progressive or "spooling" advantages of FLV as well as the ability to keep sound perfectly in sync throughout. So FLV export is a very important feature of Flix Pro.
The only way I could figure out a way to export the Flash Detection pop-up html file was to create a "dummy" SWF export with the same file names and player dimensions as the FLV export. Then erase the "dummy" SWF and port the created Flash Detection pop-up to the web along with the SWF shell for the FLV player. This is a rather "kludge" way IMHO and On2 Technologies needs to remedy this. Only a few lines of code would be necessary to "fix" this in their software. I found their technical support to be very willing to help, but not terribly proficient at explaining this issue which I had to dope out on my own primarily by trial and error.
The Flash Detection pop-up contains Java code which first determines whether the client side computer has the proper Flash implementation then either provides a rather cryptic "Flash Required" link which ports the browser to the Macromedia site for Flash 8 download or launches the SWF shell which in turn launches the FLV movie. There are a couple issues with this. First, it assumes that the client has Java enabled. Not necessarily a valid assumption. Then rather than providing an elegant explanation about what needs to be done (install a proper Flash player) - it simply leaves the visitor looking a very cryptic "Flash Required" text message which also proves to be the link. This could use some serious revision.....
There are many features and if one purchases the additional Powerplayer 8 players it's possible to customize some of them with you own "logo" by including a small SWF file which must be named "playerlogo.swf" On the example link provided, you will see the text "Lin Evans Photography" across the top of the player which was created with Wild FX Pro and saved as "playerlogo.swf". Just toss it in the same folder on your web site with the other files and all players having an "L" in the player name will pick it up and place it on the top left of your player. It can be text or a small "logo" or both I suppose.
Flix Pro also allows the user to implement optional preload buffering. This allows a selected percentage of the file to download before the movie begins and helps those with less bandwidth see better quality movies with greater bandwidth than would normally be possible. My sample uses 10% preload so that the client sees a "percent loaded" text until 10% of the file has been captured then spooling begins.
Click the link below to see the sample. This one has been tested on multiple PC's and MacIntosh systems and on a number of different browsers and seems to be pretty stable. The small amount of "jerkiness" you see when the first image scrolls to the right (from the body to the head of the jewelry bear) was in the original and not an artifact of the Flash implementation. Also a bit of jerkiness in the fast zoom out of the strawberry scene was part of the original. A bit of flicker on highly detailed images in pulse sync with the key frame about every three seconds is also normal and can't be avoided as far as I know. All in all a pretty nice improvement over earlier Flash implementations with excellent quality at lower bitrates and very good compression.
It's not so much bad documentation. New features in flash (ie. components) always tend to border on bloatware at first. They could have made them much easier. The FMP plugin is proof of that.
Great examples dudeqwerty, any chance of you posting where you learned that stuff or are you self taught?
jAQUAN, im self taught and always have been, cant stand people trying to teach me their way of doing things.
as for the filters, the documentation is a little thin, but all you need is there, all you have to do is to apply some creativity. something which i find difficult myself.
the main part of the script is a modification of the bitwise left shift operator (<<)
it works like this:
Code:
function bitwiseLeftShift(a, b) {
return int(a/(.5/b));
}
i modified it to:
Code:
function pixelShift(a, b) {
return int(a/(b/1));
}
the reason i used this method ( apart from the fact i dont know any other image resizing algorithms, yet ) is i was playing around with setPixel and i realised if you <<'d the pixels by one it would down scale the image by 2^n.
so i made a little trace table of different values <<'d by 1, 2, 3..... then i worked out the formula from there.
will probably be usfull to some ppl,
zlatan
p.s. with bigger images like the one in the example, a scale factor of more than 3 will crash most ppl machines
Last edited by dudeqwerty; 06-15-2006 at 03:52 PM.
the displacment filter map works with colour values, bluey colours shift the pixels up, greeny colours shift the pixels left, redish purple right and yellowy browns down,
if you go on the original liquify tool link i posted up, if you press "s" it will show you the colours you are drawing on a buffer bitmap with supply the colour data for the displacment filter. (press "h" to hide it again)
so its just a matter of getting flash to "draw" the right colours according to mouse movement.
the displacment filter map works with colour values, bluey colours shift the pixels up, greeny colours shift the pixels left, redish purple right and yellowy browns down
That sentence alone probably saved me a couple hours of trial and error.
I have been trying to get your "LIQUIFY.as" to function but cannot.
I downloaded the ZIP file and placed your AS CODE in a '.AS' file called "LiquifyFilter.as" but it doesn't work . . .can you send along some advice.
for each example you need to have the images in the library in the form of movieClips they should have the linkage names of "pic1" "pic2" "pic3" ...
the red part of the code is what you edit, it is the value for the slide length of your pictures, so if your pics are 200x200 px you change it to 200.
steve1312, this is because the class path is not correct as you arent putting the class in the right place, look in flash's help files about class paths, if you still cant get it to work come back here and i'll sort if for ya
zlatan
sorry about the 2 part post, didnt let me post it as one
hi
have you got any examples of how to get a movie clip button to stop on its rollover state after being pressed then go back to its up state after pressing another button
heres an example http://www.visiondigitalstudio.com/1/
thanks