[Max for Live] what will be the first device you'll build ?

Geezus · Post by **Geezus** » Wed Jan 28, 2009 10:05 pm

I've been trying to run a bunch of jitter patches in MAX to see whats up and it appears that most things require OpenGL drivers to make it work. unfortunately for me, I own a stock integrated Intel graphics card on a business laptop, so jitter is pretty much useless to me. So bummed

Machinate · Post by **Machinate** » Wed Jan 28, 2009 10:10 pm

You can "run Jitter" on any laptop, just not too many of the jit.gl.* family of openGL things. "Most" things don't require openGL to work, some do, some don't.

Question is more; what would you like to achieve?

Geezus · Post by **Geezus** » Wed Jan 28, 2009 10:14 pm

Machinate wrote:You can "run Jitter" on any laptop, just not too many of the jit.gl.* family of openGL things. "Most" things don't require openGL to work, some do, some don't.

Question is more; what would you like to achieve?

i dont know enough about graphics to really answer that question. Ideally it would be a hybrid of video triggering/cuts and real-time image synthesis (no doubt requiring OpenGL) combined with whatever effects and manipulation you add on top of that output. I have MAX but haven't had time to learn it so I'm not even "going there" as far as jitter is concerned, so I was trying out the jitter cookbook examples just to see what was up (there are very few examples I can find of jitter in action) and not many of them worked on my machine. Kept getting "cannot blah blah OpenGL blah blah" messages

mdk · Post by **mdk** » Wed Jan 28, 2009 10:18 pm

The first thing i'll build is a recording offset fixer.

either by putting an MfL device before the plugin, using max to capture the midi and creating a clip direct from max. or use max to fix the recorded data afterwards.

and the same for audio.

that is until they give in and add an option to 'record what you play'

Patch · Post by **Patch** » Wed Jan 28, 2009 11:17 pm

friend_kami · Post by **friend_kami** » Thu Jan 29, 2009 7:37 am

Machinate wrote:
friend_kami wrote:
Tone Deft wrote: absolutely and very simple to do.

for anyone who hasn't used max/msp before I can GUARANTEE you that it's easier to use than you've been lead to believe.

this with the 5.0 release of max/msp is an amazing turn of events. with jitter included, zomfg.
just curious as to how much i need to put my os on adiet in order to run jitter and live as one single device. seems to me that jitter+live would use a hell of alot of cpu, regardless of how good you patch.
How so? Most of the Jitter patches I run use very little CPU at all... perhaps you're talking about traditional "VJ" type things? In that case you'd be happy to know that Jitter can do processing on the GPU, including mixing, keying, all that stuff.

even when running through live?

friend_kami · Post by **friend_kami** » Thu Jan 29, 2009 7:40 am

mdk wrote:The first thing i'll build is a recording offset fixer.

either by putting an MfL device before the plugin, using max to capture the midi and creating a clip direct from max. or use max to fix the recorded data afterwards.

and the same for audio.

that is until they give in and add an option to 'record what you play'

when/if you do, mind sharing that?

mdk · Post by **mdk** » Thu Jan 29, 2009 8:36 am

friend_kami wrote:when/if you do, mind sharing that?

no problem. i'll be sharing everything. im an open source kind of guy

friend_kami · Post by **friend_kami** » Fri Jan 30, 2009 8:24 am

mdk wrote:
friend_kami wrote:when/if you do, mind sharing that?
no problem. i'll be sharing everything. im an open source kind of guy

just wish that i can figure out something neat to give back then eh.
heh.

xh9o · Post by **xh9o** » Fri Jan 30, 2009 2:45 pm

Tone Deft wrote:
radib wrote:if its possible then some kind of pipeline, to connect midi parameters. say: IF parameter "frequency" of "device 63" > 87 THEN parameter "osc1 level" of "device 02" = "vca level" of "device 08" x 0.075 x tempo.
absolutely and very simple to do.

for anyone who hasn't used max/msp before I can GUARANTEE you that it's easier to use than you've been lead to believe.

well then this will increase the "no time" problem.