snapshots, mouse area and using osc lists - for the lemur

hey guys! im trying to create a modified version of aerobic for the lemur.
one of the hardest things im trying to come to grips with is the mouse area object.

the mouse area object is one of the most annoying objects around when it comes to osc. it would be great if there were a better osc solution out there for it, and frankly its a bit silly of NI to completely overlook osc implementation when creating such a central object in an instrument.

when a snapshot is saved with this object, does it save the parameters directly in this object, or somewhere else?

because if it does im pretty lost. what i want to do is take a 16 value multislider list from the lemur, and feed each of those values into the mouse area object.

the other part i need to figure out is how to output the values back to the lemur. but that shouldn't be quite as hard.

thanks very much if anyone else has some experience or advice to offer on this.

 

Hi queglay,

I dont know if this is what you looking for, take a look attachment.

This was my solution to get the values from new reaktor sequencers to my lemur.

It does work bidirectional, drawing on mouse area the values are send to lemur, drawing on lemur the values are send to reaktor.

Data is stored with snapshots, so your lemur should be updated by selecting another snapshot

I did learn some tips Mike Daliot ensembles to make it.

You will need to create a osc setting in reakor named "Lemur", let me know if does work

All the best

AB

 

it does work, and thats awesome. thanks for helping me out with that, itll b handy alot in the future.

this aerobic patch is one tough thing to understand though. i cant quite figure out where the snapshots are being stored for the multislider object. there are a few snapshot value objects around. and theres a snapshot module there i've found. but its hard to figure out what does what because the routing is so crazy.

ill have a play with that test equipment module and maybe the event watcher will help me out.

 

Multidisplays, polydisplays, and mouse areas do not store any information on their own.

The Snapshot module also does not store any information itself.

The Snap Value and Snap Value Array modules do store information, and are typically what you would use to store information from a custom gui component.

Event tables can also store information but not on a per-snapshot basis.

The stock GUI controls, knobs and so on, store their own state as well.

 

thanks for that info breakdown. man im finding reaktor a bit of a beast to deal with. im used to max msp, which i prefer for conceptualization and its osc implementation. but reaktor just cant be beat for all the amazing modules out there.
most of the good ones are pretty cpu hungry so i think im gonna have to start gigging with a quad instead of a laptop by the time im done.

 

Reaktor is a bit lower level than Max is, in that there are a handful of very simple, general modules which you put together to get the functionality you want, whereas Max has a more macro level design with modules that have more specific, complex behaviors.

Personally I prefer the Reaktor approach even for sequencers and things of that nature, I've tried building sequencers in Max and found it pretty ass backwards. Though it's irrelevant for me these days as I am moving to VSTLua instead for work that doesn't involve audio, which is most of what I do...

But, that's partly just what I am used to, and I imagine that someone going the other way would have similar feelings about Reaktor.

I hear you on the OSC also, think I recognize you from the jazzmutant forums... It can be a pain to deal with in Reaktor, depending on what you are trying to do, but there isn't much that's outright impossible.

In any case, it's not so bad once you understand how things work, but it will definitely take some getting used to. Please feel free to ask if you have any more questions.

 

your right there. i can get most of my functions working in standalone. my biggest problem is routing that audio back into ableton. wish rewire worked.

i wonder if there would be a way of sending an internal audio stream from reaktor standalone into a reaktor vst in ableton.

or if you could run a vst inside reaktor standalone, i could make a max pluggo that could send the audio stream back to ableton live.

 

we need osc in vst mode, that would solve alot of problems.

 

i've figured out an acceptable workaround for this for the time being.

you can run reaktor in standalone. i recieve midi syncy from ableotn in max. i then send an osc stream of the midi clock from max to reaktor standalone. i then replace the song position with an osc recieve.

that solves the midi clock sync problem in standalone. i then send the output from reaktor to outputs 3/4 on my fireface 800. using loop feedback mode i take the output of 3/4 into ableton. and there it is. you can take outputs from ableton, process them in reaktor standalone, use osc as well, and send them back into ableton.

 

interesting. i get the feeling my m-audio 410 may be able to do something simiolar to the fireface, as it has a software mixer with an auxilary system, but i could never be bothered to learn it.

 

worst case scenerio some might have to buy short cables just to patch the output back into the input. but be careful of feedback.