neophob
commented
10 years ago This on the todo list, as the next release should contain a touchosc gui this feature will be included.
Open ozett opened 10 years ago
neophob
commented
10 years ago This on the todo list, as the next release should contain a touchosc gui this feature will be included.
ozett
commented
10 years ago Wonderfull! I found also version 2.0 production some minutes ago. (no blog entry, no feed?) its actually running ... i copied properties and blinken to upgrade....
i leave this thread open, as you wanted to see whats still on the list. ok?
neophob
commented
10 years ago Blog post will follow soon, thanks for the reminder ;)
Yes, leave this issue open, I'll close it if its implementet...
ozett
commented
10 years ago Hi, right now i managed to send OSC-Messages to Pixelcontroller to change presets.
as long as there is no status-info about a currently running preset implemented, i have a workaroung to store the running state in the fixed preset-nr 140 and recall it from there. But i have timing issues between the separatle send commands of 1) change_preset to 140, and 2) save_preset, 3) change_preset new, 4)load_preset...
That brought me to scan through the OSCspecification 1.0, which showed me a "OSC-Bundle". With this i could send both OSC-Messages in one "OSC-Packet". My question: if i go further in this direction: is "OSC-Bundle" implemented in pixelcontroller 2.0/2.1 ?
besides that, Thanx, Pixelcontroller is running great !! and still discovering great presets ....!! ozett
neophob
commented
10 years ago Bundles are supported yes
Hi, I managed to control Pixelcontroller via some simple OSC-Messages, send via osc-send from the toolkit. I change Presets with this. Is there a way to query Pixelcontroller which Preset or Generator is actually running? I dont see some Return-Objects or any method to query actual Infos from running Instance, instead of perfomance.
Thanx, Pixelcontroller is running great !! ozett