Midi controller for demos?
category: general [glöplog]
um.. well maybe not a GBA, but a DS at least :P
It works for GBA as well, it just have to be an EMULATED machine (ask skrebbel for details) ;)
I seem to remember Navis/ASD used his mousewheel as a granular source for increasing/decreasing complexity on-screen.
i used a midi controller for a few demos, in one for tweaking parameteres, and in two others for realtime parameter input
I also used a controller (evolution UC33) for an audiovisual performance, just filtering the 7-bit values to obtain smooth control parameters.
Those korg nano things seem very handy, btw...
Those korg nano things seem very handy, btw...
This is really interesting. It so happens that I'm working on tracker to sync demos via network/serial connections right now. For Texas, and groups who have done this before, how is it your handling large amounts of data? For instance model data. I was thinking about having a tracker command called "lump load" that passes data to an effect. Also I was thinking about having four cameras that spline around that you set-up keyframes for in the tracker, which effects then can use if they want too. I'm so so curious (:
Quote:
Those korg nano things seem very handy, btw...
they dont just seem <3
sigflup: We don't. Handling non-sync data is not a job for the sync-system. If you want to save yourself some work you can download GNU Rocket, the sync-system used by (among others) Texas and Elevated, from http://rocket.sf.net
I think I'll stick to what I'm doing because of the effort I've already put into it. GNU rocket? how strange, I wonder who the first scener to pick up this was...
Yeah - the Korg Nano Kontrol is excellent. The NanoPad is a bit shit - over-sensitive pads and a crap X/Y, while the NanoKey is totally shit for everyone except one-finger-jockeys who've never played a real piano.
I just got a Kaoss Pad 3 (for music, mainly), which has loads of very nice control features on its 8x8-LED touchscreen...including tap/clock-slave/autodetect BPM and motion recording. I haven't done visuals with it, but I bet it would be great for experimenting with touchpad swooshes which you can loop in sync with your video/demo and then adjust slightly on the fly.
I'm investigating whether I can switch between CC layouts so that I could, for instance, go from an eight-row vertical touch fader surface to an X/Y surface, to a horizontal 'centre-to-sides' (or panning) surface, etc.
Okay, it's MIDI and not OSC, but it's begging to be taken advantage of. The OSC weapon of choice at the moment is the monome, but it's buttons all the way; no knobs. (However, someone's done a Processing sketch that lets you operate Max/MSP patches designed for monome with a KP3 \o/).
By the way, in case anyone's interested, the Korg video Kaoss Pad was a bit shit - 95% crap effects, and just a fancy video mixer. Not intended for realtime heroes, clearly.
I just got a Kaoss Pad 3 (for music, mainly), which has loads of very nice control features on its 8x8-LED touchscreen...including tap/clock-slave/autodetect BPM and motion recording. I haven't done visuals with it, but I bet it would be great for experimenting with touchpad swooshes which you can loop in sync with your video/demo and then adjust slightly on the fly.
I'm investigating whether I can switch between CC layouts so that I could, for instance, go from an eight-row vertical touch fader surface to an X/Y surface, to a horizontal 'centre-to-sides' (or panning) surface, etc.
Okay, it's MIDI and not OSC, but it's begging to be taken advantage of. The OSC weapon of choice at the moment is the monome, but it's buttons all the way; no knobs. (However, someone's done a Processing sketch that lets you operate Max/MSP patches designed for monome with a KP3 \o/).
By the way, in case anyone's interested, the Korg video Kaoss Pad was a bit shit - 95% crap effects, and just a fancy video mixer. Not intended for realtime heroes, clearly.
the midi-controllier option is an old idea anyway, im sure it can be usefull for some ppl. i havent got the time around to code such a thing, ive got too many other projects taking time. but its definitively something worth implementing in a system.
here's the few lines of code needed for tracking MIDI CC's if anyone's interested
Gargaj: cool
Cheers gargaj!
just to add to this useful thread. some of you might want to look into TimelinerSA. It's using modern OSC an IP/UDP rather than MIDI. designed for VVVV (Max/SP type app) but i have sucessfully used it for a Processing project and it works very well.
i'm guessing it works similarly to GNU Rocket, but with an awesome interface making use of bezier splines to control vaeriables, etc.. ;)
i'm guessing it works similarly to GNU Rocket, but with an awesome interface making use of bezier splines to control vaeriables, etc.. ;)
sigflup: GNU Rocket is made primarily by me (but with some help from Skrebbel, and input from a lot of other coders), based on Skrebbel's older synctracker. It has nothing to do with the GNU project, the name is pretty much a crappy joke ;)
rtype: Cool. But after testing TimelinerSA a bit - those are not bezier splines. What they call "cubic" is pretty much the same thing as is called cosine/smooth in GNU Rocket (they probably use a smoothstep function, something I've been planning to replace the cosine-thing in GNU Rocket with).
I played around a bit with it, and the interface has some neat features, some features I'm a bit on the fence about, and lacks some features that make it pretty much useless for me:
+ You can position two keyframes on the same position, giving a jump without having to have a single row with a step-key. GNU Rocket can't do this - you'll have to have high row-rate, and "no one will notice the glitch" :P
+ Timed text support. Very cool.
+ Color support. This is something I've been thinking of adding (through convention, but with some helpers) in GNU Rocket.
? Timeline jumping. I just find this concept too confusing to be able to use.
- Generally confusing interface. I guess this could be said about GNU Rocket as well, but at least GNU Rocket doesn't have a lot of buttons with only one letter on it.
- No undo support. Seriously, that blows.
- Time units are seconds only. That's just crazy if you're synchronizing with music.
- Lots of annoying redraw-bugs.
Whoa. I'm becoming Optimus.
rtype: Cool. But after testing TimelinerSA a bit - those are not bezier splines. What they call "cubic" is pretty much the same thing as is called cosine/smooth in GNU Rocket (they probably use a smoothstep function, something I've been planning to replace the cosine-thing in GNU Rocket with).
I played around a bit with it, and the interface has some neat features, some features I'm a bit on the fence about, and lacks some features that make it pretty much useless for me:
+ You can position two keyframes on the same position, giving a jump without having to have a single row with a step-key. GNU Rocket can't do this - you'll have to have high row-rate, and "no one will notice the glitch" :P
+ Timed text support. Very cool.
+ Color support. This is something I've been thinking of adding (through convention, but with some helpers) in GNU Rocket.
? Timeline jumping. I just find this concept too confusing to be able to use.
- Generally confusing interface. I guess this could be said about GNU Rocket as well, but at least GNU Rocket doesn't have a lot of buttons with only one letter on it.
- No undo support. Seriously, that blows.
- Time units are seconds only. That's just crazy if you're synchronizing with music.
- Lots of annoying redraw-bugs.
Whoa. I'm becoming Optimus.
urgh that timelinerSA... nodebased editors are crap as soon as the # of nodes exceeds 10.
Maali: TimelinerSA isn't a node-based editor. I guess you followed the screenshots-link to the main vvvv-site :)
I have tried TimelinerSA a few minutes. It looks useful!
I didn't expect to find something perfect for my needs (actually, I started writing my own thing), but this seems quite close to what I want. The good thing is it's open-source and written in C#, so I think I'll try to improve/adapt it.
Time is a floating point value, so it's fine for music sync. Interface should be easy to improve (remove those stupid buttons and use friendly menus). Colours and string support is exactly what I wanted.
Thanks button/kusma!
I didn't expect to find something perfect for my needs (actually, I started writing my own thing), but this seems quite close to what I want. The good thing is it's open-source and written in C#, so I think I'll try to improve/adapt it.
Time is a floating point value, so it's fine for music sync. Interface should be easy to improve (remove those stupid buttons and use friendly menus). Colours and string support is exactly what I wanted.
Thanks button/kusma!
Quote:
the NanoKey is totally shit for everyone except one-finger-jockeys who've never played a real piano.
You're being way too kind about the NanoKey -it's absolutely worthless and only serves as an example how not to make cheap USB piano keys. The NanoPad is remotely okay for a spot of coarse button mashing -I got my money's worth out of it.
Gargaj: you happen to know if theres a midi message to poll controller-status instead of waiting for changes?
I don't think so, I'd assume most MIDI controllers are write-only.
Wonder if anybody heard about the monome arc?
(well, I know, it's not MIDI but still...)