I really want to use your libraries to build a player that can do a frame by frame seek… using flash…
maybe to much to ask

Thanks again for your help

if there is an analogous way to segment sound using flash?

So I tried a fix by adding new paths to my AS3.0 preferences:
“$(AppConfig)/Component Source/ActionScript 3.0/User Interface”

No luck… any ideas? thanks

Magnus’s last blog post..EMUG Meetings in Abu Dhabi?

Your solution for sampling color is so much more graceful and simpler than mine - I can’t wait to implement it and observe the performance increases. I really do appreciate you taking the time to share this method as it definitely made this article much, much better.

For example:

(1) Play a video (or set up any bitmap data provider)

(2) ‘Mosaic’ it… down-sample it into a bitmap data… this can either be done by (a) using a single bitmap data as a single buffer to capture the video into, scaling to fit the buffer during capture or (b) using 2 bitmap datas as a double buffer where the initial capture is unscaled, then is copied to a second bitmap (scaling prior to or during this second step).

(2a) Duplicate the video into a bitmap data whose size maps 1 pixel to each ‘region’ being captured. For example a 320 x 240 video source with ‘10 rows’ and ‘20 columns’ would be captured into a bitmap that is 32 x 12 pixels. Use a matrix transform to scale with the draw() method to scale the source to the output resolution during capture. You can apply smoothing as desired (depending on what sort of interpolation you want).

(2b) Duplicate the video into a bitmap data whose size matches the source (using draw()). Then either:

(2b1) nest that bitmap (buffer#1) into a parent object, then draw() the parent object into a lower resolution bitmap (buffer#2). This should get around having to bother with a matrix transform of any sort during the draw() step since you are drawing from a parent’s display space (so the scaled-down child data is captured in its scaled-down form vs. its unscaled form).

(2b2) copyPixels() that bitmap (buffer#1) into a lower resolution bitmap (buffer#2), using a matrix transformation to reduce the resolution during the copyPixels() operation. You can also decide whether you want to selectively mess with channels in this step.

(3) Once you essentially have a low-resolution bitmap of the original video (where flash has done the interpolation for you) you can then quickly traverse the low-resolution data to get a given sample regions average value (and in turn can look at that sample’s color as RGB, HSV or whatever else).

In this scenario instead of having an object for every slice you’d basically have a buffer (a bunch of pixel data where each pixel represents a sample region’s average value), and some utility methods for using the buffer’s data. You could still then allocate an object acting as a view for each sample - whereby the buffer is basically the model data provided to that view. You could just set an update() method on the view that gets passed the new buffer’s value when it is updated (so for each sample period you dispatch or notify the views that the buffer data has changed, passing them or referencing them their region’s pixel ‘value’).

Maybe I only took a fast look at your code - it looked quite good, and well-written. Where when you ’sample’ you are actually performing an average on each region by going through each pixel of the region (and keeping each pixel’s RGB in a sample set). This step you don’t need, since you can arrive at an average pretty efficiently just relying on flash to down-sample the region for you (and you can define from a few common interpolation methods — linear = no smoothing, bilinear = smoothing). Once you have the average you can easily compute HSV/brightness/etc. using external utility methods vs. methods on the object/data itself (the rgb2hsv, hex2rgb, etc. color space methods can certainly be static, and/or external to the samples themselves).

Another advantage to this hack is that you can use common Bitmap filters and transformations that flash applies (fast) to manipulate the downsampled buffer data (increase contrast, invert values, blur it, edge contrast it, etc.).

Hope you find this useful!…
N