The file used for this was 06_soundAnalyzer.fla which combines the use of hype's oscillator behaviour and sound analyzer framework.
The file can be found at:
HYPE > examples > Flash > SoundAnalyzer > 06_soundAnalyzer.fla
By default, the framework matches its size to the stage. For this example the stage size has been set to 480px by 480px .
The object has been left as the default MySquare and the number of objects has been increased to 200.
var pool:ObjectPool = new ObjectPool(MySquare, 200);
The xStart, yStart, xSpacing and ySpacing for the GridLayout can all be left at default. Increase the number of columns to 50. If your stage is wider than 480px, the number of columns will need to be increased to fill the width of the stage.
var layout:GridLayout = new GridLayout(0, myHeight / 2, 10, 10, 50);
Adjust the var freq to 150. This will slightly slow the rate at which the squares fall.
var freq:int = 150;
The file already tracks the alpha and Y-scale of the object.
To make the object more transparent, change the last value used by the aTracker to .5.
In order to make the Y value scale less, change the last value of sTracker to 10.
Copy the sTracker code and paste it twice. For the first tracker, change sTracker to sxTracker and change the property it's tracking from 'scaleY' to 'scaleX'. Change the last value of the new sxTracker to 5.0. This causes the X-value of the object to change slightly as it falls, making the object appear 'softer'.
For the second tracker, change sTracker to szTracker and change the property it's tracking from 'scaleY' to 'scaleZ'. Change the last value of the new szTracker to 5.0. This causes the Z-value of the object to change slightly as it falls, adding some depth to the object. Instruct sx and sz to track the object.
var aTracker:FunctionTracker = new FunctionTracker(clip.myFill, "alpha", sa.getFrequencyRange, [i*4, i*4+4, .25, .50]);
var sTracker:FunctionTracker = new FunctionTracker(clip.myFill, "scaleY", sa.getFrequencyRange, [i*1, i*1+2, 0.5, 10.0]);
var sxTracker:FunctionTracker = new FunctionTracker(clip.myFill, "scaleX", sa.getFrequencyRange, [i*1, i*1+2, 0.5, 5.0]);
aTracker.start();
sTracker.start();
sxTracker.start();
The two biggest visual changes to the file come from altering the oscillator. First, 'Oscillator.sineWave' is changed to 'Oscillator.sawWave'. Change the min value to 0 and the max value to Math.random()*600. This forces the wave to start at the top of the stage and end well below it. Then, change i/(180/2) to i/(45/2).
var yOsc:Oscillator = new Oscillator(clip, "y", Oscillator.sawWave, freq, 0, Math.random()*600, i/(45/2));
yOsc.start();
As a last change, add a blur effect to the canvas.
import hype.extended.rhythm.FilterCanvasRhythm;
import hype.framework.core.TimeType;
var blur1:FilterCanvasRhythm = new FilterCanvasRhythm([new BlurFilter(1.5, 2.5, 1)], bmc);
blur1.start(TimeType.TIME, 1);
When a sound is played, the analyzer responds as expected. When no sound is played, the objects load and fall kind-of like rain, like so:
Hype sound exploration stuff: here!
As a warning, it's still not unloading properly - Click a lot it you want your computer to crash!
Visual representation of my blog:
Varoun uploaded our video assignment from last semester!
That class was so much fun. I miss our group!
Early in the semester we had an assignment to re-size Flash banners. While not particularly glamorous it was a good exercise for practicing re-sizing and seeing how fast it could be done, since realistically there is a lot of banner re-sizing in my future.
The banners were for Walk the Line. Prepare to be assaulted by floating heads!
So I was trying to figure out how to organize my images so I could upload them to Photobucket for placing them on my blog. I couldn't decide whether to link to them or slide-show them or just throw them out into the snow and let them fend for themselves.
I then realized. Hey, I have webspace - I can host my own stuff. Why am I using Photobucket?
Thankfully, the internet has the perfect meme for such a moment.
For our flash class we had to take code we'd learned and apply it to the creation of a Nissan-themed mini-site. We had to take code involving children and stages and apply it to the time-line version of the site that had been completed way back in week 6. My parents follow my blog. I just officially lost them. I may have lost myself. But the point is:
FLASH.
It's pretty. AND FLASHY. Click the image. :pUltimately, I understand how to apply what we learned to the creation of another site - which I suspect was the point.
**There are no actual attacking androids. yet.
These are the finished design for the Android app, there are only two shots of the app itself (one landscape and one portrait) but my hope is that (with the possible aid of the site map) how it's intended to work is clear.
Group projects. You win some, you lose some.
Throughout the term we had group project to redesign and apply basic code to a website called Cr(eight)iv - the actual name using the numeral 8, not (eight), but it was requested by the client that we not use their actual name so as to not divert search engine attention from them.
The first part of the assignment as to develop three potential designs for the site.
The three designs I came up with were:I used the third design, admittedly because it was the easiest to slice for coding. I really wasn't sure if I could successfully code something more complicated - though now I am confident that I can. The coded bit can be found here. It's honestly really basic stuff - but it works and I'm proud of myself for getting it done.
This project involved a lot of frustration. There were basically 'group issues' plaguing the entire class - likely stemming from the fact that this was one of the first group situations where we didn't have control over who was in our group. Thankfully it's done now, and the Eros project renewed my faith in group-work. :D
We had a group project to create a website mock-up and the branding for an imaginary Tea-house called Eros. As a client they wanted a site that focused on their booming teas and had a Telus or Apple type feel to it.
My initial idea for the design was along the lines of this:The problem was that, although the picture in the background was nice, the site was becoming far too busy and cluttered when the client was looking for clean and simple.
Not to be discouraged, I took the design concept that my super awesome partner, Enoch, had been working with and started modifying that.This was my final design for the site. I like it because it represents what a group collaboration should be - by working together we came up with a design that neither of us would have reached as quickly on our own and neither of us felt hindered by the other during the process. It's nice to have someone next to you while working that has the honesty and interest to look at the hideous green line your about to apply to an object and say "... you do know how tacky that looks, right?".
Oh puns, how much better the world would be without you...
For most of the semester, we started off our pre-production class with warm-up sketching. We had to submit our ten favourite sketches for marking.
I've never taken any classic art courses, so anything involving theory like perspective, or bone/muscle structure was exciting for me. Drawing stickfigues that could potentially be the foundation for a person instead of my usually foundation for a treant (spell check doesn't recognize treant or ent? For shame.) was also thrilling.
My favourite sketches are those that look passably male. Where to even begin drawing men generally confuses me. The hips that aren't hips, the lack of curves but still needing to have shape. Even when drawing while young I'd reach a point of frustration and just make it female.
When in doubt, throw boobs on it.
So, yes, drawing an almost male thing is a triumphant moment.
The revised versions of DyStar and NCC. 
