Visual Productions forum

Products => CueCore, QuadCore, IoCore, TimeCore & B-Station => Topic started by: ERC on January 22, 2014, 11:15:17 PM

Title: OSC trigger issue
Post by: ERC on January 22, 2014, 11:15:17 PM
Hi Guys...and Girl...  ;)

I have a little question regarding OSC triggering Cuecore over wifi. When I make a template and name my buttons like;
Push1, Push2, Push3, Push4 and I use the OSC Learn function in Cuecore. My problem is that the OSC learn function only learns the first letter of the button name, in this case "P". So Push1,2,3,4 can't be triggering different actions. I had to rename my buttons to q,w,e,r in order to use them in learn mode to trigger different actions.

Am I doing something wrong here?

Cheers,
Erc
Title: Re: OSC trigger issue
Post by: Dennis Kromhout on January 23, 2014, 09:03:02 AM
What firmware are you running? Just tested using TouchOSC and works fine.
Does the monitor show the strings you're expecting?
Title: Re: OSC trigger issue
Post by: ERC on January 25, 2014, 09:21:57 AM
Last version of Firmware for Cuecore. String seems to be learned ok. I have experienced this more then once. I use TouchOSC and a custom made template.
Title: Re: OSC trigger issue
Post by: djgait on March 06, 2014, 12:28:22 PM
Same issue here.

B-station pcb 1.04  FW 1.09

String is learned ok , but maybe there are a limited number of characters displayed in the webpage of the device.
I find the webbrowser very slow when a OSC device is connected, sometimes only responding after reboot of the device.

I do seem to have another issue regarding sending messages, but maybe that is an user issue:

I Recieve my OSC messages OK, but when send a message, verified the addres (e.g. /SAUNA/led1  value 1), the device detects the incoming message but nothing happenes with the led to be controlled.

EDIT:

It seems that the webbrowser of the units only supports 10 characters of message length. If you reformat the message so that it is maximum 10 chars long it works. This issue is for both incoming and outgoing messages.
Not handy since TouchOSC needs the page name as leading for address string and then you easily come to 10 chars