Where should i start?

category: code [glöplog]

@p01: your answer is absolutely not stupid :D

thank a lot!

added on the 2012-02-02 14:49:32 by rez

I love how rez just figures this out by trying. It's completely the attitude that this thread is about. You can get all into the understanding things business, but if you can do something cool even though you don't get half of it, that's just fine too. No probs if the understanding comes after the results instead of before. That's the fun of democoding as opposed to, say, most decent professional programming.

added on the 2012-02-02 15:38:31 by skrebbel

rez: seconds are bad, get the bpm and convert it to beats instead. Then add white screen flashes!

added on the 2012-02-02 16:08:21 by psonice

@psonice: yes, I already did that, I converted the seconds into "measure" (kind of pattern/line) for teh synchros :)

added on the 2012-02-02 16:24:24 by rez

@skrebbel: that's my process of creation for everything, 90% of my effects are found by repeating thousands times "try / fail / try / fail / try / how that looks cool / let's continue on that / try / etc..." :D

added on the 2012-02-02 16:26:59 by rez

In terms of syncing, don't just look at a visual representation of the music, listen to it as well. As I always do, I'll champion GNU Rocket for syncing. It's been used for 4k and 64k intros as well as a shitload of demos, so give it a try. Introductionary article: http://www.displayhack.org/2011/syncing-your-real-time-graphics-right/
Example secret trick:

Quote:

One example (here goes one of my secret tricks :) I can give is with bass. If you stand in front of a big PA-system and some heavy bass plays, your natural instinct will be to close your eyes, or at least, that they contract a bit. In the past, I’ve played with this by syncing a slight black screenfade to places in the music (or ambience) where there are a lot of low frequencies. The effect is almost never noticable, but it really helps to build the effect you want.

added on the 2012-02-02 17:47:34 by gloom

gloom: Good one :)

Reminds me of something we did back in 2000 (fr-06): The white flashes were actually a white flash and a "black flash" that's fading out slower right behind it (layer-wise). That way the image went from white to darker to normal, just as if your eyes had to adjust even more to the change in brightness. That made the flash stand out quite more :)

(Funny thing is that I got this trick from Skaven who used it aurally in the Second Reality end part - right after the steep attack of a note, lower the volume a bit and then let it get back up to normal. Makes things fake-louder :))

added on the 2012-02-02 18:10:01 by kb_

To quote Castlevania: "I'm interesteed in this"

Thank you gentlemen. More tips like those please :)

added on the 2012-02-02 18:16:55 by superplek

kb: Yeah, I've done that as well -- really effective. :) While we're on the subject of flashes/music/sync, here's another tip: if you sync to something in the music, like a crash symbal, make sure to time the fadeout of the flash to the actual audible length of the sound as well -- it makes all the difference when tying something visual to something audible. Every time I hear a crash cymbal in a demo and see the flash either fade out very quickly or veeeery slowly, I always cringe, because I know that the only thing they thought about while syncing was when to trigger the flash, not _how_, which is equally important.

added on the 2012-02-02 18:20:48 by gloom

I think it's hilarious that this thread got good. Who knew.

added on the 2012-02-02 18:45:01 by ferris