Qlab hotkey trigger - how adjust levels on a hotkey??

Hi all!
So, wrestling with Qlab 5 (some changes in there that are infuriating...). We have an audio cue that we've assigned to a hot key (trigger). The audio cue is not being used at all within the cue stack - we placed it at the bottom of the pages of cues. We adjust levels, even trim, of that audio cue, but the hot key trigger ignores any level settings. Is there no way to adjust the level of a hot key trigger??
What am I missing here?
Thanks so much for the help!!

hello!

i'd love to know more about what changes in QLab 5 you find infuriating, but to try to answer your question directly i think i need more information. i think what you're doing here is setting up a single Audio cue which you want to play at any time, using a hot key, and you want to adjust the level of that Audio cue. is that right? or are you trying to use the hot key to adjust the levels of a different cue?

could you post your workspace file here so that i can download it and take a look? i'm quite confident i can help you out here. and then after that if you feel like discussing the other things, we can do that too.

On my home computer I just downloaded an update to Qlab 5, and I'm not having the problem, so I'll update at school and see if that solves the issue. Probably a bug that got fixed in an update.
But - yes, this issue was for a single Audio cue which I want to play at any time, using a hot key. For whatever reason, changing the audio level for that cue had no effect on the level played when the hot key was struck. And there was no way to adjust the level, the hot key played the audio cue at the same level no matter what.

A couple things off the top of my head that bug me about the update is merely changing where to find adjustments - like "integrated fade" checkbox. Now it's at the bottom of the screen, not on the right. Why change that?
The symbol for Auto Continue - why change that?
I hate updates that change where a button or checkbox is placed - for no apparent reason. I'm left jumping between updates (because some of the schools where I work are running 4 (lifetime licenses) and some are running 5 (new licenses), and having to remember where something was moved, or how it now operates.

I'll let you know if the update to 5.1x fixes the hot key level issue.
thanks!

doggmann said:

On my home computer I just downloaded an update to Qlab 5, and I'm not having the problem, so I'll update at school and see if that solves the issue. Probably a bug that got fixed in an update.
But - yes, this issue was for a single Audio cue which I want to play at any time, using a hot key. For whatever reason, changing the audio level for that cue had no effect on the level played when the hot key was struck. And there was no way to adjust the level, the hot key played the audio cue at the same level no matter what.

Click to expand...

ok, glad to hear you're not seeing the problem at home. keep me posted, and once again if you still have trouble, please post the workspace for me to look at or contact [email protected] to get the fastest help.

doggmann said:

A couple things off the top of my head that bug me about the update is merely changing where to find adjustments - like "integrated fade" checkbox. Now it's at the bottom of the screen, not on the right. Why change that?

Click to expand...

we moved all the controls from the right edge of the time & loops tab to other places in order to maximize the available space for the waveform view. the more you can see in that view, the more useful it is, so we took this opportunity to improve that aspect.

doggmann said:

The symbol for Auto Continue - why change that?

Click to expand...

three reasons:

1. folks with limited eyesight or low-resolution displays could have a hard time with the auto-continue arrow
2. there was also no semantic link between the shape of the arrows and the role that they play, so a person just had to memorize which was which without any clues.
3. it was difficult to describe them verbally... "one is like an arrow, but with three downwards-pointing bits, and the other is like an arrow but with a circle at the back, sort of like an anchor maybe?"

the new symbols attempt to improve on all three points:

1. the two shapes are easier to see. fewer small details, and no closely-spaced series of parallel lines which tend to blur.
2. continue is just a straight arrow, and follow is an arrow with a flag. F for flag, F for follow.
3. as you can see, it's easier to describe the new ones.

doggmann said:

I hate updates that change where a button or checkbox is placed - for no apparent reason. I'm left jumping between updates (because some of the schools where I work are running 4 (lifetime licenses) and some are running 5 (new licenses), and having to remember where something was moved, or how it now operates.

Click to expand...

i agree that changes for no reason can be disruptive and feel pointless. we try to avoid making changes that feel disruptive at all, and when we do make them, we do it because we have a reason to. i hope these explanations feel helpful... we don't want to frustrate you!

jumping back and forth between QLab 5 and QLab 4 is indeed irritating, and my honest answer there is simply that improvements require change, and change takes getting used to. i try to imagine a first-time users of QLab sitting down to QLab 5 and learning from scratch, and try to make sure that the new design makes their life easier.

Sam Kusnetz said:

the other is like an arrow but with a circle at the back, sort of like an anchor maybe?

Click to expand...

That's certainly how I'd always read the symbol - as an anchor, and couldn't work out the connection.