Forums > Max For Live

OSC-route object not working Live 9 64 Max 6.1

January 16, 2013 | 7:23 pm

OSC-route object not working Live 9 64 / Max 6.1

Just wondering if anyone else is getting this problem with the live 9 64 beta and max 6.1 combination , i suspect its something to do with the fact that there is some kind of 32 / 64 missmatch but im pretty new to max and not sure if there is a way around this.

Note its working perfectly in live 8.3.4 (32bit) and max 6

Any suggestions would be appreciated.


January 16, 2013 | 7:29 pm

also note


osx 10.6.8

January 16, 2013 | 7:34 pm

All 3rd party externals will need to be updated to run in the 64 bit version of Max 6. OSC-route is currently a Max 6 32 bit external. Right now there is no SDK for the 64 bit version of Max 6 and hence there is no way for 3rd party developers to update their binaries.

We realise this is a significant problem for most Max and Max for Live users and we are working as hard as we can on the massive pile of work which is the 64 bit port in order to get to the point where we are able to publish the full 64 bit compatible SDK. Your assistance in testing the current version of 64 bit Max for Live will greatly help us get to that goal more quickly.



January 16, 2013 | 7:41 pm

Brilliant …

perfect answer … thanks so much Andrew , thought it may be something like this…

i wait patiently to use my spare 4 gig with live a little longer.

really appreciate it…


January 16, 2013 | 8:15 pm

FWIW, you might be able to make use of the regexp object as a workaround for OSC route in the meantime. Might mean a little bit of restructuring of your patcher, but perhaps an abstraction could be made which takes patcherargs, stuffs them in a coll to match to and sends on accordingly. JS might be another option if it’s not a problem to execute in the low priority thread.

January 17, 2013 | 11:28 am

Hey Mr kit Clayton…
cheers for the post.

Though i do understand the signal flow and in a very basic way , the objects your mentioning.
But i am new to max and this will take me a bit to sort out …
For now i am able to get by with live 8.3.4 and max 6 ….
But i will check out something based on what you said.
And really appreciate your answer.

Have a good one


January 17, 2013 | 9:08 pm

FWIW, Live 9 and 6.1 in 32bit should also work fine for your purposes. It is only 64bit which has the limitations on 3rd party externals, which will need to be recompiled once the SDK is public.

January 18, 2013 | 12:24 pm

yeah mannnn…
all good with using other versions

im really just waiting to be able to use live 64 , for the slight boost in performance , the thing is its very heavy on the max side also , so any little power increase is gonna make a massive difference for me…

all good

thanks again


January 18, 2013 | 8:20 pm

You won’t see significant performance improvements in 64bit. The main benefits to 64bit is using a larger memory space, and the ability to use numbers with 64bit precision as passed by max messages.

January 18, 2013 | 8:56 pm

"The main benefits to 64bit is using a larger memory space"

exactly what im talking about….

January 25, 2013 | 8:25 pm

also note

osx 10.6.8

Does it work with 10.8.2 ?

January 25, 2013 | 9:44 pm

@ Stephane Morisse

The issue at hand here seems to be the bitness of the applications WRT bitness of third-party externals, not the OS – so barring any unrelated incompatibility . . . it should work fine on 10.8.2.

January 26, 2013 | 11:46 am

not sure about 10.8.2

im running osx 10.6.8 in 64

all good.


February 20, 2013 | 8:48 pm

Exciting times ahead!!

March 25, 2013 | 2:17 pm

Hi I’ve been trying to roll my own version of OSC-route while I wait for the original to be updated, it seems to work, would love to hear feedback. It takes multiple arguments and puts them in a traditional router (with 10 outs). It uses a regex, which I saw on another post about OSC-route, to convert the OSC namespace into a list. It then reverses that back,

— Pasted Max Patch, click to expand. —
April 19, 2013 | 11:23 am

hello, there is a way to parse a list of float?
here an example, it behave unlike OSC-route.

— Pasted Max Patch, click to expand. —
April 19, 2013 | 4:13 pm

[route /test] ?

July 8, 2013 | 1:27 am


just found out there are two links to downloads of the [osc-route] object…
one is old
one is new

old =
new =

new supports 64bit!!!!! pfff…

July 8, 2013 | 1:39 am

thanks LUC3 …. ill check it out .. at the time i ended up bringing the osc in with

regexp (/) @substitute " "

so all good

but sadly my set relies heavily on a a 32 bit au that dose not work with any wrapper …. , so im still idling on 45% cpu in live 8 , with live 9 64 waiting patiently on my dock.


July 8, 2013 | 2:00 am

why live8? Live 9 32-bit works well, I’d say?

July 8, 2013 | 2:07 am

" why live8? Live 9 32-bit works well, I’d say? "
not sure bth , there was a reason at 1st … but really cant remember at this stage …
i think i was getting weird lock ups from 9 , and also weird drop outs of send and receive objects in max6 from memory …. id say ill have another look soon.

just tested the new oscrouté

all good ….


July 8, 2013 | 3:03 am

Yee hah I’ve been waiting a while for this! thanks for finding it!

July 20, 2013 | 12:35 pm

to make a MaxForLive frozen device compatible with both 32bit and 64bit systems, should a separate device be frozen out of Live’s 32bit and 64bit versions? I am freezing the device from a Windows machine with Live 9.

Viewing 23 posts - 1 through 23 (of 23 total)

Forums > Max For Live