m4l Connection kit OSC TouchOSC OSC address settings
Does anybody else have this problem?
OSC TouchOSC device does not remember OSC address settings when I reopen a live set.
Any solutions will be great..
Hi Korzybski, the OSC address settings should be correctly recalled in the OSC TouchOSC device from the latest version of the Connection Kit!
Hi,
I think the issue has not been solved.
I installed the last version of Connection Kit (April 2020) and OSC addresses are still not remembered afterI reopen the live set. This is a very bad problem if you have to relearn all the addresses....
For giving you more information, I am running it on a Win 64 bit and I see OSC data well received in the OSC TouchOSC device. It only does not remember addresses when re-opened. I also went to Github and copied the last version of the device to the Connection Kit folder. The issue persists.
Can you check this an provide a solution?
Same problem here
With the latest Live 10 and Connection Kit version installed.
Reconstruct:
Open a Live Session, and load the OSC TouchOSC device from Connection Kit
Make it work and configure it (IP/Port) to work proper over OSC
Map some of the OSC addresses to Live Parameters and test it
Save Session
Close
Open the previosly saved session in Live
None of the configured parameters will work!
You should see the yellow dot, so the OSC data is coming in, but it is not changing anything in Live anymore.
Any solution for this? And what is the problem?
It's a usefull plug in, so it would be great if it works.
I tried the same with the OSC Send pluging from the same kit and this one seems to reload just fine.
Similar issue here, running on Mac OS Mojave, Ableton Live Suite 11.
When reopening a saved LiveSet with parameters mapped it does actually show my parameters as still mapped (e.g. OSC address: /fader1 mapped to MIDI address: VCF Cutoff), but when I move that /fader1 in TouchOSC it doesn't change the parameter in Ableton / doesn't react (although I do get the Port blinking, showing me that Connection-Kit is receiving signals from said fader).
So it's basically the same problem in that I would have to relearn the parameters, the only difference being that the address (/fader1) is shown as "mapped" when opening the LiveSet.
Did you guys figure out a workaround?
I fixed it:
https://www.mediafire.com/folder/3470ksaq12jdl/OSC+Max+For+Live+Device+Fixed
also added speed limit control (for osc messages) and a midi version of the device.
Thank you Alan, those work great !
The mapping on the 2nd line seems to self-duplicate on the 3rd when blank, but I didn't have this issue when using all 8 slots of the plugin.
Alan, great work! Would you happen to know how to get the regular OSC MIDI Send to recall? I'm not able to recall changing the Port when loading a set.