Announcement: OSCulator 2.5

[Clearscreen]

I tried to use it with the Wiimote and Live, but couldn't figure it out and got distracted with other stuff. I'd like to take a look at it again. What are other people clamoring for OSC in Live for, I wonder . . .

That's what i would like to know. No OSC support seems to be at a lot of people's deal breaker list only dwarfed by it's second cousin, no automation support past the 128th parameter.

If you have never used OSC its kinda hard to realize how you can use it...Way diff than MIDI. Think of the fct that MIDI is one Byte at a time and OSC is sent Via Network Packets...

With OSC you could easily find out the name of the selected clip on the track named BasZ_FarT... Then you could ask if there is a clip next to it... You could also ask how many bars the clip next to it is... What is its Time sig...Are its transients on point ( OK thats a pretty good OSC Implementation ).

With OSC you can Find a parameter named Yum Yum and tell it to go from 0 to 123987 over a course of 64 bars...

In this thread someone mentioned a monome. With a monome all you have to do is send it a /clear messsage...
and all its lights will go out...
With MIDI you would have to tell each and every light to go out...Not the end of the world but you can see there is a better, more modern way...

I think its awesome that peeps like Camille Troillard are promoting ( and doing really cool stuff ) with OSC but until big companies realize that many requested things can easily be done with a nice OSC implementation ( or a Scripting or OO Lang Implementation , or the fact that MIDI is just not cutting it anymore, OSC will just be a Taboo type of witchcraft...

+1. definitely hats off to the OSCulator people (even though it's OSX only and i can't use it...)!! all we need is a good OSC implementation in one major software (nudge nudge ableton...) and it'll take off...

[Michael Hatsis]

That's what i would like to know. No OSC support seems to be at a lot of people's deal breaker list only dwarfed by it's second cousin, no automation support past the 128th parameter.

If you have never used OSC its kinda hard to realize how you can use it...Way diff than MIDI. Think of the fct that MIDI is one Byte at a time and OSC is sent Via Network Packets...

With OSC you could easily find out the name of the selected clip on the track named BasZ_FarT... Then you could ask if there is a clip next to it... You could also ask how many bars the clip next to it is... What is its Time sig...Are its transients on point ( OK thats a pretty good OSC Implementation ).

With OSC you can Find a parameter named Yum Yum and tell it to go from 0 to 123987 over a course of 64 bars...

In this thread someone mentioned a monome. With a monome all you have to do is send it a /clear messsage...
and all its lights will go out...
With MIDI you would have to tell each and every light to go out...Not the end of the world but you can see there is a better, more modern way...

I think its awesome that peeps like Camille Troillard are promoting ( and doing really cool stuff ) with OSC but until big companies realize that many requested things can easily be done with a nice OSC implementation ( or a Scripting or OO Lang Implementation , or the fact that MIDI is just not cutting it anymore, OSC will just be a Taboo type of witchcraft...

+1. definitely hats off to the OSCulator people (even though it's OSX only and i can't use it...)!! all we need is a good OSC implementation in one major software (nudge nudge ableton...) and it'll take off...

Actually, most of the things i mentioned here can pretty much be done with a nice SYSEX Implementation using 14bit MIDI...But it wouldn't be as easy to read or use Like OSC messages...No Latency with OSC either...

[Lazos]

You are right, beats me. Wiimote control is about as exciting as watching your friend play a video game. I realized I have more fun manipulating a filter cutoff and resonance with my laptop mousepad! I think I'm sticking to looping my real acoustic instruments and saying fuck all these attempts to make nerdy computer music look cooler on stage. And I would much rather watch milk being drank with a fork than watching someone launch clips with their car alarm remote . . .

good for you..

Sorry, didn't mean to irritate. Just figuring out what works for me. I think the wiimote could make a great interactive tool, really, depending on how one uses it. And Osculator looks fabulous, btw. Great work! I want to learn more about OSC.

[G.]

really great soft !!!

i tested it and used it with live and max/msp, but :

- when i map my wii data to midi channels, it's really hard to assign ONE of them to a live control since there are continuously data coming from the wiimote and going to live over the midi port... i have to enable only one parameter and press command+m in live to assign it, then coming back to osculator, enabling only one other parameter, going back to live, etc... not very handy... lets say very long to do...

-in the wimmote namespace, i can see an /wii/1/ir/xys (or something like that, i've no wiimote connected right now), ok x is x, y is y, and i guess s is the size, which can be used to evaluate the distance between my ir source and the wiimote. but this damned "s" stay constant, whatever i do...

any ideas?


g

[Clearscreen]

Actually, most of the things i mentioned here can pretty much be done with a nice SYSEX Implementation using 14bit MIDI...But it wouldn't be as easy to read or use Like OSC messages...No Latency with OSC either...

really? can sysex send you arbitrary track names? hmmm... i know mackie control can do 'some' of this, but i wouldn't have thought it could do all of it...

[Michael Hatsis]

Actually, most of the things i mentioned here can pretty much be done with a nice SYSEX Implementation using 14bit MIDI...But it wouldn't be as easy to read or use Like OSC messages...No Latency with OSC either...

really? can sysex send you arbitrary track names? hmmm... i know mackie control can do 'some' of this, but i wouldn't have thought it could do all of it...

Sure, thats actually how mackie control is set up with SYSEX to get track names effect names, Rack names... I dont actually think that you can get clip names via mackie control ( id love to be wong here ), but ive never tried. But thats just a limitation of mackie's SYSEX implementation, if they wanted to they could do this via SYSEX...

SYSEX is pretty powerful, just a pain in the rump to read...

[tuscland]

really great soft !!!

i tested it and used it with live and max/msp, but :

- when i map my wii data to midi channels, it's really hard to assign ONE of them to a live control since there are continuously data coming from the wiimote and going to live over the midi port... i have to enable only one parameter and press command+m in live to assign it, then coming back to osculator, enabling only one other parameter, going back to live, etc... not very handy... lets say very long to do...

-in the wimmote namespace, i can see an /wii/1/ir/xys (or something like that, i've no wiimote connected right now), ok x is x, y is y, and i guess s is the size, which can be used to evaluate the distance between my ir source and the wiimote. but this damned "s" stay constant, whatever i do...

any ideas?


g

Hey G.,

The problem you have with MIDI CC learn, is that the wiimote continuously sends data as long it is connected. To help with that, put OSCulator's window frontmost (go in the Window menu to do that), and solo the parameter you want to learn (Command-R). The solo function is there for that, and keeping the window frontmost makes it easier for going back and forth the two applications.

As for the size parameters, it does change but not so much. Depending on the size of you IR light source, it may or may not give you interesting results …


Best,
Cam

[stjohn]

hi do u think anything like this would come out for PC??

currently im using a wiimote with Max MSP.. and the tk.wii patch, trying to develop a finger tracking controller, and tk.wii doesnt not support multi point.