AbleSet 3.1.0-beta.7

Beta
1

Cues

  • Added the ability to split Cues attributes into multiple, so [c:2] [c:halftime] now behaves the same as [c:2:halftime]

OSC Tracks

  • Added a new ? placeholder feature that allows you to specify where arguments from clip names should be placed (docs)
    • For example, if you want an OSC track to trigger notifications, you can use these attributes on the track name: [/notify/big all ? 2000 red] [single]
  • Added a new ?cc placeholder feature that allows you to insert the color of the current clip as an argument
    • Expanding on the previous example, [/notify/big all ? 2000 ?cc] [single] displays a notification in the color of the clip that triggered the OSC command

AbleNet

  • Added more logs around AbleNet for better troubleshooting
  • Fixed drift correction and “Sync Playback Now” not working when using the “Connect to Custom IPs” field

You can download this beta here:
Mac (Apple Silicon): https://ableset.com/download/mac-arm64/3.1.0-beta.7
Mac (Intel): https://ableset.com/download/mac/3.1.0-beta.7
Windows: https://ableset.com/download/win/3.1.0-beta.7

2

Hi @leolabs the new ? syntax looks really useful - can’t wait to test! Wondering if there’s anyway you could possibly expand it to include default values?

I would really like to use an OSC track to set the value of a shared variable, however, I would only like the variable to have the value while the playhead is on the region within the project. Without a default value parameter I would need to have a midi region for the entirety of the project with my default value, then have regions for the “new” value.

Example track name: Ext +OSC [/shared/active “?=no”]

Then, in that track a region titled “yes”. This would become the value of the variable when playhead on top of it and “no” at all other times.

image

Also, if the “Ext” track was inactive, then the value of the variable would stay as “no” - I have a use case where I would also combine the flags +GUIDE and +LOOPGUIDE to help determine the value of the variable.

Thanks for considering! :slightly_smiling_face:

3

Hey @zacjohnsnz,

That’s a good idea!

Currently, the only way to achieve this would be exactly what you described: covering the full timeline with a default-value clip and then placing your override clips on top.

I’ll pass this along, thanks for the suggestion!

1 Like
4

Hey @zacjohnsnz,

Just wanted to follow up; as of AbleSet 3.1 beta 10, this is now possible. There’s a new [?? default] syntax that lets you define a fallback OSC command or value that gets sent when the playhead reaches an empty space between clips.

So for your use case, the track name would look something like:

Ext +OSC [/shared/active] [?? "no"]

This way, clips named yes would set the variable to "yes", and whenever the playhead hits a gap, it automatically sends /shared/active "no".

Thanks again for suggesting this and let me know how this works for you!