You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 19, 2021. It is now read-only.
hi, i am digging into OSC-Bundle messages and saw the specs about the timestamp in OSC-Bundle messages. it says, If the thimestap is in the future, the server will process it than. That means, one could send OSC-Messages as a timer, to change presets at a later time. do you ever experienced/tested this? Will it work on your implementation of an OSC-Server?
The text was updated successfully, but these errors were encountered:
i read it in the specs for OSC on opensoundcontrol. (http://opensoundcontrol.org/node/3/#timetags)
as i wanted to leave as less work for a real programmer ;-) i took the last hour to test this. i grabbed a copy of pyOSC (https://gitorious.org/pyosc) and changed the testing.sender.py from the example to send bundles. at least (puhhhhh) i managed it.
besides: i now can send this binary-data from my homeserver to pixelcontroler. so i hope i can now faster change between presets. i do this, if someone walks through the motionsensor and walks down the stairs - i gabe him a white preset with a lot of light - and after 10 min. back to a prettty constantly running preset. now i can send with a bundle only 1 message instead of 2 messages before ( which had been 1)change preset and 2) load preset).
back on topic: than i went into the risk and added a timestamp for 60sec in the future to the bundle, send it to pixelcontroller and it was immediatly processed. so pixelcontroller (2.0) ignores this!?
as is wanted to give you a good basis, i cross-checked the send data with wireshark. so as long as i see, the timestamp was correct. if youre now interested in this, i can leave this up to you....
besides another point: what about with only 1 OSC-message to change to a preset and also load (=activate) it? like /SWITCH_PRESET, or to have all OSC-Preset messages alphabetically sorted, all preset-related OSC-Messages could start with /PRESET... , like /PRESET_SWITCH 140, /PRESET_LOAD 140, /PRESET_CHANGE 140, /PRESET_ACTIVATE 140 ...
i add a picture...
go on famous pixelinvader!! (is there developer release of 2.1 to test yet?)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
hi, i am digging into OSC-Bundle messages and saw the specs about the timestamp in OSC-Bundle messages. it says, If the thimestap is in the future, the server will process it than. That means, one could send OSC-Messages as a timer, to change presets at a later time. do you ever experienced/tested this? Will it work on your implementation of an OSC-Server?
The text was updated successfully, but these errors were encountered: