A while back, I modified an existing MaxForLive device to send OSC messages out of Ableton Live, with the OSC address being the name of the clip. I wondered if AbleSet could be used for the same purpose?
For example, any number of tracks tagged with +OSC that would āreadā the name of clips and send that message out to an OSC server. There would have to be a way to input the port number and IP address (preferably multiple destinations for different tracks).
This would allow for creative automation of OSC responding hardware and software natively through AbleSet. Possibly even an additional way to automate AbleSet itself on the localhost?
Leo! Next level stuff. Ever since I discovered Ableset I have dreamed of timeline synced outbound OSC. This is a fantastic implementation! Every time you come through with something like this I can eliminate a layer of complexity from my setup, which makes me very happy!
Thank you so much for this brilliant tool and for continuing to make me fall in love with Ableset all over again! I hope I donāt fall too far down the rabbit hole this week figuring out new and awesome ways to use this
footnote: I canāt tell you how long I battled with a Max For Live implementation to do what youāve done so elegantly. It almost drove me mad!
Iām glad to hear that youāre happy with this feature and would love to hear what use cases you come up with! Iām planning to add some examples to the documentation as inspiration for others who might be interested in this feature.
I know Iām obviously doing something wrong here.
What I was trying to do was display āMBPā on the MacBook, and āiPhoneā on the iPhone
Iāve gone through the documentation but I canāt find information on the ports I should set this to.
For OSC commands to AbleSet, you can omit the host and port entirely. Then, to target a specific device for the notifications, change the āallā parameter to the name or IP of the device. You can change the name of a device on AbleSetās settings page.
E.g. /notify/big 127.0.0.1 MBP or /notify/big phone iPhone given that youāve named your iPhone āphoneā in AbleSetās settings.
I hope this helps! Let me know if the documentation can be more specific for this. Itās still fairly rough and a work in progress
I think it might help to be a bit more specific for those who arenāt as tech-savvy.
For example, I discovered through trial and error that if a device has spaces in its name, you can target it by typing single dashes instead of spaces. So, āDevice 2ā would be āDevice-2ā.
Hmm, thatās interesting. Thereās no code that converts spaces to dashes, so I donāt know why this works
If youād like to supply parameters with spaces, you can also wrap them in quotes, e.g. /notify big "Device 2" "Test Message". Does this work for you as well?
Is it possible/could it be possible to send use the OSC track to send commands that control the show/hide toggles for Performance view?
Absolutely love the remaining song duration setting and its clutch when weāre in a full song, but in most cases weāll transition out of a full song into a click loop at the same tempo of the previous song to play behind an emcee giving announcements. I mark these as their own āsongsā so our band members remember its coming up. But I would love to be able to disable the song duration in these quick loop sections. Since it is only a 1 second loop (and I added the flashing loop indicator) the added animation of watching the duration count down one second, disappear, and then loop over and over again is a lot of on screen action.
But I thought this might be something the new OSC track commands could handle, send a āhide remaining song durationā a beat before that locator is reached and then send a āshow remaining song durationā the next spot in the set, etc. I looked in the documentation and donāt think I saw anything about the view settings but itās very possible its there and I just did not realize.
The behavior youāre seeing looks like a bug ā the remaining time shouldnāt disappear at the end of a song. Iāll release a fix for this with the next update soon.
That said, the idea of controlling the visible elements on the performance page via OSC is still interesting. Iāve added it to my todo list
