AbletonOSC supports OSC wildcard patterns using * to query all sub-addresses matching a path segment

When AbletonOSC receives an OSC message whose address contains , it regex-expands the wildcard to [^/]+ and dispatches to all registered callbacks whose address matches. Replies are sent individually for each match. For example, /live/clip/get/ 0 0 queries every readable property of track 0, clip 0 in one round-trip. This is useful for bulk state queries when building a controller UI or syncing a visual host to the current Live session on startup. The wildcard matches within a single path segment only (it does not match slashes), so it expands one level at a time.

Examples

Query all clip properties: /live/clip/get/* 0 0 — receives replies for name, gain, length, is_playing, loop_start, etc. in rapid succession. In the run-console: >>> /live/clip/get/* 0 0

Assessment

Explain what /live/track/get/* 0 returns. Would /live/*/get/volume 0 match all volume endpoints? Explain why or why not based on how AbletonOSC implements wildcard expansion.