Object audio fades respecting fade curves

[FL K]

Hi lovely folks at F53,

As I am building a show I wanted to give an object moving through the space acceleration - like g force in free fall; what I have tried (in vain):

- alter the fade curve of the fade cue that moves the object (result - the object seems to move at the same constant speed)

- drawing a new path that sees points closer to the beginning of the object's path closer together, and growing progressively further apart towards the end of the path (in case the logic somehow divvies up the cue time equally between segments of the path) - result - the object seems to move at the same constant speed.

May I ask, is this non-adherence an oversight/was not a high priority when implementing Object audio, or is there a deeper reason not to do it?

Of course work arounds could be to try and break up the fade manually into more, smaller fades, but that is less than elegant and time consuming, so it would be amazing if the fade curve could indeed act on the speed/percentage of completion of the path, similar to all other parameters that fade cues control.

Cheers,

Freddy

[Sam Kusnetz]

All work takes time.

We opted to release object audio when we did with the set of features that we thought made the most impact.

As I hope is obvious by now, we continue to develop new features, and new additions to existing features, all the time.

Constant-speed paths are not an oversight, they are the preexisting condition of automation in QLab. Adding variable speed to paths is going to take work, and we decided to defer that work until after we completed other things that we thought were of a higher priority.

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/f964e374-ad95-4909-93c5-f0af5f50eb08n%40googlegroups.com.

[FL K]

Hi Sam,

Thanks for the clarification, and apologies if my question and/or its wording came across as demanding, this was not my intention at all - object audio is such a cool feature! I just had one question about one of your statements below:

On Friday, 15 May 2026 at 02:15:18 UTC+10 sam wrote:

Constant-speed paths are not an oversight, they are the preexisting condition of automation in QLab.

 

Oh, I figured that because it existed in both the audio and the video domain (that progress along a fade are bound to the shape of the fade curve) both concept and execution were established pathways to draw from?

Adding variable speed to paths is going to take work, and we decided to defer that work until after we completed other things that we thought were of a higher priority.

Sure thing; I am trying a workaround I think is supposed to be supported by current feature set?

- play a cue with q number "falling" with an object "A"

- play a text cue with q number "guide"

- use a localhost loopback network cue that sends continuously /cue/falling/audioMap/object/A/position/y/live #/cue/guide/translation/y/live#

- play a fade cue with the desired fade curve that fades the geometry of "guide"

At the moment, while the elements are described in the OSC dictionary, this does not seem to work for me - the object stays put (I am watching the monitor) in "falling"'s start position.

I have attached an example workspace; am I missing something crucial, or is there a bug?

All the best,

Freddy

[Sam Kusnetz]

You’re really close;

This OSC message:

 /cue/falling/audioMap/object/A/position/y/live #/cue/guide/translation/y/live#

Should instead be:

 /cue/falling/object/A/position/y/live #/cue/guide/translation/y/live#