![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: osc Message form |
garth paine Member |
![]() ![]() ![]() Hi all I am working with a lot of OSC messages coming into Kyma and I have had a few problems: One is that Kyma seems not to like names in the form The other is that Kyma seems to buffer the OSC names it sees so that when one goes to assign an OSC message to a fader using right click, OSC message names that have been changed still show in the array of possibilities - it would be much better I think it if just showed the OSC messages it is currently receiving - although I guess this may have something to do with saving the state? Cheers, Garth IP: Logged |
garth paine Member |
![]() ![]() ![]() another question - I am finding allocating the OSC by right clicking on the widget name a little unreliable - for instance I have a fader that tells me is it set to /kWater01Energy, but it is not moving with the OSC data. Also I have a widget set to /kWater04Energy and it is moving along with the OSC data, however, the small slider I have in the VCS that show the OSC incoming numbers and the !WaterEnergy04 which the SoundToGlobalController outputs from that OSC stream have both stopped showing change, so I am suspecting that the OSC stream has been redirected to the fader and is no longer available to the SoundToGlobalController - is this the case? Does this mean I can not allocate the same OSC data to more than one VCS widget? If so I gess I need to hardcode the SoundToGlobalController output instead which I know I can plugin into any number of sounds. Thanks, Garth IP: Logged |
garth paine Member |
![]() ![]() ![]() I can add here that I had two OSC messages kWaterStream04e kWaterStream04x Kyma did not seem to be resolving the difference. IP: Logged |
SSC Administrator |
![]() ![]() ![]() For your first question, could you provide an example or explain it a little more? We tried sending /kWaterStream04e to the Paca(rana) and was able to assign that to control a VCS widget. Also, we used !osc_kWaterStream04e in a parameter field of a Sound and that worked. The Paca(rana) remembers the last 32 OSC messages it has received since it was turned on and does not have any way to know if you have stopped using a particular message.
At this time, you can control exactly one VCS widget with an OSC message. IP: Logged |
SSC Administrator |
![]() ![]() ![]() Are you certain that your other program is putting out the correct OSC messages? We just tried sending /kWaterStream04e and /kWaterStream04x (which were each mapped to a separate VCS widget) and were able to control them independently. IP: Logged |
garth paine Member |
![]() ![]() ![]() Thanks Guys - yes I found this worked fine as a sound, but not in the timeline. I setup SoundToGlablaControllers (STGC) in the timeline with the !osc_kWaterStream04e as source and an output !waterFourEnergy - I have about 14 data streams coming in. In the timeline I got some weird behaviour where Kyma complain I had more than one source for the STGC and should correct that and the neither the input or output for the STCG showed in the VCS. I know i did not have duplicates of the message being sent from MAX so I am not sure what was causing this. I then changed the names and it worked. I wandered whether there was a name length limitation? but in essence if I tried to have !osc_kWaterStream04e and !osc_kWaterStream04x, and I have these for 8 water streams. then Kyma complained until I changed the names. This behaviour was in the timline only. IP: Logged |
SSC Administrator |
![]() ![]() ![]() Hey Garth, if possible could you email us a stripped down version that exhibits the behavior? Thanks! IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.