#Touchosc editor windows buttons not visible download
→ download serialosc (be sure to restart your device afterward) additional docs I realise that this project uses a large number of OSC objects as well as nearly 20 loop back channels.Serialosc started ~/Library/LaunchAgents/ There are other TouchOSC LED objects that continue to work fine at 4.9.0 (eg the Drum Beat LED) so fundamentally the functionality still works - just not for all objects. If you load the project under 4.8.5 you will see it working as intended. If I assign an existing TouchOSC object eg ScanOff to the same QLC+ Button, I see it behaving as expected ie receiving feedback OK, and pulsing as the chaser runs in time with the speed dial. There are other objects affected in the same way too. Sometimes I can not register it in the input profile, and sometimes I can register it, but not auto assign it to a VC button. The specific problem I am having is that' with 4.9.0 that object is no longer receiving feedback, and even if I create a new button to replace /Main/TapLED, it still does not work. This all works fine, and the project in question works fine at 4.8.5.Īs you can see in the input profile /Main/TapLED is registered OK. I create a TouchOSC button and register,assign etc it in QLC+, and then once the project is working I recreate the TouchOSC object as an LED. This is a technique I have used a few times.
Yes, the /Main/TapLED is a TouchOSC LED not a button. I am also very close to having a production ready, headless Raspberry Pi 2 implementation running too. I could run tests on Win 7 if that helps, but Linux is my real target OS. I'm sorry I can't be more specific or helpful in narrowing down the symptoms, but am willing to provide further information if that will help, and to run further tests as requested. All buttons work fine at version 4.8.5, and the TouchOSC / QLC+ configuration has been used live at stage performances.
In fact, other buttons which were added later in the development of the OSC template work fine. They certainly weren't the last to be added to the OSC template. I can't identify anything special about the OSC buttons that don't work. The TouchOSC profile file has been stable for a while and thoroughly tested previously, and used in production. After upgrading to 4.9.0 I have certain OSC controls that don't work, and some that work but don't receive feedback.ġ) 90% or more of the OSC buttons work fine, with feedbackĢ) the OSC buttons which don't work are not detected by the Input Profile Editor Channel Wizardģ) I created a new 'test' button on the OSC template, and this was detected by the wizard, but when I went to the Virtual Console to assign it to a button it was not detected.Ĥ) Restarting QLC+ allowed the test OSC control to be AutoDetected in VC and assigned to a VC button, but no feed back is sent to the iPad when using that button.ĥ) I know the QLC+ functions are running correctly, and in fact if I temporarily assign the VC button to a working OSC button - then the two way communication works fine (ie button press & feedback) - but it won't work when I revert back to the problematic OSC button I have a project which makes heavy use of TouchOSC (I have replaced my Behringer LC2412 with a customised TouchOSC template on an iPad).
I have also been having issues with TouchOSC after upgrading to 4.9.0
0 kommentar(er)
