Hi all,
what are the OSC adresses for the Names of active Song in Setlist and also for Previous Song and next Song?
I found the adress “/RackspaceName” for the active Rackspace which works perfectly, but I would like to see actual, previous and next song in Setlist Mode on my TouchOSC remote.
I wasn´t able to find that in the OSC messages part of the manual.
I partly solved that myself searching the community. So I found “/CurrentSongName” for actual song in an earlier post.
I also found “/NextSongName” just by trial and error…
“/PreviousSongName” which I would have been expecting for previous Song doesn´t work though.
So what is the adress for previous Song?
Is there a list of these adresses somewhere?
I want to display the names of current song, next song and previous song on my touchOSC remote.
I was able to find the adresses for “current song” (/CurrentSongName) and “next song” (/NextSongName). They are working already on my remote.
I´m just missing the adress for “previous song”…
Glad to help you
If you open the monitor OSC in the TouchOSC you can see all the OSC messages sent and received…it helped me a lot to know all the messages used
I’ve been having a really tough time figuring this out as well, and finally realized that I had to set the correct Remote client IP address in Gig Performer (under Options → OSC Setup). Any system OSC messages GP sends out get sent to this address, so under “Manage OSC Targets” I set up the address for TouchOSC and then set the remote client IP address to that. I’m also running BitWig on the same computer and launching clips via OSC from GP so I originally had that set to BitWig’s address. But you don’t need that since for any widget, you can enable Direct OSC and target any client you want (BitWig in my case). Now when I use /RackspaceName as the OSC message attached to a text or label in OSC it’s showing the rackspace name correctly. Hooray! I hope this helps someone else as well because this was extremely frustrating.
Yes, that is described in the manual, and believe me, I read that section many times. It just didn’t click for this particular application with TouchOSC until now.