Ableton Forum

continuous wrote:

db2 wrote:I have a friend who does very similar work. He uses just about every tool imaginable, but when it comes to his integrated audio/visual work he uses several max patches routed together controlling a couple of jitter patches (the max video object set). It's the perfect way to sync many parameters of your audio to video.

I know plenty of guys who use max and lots of other seemingly academic tools to compose their audio work, but who then use very simple tools to perform it, although they tend to have many more complex mappings then the average cat.

But when it comes to that very intimate and subtle audio to video connection, max/msp/jitter provides an extremely flexible environment.

Thanx for the info! I'm wondering how Max 4 Live will play out in regards to creating projects like this?

Well, Jitter is a pretty intense set of max objects letting you operate tons of video editing parameters and build all kinds of new tools/ways for interacting with live video. I'm assuming if you have max/msp/jitter it would be fairly easy to pass controllers into max/jitter from max for live, and assign those to jitter parameters to do some hardcore real time video manipulation, but its really the open nature of jitter that allows for extremely flexible routing/control over innovative video objects. I'm absolutely sure that there are other video suites that will allow you to control some video mixing parameters by sending out midi commands via IAC Bus or midi pipe or the like, but most of them aren't as in depth as the jitter set when it comes to video.

It's all about what you want to do. I'm sure that some very interesting results can be achieved with a much less complicated system. The joy of max is that it's all being developed in the same environment, so you don't have to think so much about what's controlling the audio as being different from whats controlling the video, just maybe some transformers to make the parameter ranges make sense.

What should be nice is that max for live will begin to encourage people of all different skill levels to experiment with different setups and begin to demonstrate what is possible with other programs as well, not strictly max/jitter.

db2 wrote:

continuous wrote:

db2 wrote:I have a friend who does very similar work. He uses just about every tool imaginable, but when it comes to his integrated audio/visual work he uses several max patches routed together controlling a couple of jitter patches (the max video object set). It's the perfect way to sync many parameters of your audio to video.

I know plenty of guys who use max and lots of other seemingly academic tools to compose their audio work, but who then use very simple tools to perform it, although they tend to have many more complex mappings then the average cat.

But when it comes to that very intimate and subtle audio to video connection, max/msp/jitter provides an extremely flexible environment.

Thanx for the info! I'm wondering how Max 4 Live will play out in regards to creating projects like this?

Well, Jitter is a pretty intense set of max objects letting you operate tons of video editing parameters and build all kinds of new tools/ways for interacting with live video. I'm assuming if you have max/msp/jitter it would be fairly easy to pass controllers into max/jitter from max for live, and assign those to jitter parameters to do some hardcore real time video manipulation, but its really the open nature of jitter that allows for extremely flexible routing/control over innovative video objects. I'm absolutely sure that there are other video suites that will allow you to control some video mixing parameters by sending out midi commands via IAC Bus or midi pipe or the like, but most of them aren't as in depth as the jitter set when it comes to video.

It's all about what you want to do. I'm sure that some very interesting results can be achieved with a much less complicated system. The joy of max is that it's all being developed in the same environment, so you don't have to think so much about what's controlling the audio as being different from whats controlling the video, just maybe some transformers to make the parameter ranges make sense.

What should be nice is that max for live will begin to encourage people of all different skill levels to experiment with different setups and begin to demonstrate what is possible with other programs as well, not strictly max/jitter.

Thanx for the info, feedback, and perspective. I've been messing with using the IAC bus to send midi over Lan to my Pbook (to Modul8 and Zwonull.MGFX) but realize that the results are pretty random. Most likely I will not get too deep in the max/jitter world. I'll be curious to see how the M4L stuff develops visually though!

cheers

i'd just hold off getting excited about jitter in mfl for a while:

It's likely that there will be some crippling of Jitter output while editing in Max for Live unless you own the Max/MSP/Jitter bundle.

http://www.cycling74.com/special/maxforlive