Osc problem

ray

i'm trying to send osc signals to three mac minis using three different osc multi transmit actors with three different osc addresses. on two minis it all works fine but on one mac mini the stream addresses /isadora/1 and /isadora/2 work fine but /isadora/3 isn't working. i keep getting a prompt to add something to the /isadora/3 address but i don't know what i should add. the other two work fine with just the address and nothing more added. the fan on the problem mini also gets loud sometimes. i'm using 1.3.0f24 and the minis are exactly the same. in the stream setup dialog box the third osc address is there but it doesn't receive any data. when i add another address it detects the data and when i add the correct address it prompts me for something more.

any clue what could cause this? in three days i'm having a visit from a museum curator and everything must be perfect so i'm getting a little desperate!!!

any help would really be appreciated!

best
ray

mark

Dear Ray,

It is a bug that you are able to enter addresses like /isadora/1, /isadora/2, etc. into the Stream Setup Windows – and in fact, doing so can cause older versions of Isadora to crash. (It's fixed in the current pre-release.) The OSC addresses /isadora/1 through /isadora/99 are "built-in" -- you don't need to enter them in Stream Setup. So clear everything out of your Stream Setup window, add your OSC Listeners, it should work.

If this doesn't solve the problem let me know.

Best Wishes,

Mark

ray

thanks mark, i'll try your solution.

best

ray

ray

hi mark

it didn't work.
i uninstalled 1.3.0.f24 and installed 1.3.1.f02 with no success on the mini with the problem. now it tells me '/isadora/1 through /isadora/999 are reserved for use by isadora'.
i'm not running any other programs, just isadora.
the master computer is running 1.3.0f24. maybe that's the problem but i really don't think so because all three osc addresses are working perfectly on the other two machines.
btw, i'm recieving a signal in the stream setup itself but not in the patch, have been all along.

best
ray

mark

Dear Ray,

The fix is in 1.3.1f03, which I'm still testing. If you PM me I'll find a way to get it to you.

Best Wishes,

Mark