My question as a newb is how I use this? Do i simply run the script once?

This is great news. I’ve been finding serial osc a bit unstable on 10.9.5. Hopefully this resolves with the new update.

Best of luck wrapping it up. :coffee:

still testing cross-platform. apologies for the delay.

unless you want to compile the dev branch yourself, i’d suggest waiting for the release installers.

Any progress on this? Maybe you could provide instructions for compiling from source for now?


i’m not going to provide complete instructions since there is the potential for many things to go wrong and it’d take me a very long time to cover all of the dependencies. there are basic waf instructions in the libmonome readme.

i may try to get the mac version posted prior to the windows version being finished, will hasn’t had much time lately.

also, just a note-- the currently available serialosc works very well. this new version is minor improvements helpful for debugging and knowing what’s going on.

Thanks for the info! I’ve had serious issues when using my Arduino-based controller together with the current serialosc since Mavericks. I was hoping this would be resolved with the new version?

Now the new website is live, it might be good to do a page on all the ways serialosc/monomes can interact with Max7/BEAP etc.

I remember a great serialosc video about how we can now use our grids in Max for input/UI stuff but not sure if this was ever formalised.

I’m looking at ways to bring my grid into my max patches and this would be a good way to start before learning the coding/scripting stuff.

didn’t stretta do a BEAP intro video?

i’m not sure what else to say about Max other than BEAP and the Grid Studies… what specifically would you suggest?

There’s a monome devtools patch you can download from the extend page on monome.org (hope I remember that correctly) which makes it all pretty clear imo. At least, that’s where I got started. It explains all the syntax for connecting to the grid (or arc) and sending/receiving commands to and from it. Pretty straightforward.

have you seen this?

http://monome.org/docs/grid-studies/max

thanks for the answers, I’m saving the grid studies page for when I’ve can devote more time to it, I’m still only 6 months into learning Max.

it was a expanded, written version of this that I was looking for:

just showing all the cool things you can now do with serialosc.maxpat & max 7 that are wired in under the hood.

I remembered seeing the video but then never saw anything further documenting this, perhaps its all hiding in the .maxhelp files in Max 7. I’ll have a look tonight.

Where can I find serialosc-monitor?

Ah, found this and it seems to do what I need:
http://archive.monome.org/docs/app:monome_home

hey!
uhm, i’m on max 6 and using a 2009 256 device, an older version of serialosc, mac yosemite and everythings working perfectly. is there a need or would i have any advantages if i upgrade to max7 and the new serialosc?

Was there a serialosc update? I don’t know where to find it. Is it only on the Github and you need to build it? Does it support encoders on 40h? Thanks!

Jimmy

the current serialosc installer is good. we have a new version with somewhat invisible improvements that’s waiting for packaging and an auxiliary monitoring app.

40h encoders are very poorly supported-- i’m not sure if they’re in serialosc. you may want to run monomeserial, which will create different headaches possibly. what is your goal?

I’m just trying to use that strange ‘slab’ I got that has a 40h and 2encoders on it. I can use monomeserial 0.20 and get the encoder data out, but I thought maybe I should move off such an old version.

Maybe I should pull the 40h out of the slab and turn it into a 40h in a more standard enclosure.

I found the 1.4 version of Serialosc installer today.

Thanks

ah, the slab. i would stick to monomeserial, or simply rehouse the grid without the encoders.

are you guys talking about these encoders: http://archive.monome.org/docs/tech:mk:aux:enc ?

i remember you were working on this for me a while ago, but everytime encoder functionality was included, the button/pad response time was inhibited.

i haven’t really thought about these in a while. should I assume it’s better that i keep ignoring them because future implementation will most likely not happen? i don’t think i’ll rehouse my grid, i’ve grown attached to these knobs sticking out the side, even if they are never used.

cheers

Neat. I’ve never seen those encoders before. What I have is a 40h type grid in a big slab of walnut with two encoders one one side of the grid. It’s bounced through several owners, and currently it’s my ‘opportunity.’