Playback rate of 2D network fade

[Tweaky]

Hi all,

Wondering if it is possible to change the rate of a 2D network cue? 

What I'd like to achieve is a sound trajectory that is changing in speed while already started, similar to 'trajectory rate' in Spacemaps?

Thanks!

-- Dennis

[Sam Kusnetz]

That’s not possible right now in a single cue.

What you need to do is build your trajectory in parts which follow after each other, and give each part its own duration.

We know this isn’t ideal; this is on The List!

Best

Sam

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

--
Contact support anytime: sup...@figure53.com
User Group Code of Conduct: https://qlab.app/code-of-conduct/
 
Instagram: https://www.instagram.com/Figure53
TikTok: https://www.tiktok.com/@QLab.app
Bluesky: https://bsky.app/profile/qlab.app
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/qlab/ddd4e792-330b-4bec-8331-769fbdd95d0fn%40googlegroups.com.

[Tweaky]

Hi Sam,

Thanks for your quick reply.

I created a MIAP patch in Max to be able to change the rate of a trajectory. 

During the programming of this I stumbled on something I don't understand:

If I send an OSC string like this /cue/2/audioMap/object/AA/position/live 504 500 it works perfectly fine, and it moves the AA object in the map.

If I send this OSC string /cue/2/object/one/position/live 504 500 nothing happens, not even a reply from QLab with an error.

Do I miss something here? 

Best,

-- Dennis

Op woensdag 13 mei 2026 om 15:20:18 UTC+2 schreef s...@figure53.com:

[Sam Kusnetz]

On May 13, 2026 at 5:11:35 PM, Tweaky <dnn...@gmail.com> wrote:

During the programming of this I stumbled on something I don't understand:

If I send an OSC string like this /cue/2/audioMap/object/AA/position/live 504 500 it works perfectly fine, and it moves the AA object in the map.

If I send this OSC string /cue/2/object/one/position/live 504 500 nothing happens, not even a reply from QLab with an error.

Assuming you have a cue with cue number “2” which contains an object named “one” that should work fine, as it just did for me while testing it here.

It may be worth noting that the inspector for cue 1 won’t show the object in the “live” position; you need to look at the map monitor to see the live position of the object.

If you’re still having trouble with this, can you send a copy of your workspace and ideally a video of the problem in action to sup...@figure53.com please?

[Tweaky]

Hi Sam,

Yes! Thanks, it works indeed! 

Didn't know I had to look at the monitor, and expected it in the cue itself as I did see the audiomap object AA move there. Guess that has to do with the idea that audiomap objects are global?

Best,

-- Dennis

Op donderdag 14 mei 2026 om 15:49:31 UTC+2 schreef s...@figure53.com:

[Sam Kusnetz]

On May 15, 2026 at 5:19:16 AM, Tweaky <dnn...@gmail.com> wrote:

Yes! Thanks, it works indeed! 

Didn't know I had to look at the monitor, and expected it in the cue itself as I did see the audiomap object AA move there. Guess that has to do with the idea that audiomap objects are global?

Sort of, but really the reason is that OSC messages which end in “/live” only alter the “live” state of things, not the real saved state.

It’s like how after you run a Fade cue which changes the levels on an Audio cue, the inspector for the Audio cue shows the starting levels, not the current levels.