QLab 5.4 public beta

[Sam Kusnetz]

Hello all

Today I’m very pleased to present to you the public beta of QLab 5.4:

https://figure53.com/temp/QLab-5.4-b2.dmg

This is a major (and free!) update to QLab 5. Here are some highlights:

★ ADDED: Mute and Solo buttons for cue outputs (found in the Trim tab of the inspector) and audio patch outputs (found in the Patch Routing tab of the audio output patch editor.)

★ ADDED: You can now edit audio effects from collaboration remotes. The audio effect must be installed on the remote computer as well as the primary in order to add it or edit it remotely.

★ ADDED: Fade cues now support 2D fading of video geometry.

★ ADDED: Several new tools for editing 1D fade curves and 2D fade paths, including arrow key navigation, multiple point selection, copy/paste, scaling, aspect lock while dragging, rotation and reverse tools, and a circle drawing tool.

★ ADDED: The up-fade and down-fade curves in the Curve tab of Fade cues can now be locked together as mirror images. When locked, changes to either curve affects both curves symmetrically.

ADDED: You can now set a finite duration for Mic cues and Camera cues.

ADDED: A submenu to allow more options when opening a target file in an external editor. You can find this submenu by right-clicking (or control-clicking, or two-finger-clicking) in the waveform view of the Time & Loops tab of the inspector.

ADDED: Support for copying audio effects between cue outputs and between device outputs.

ADDED: Support for batch-editing MIDI File cues.

ADDED: Support for moving cues using the AppleScript “move” command.

ADDED: The "Select cue..." tool now offers an option to quickly select the cue currently at the playhead.

ADDED: The IP address and port number of NDI sources are now shown in the Video Input tab of Workspace Settings → Video.

ADDED: Instrument definitions for a bunch of BriTeQ fixtures.

ADDED: Instrument definitions for a bunch of Chauvet DJ fixtures.

ADDED: Instrument definitions for a bunch of Chauvet Professional fixtures.

ADDED: Instrument definitions for several Clay Paky fixtures.

ADDED: Instrument definitions for the Epson EB-PU2100 series and EB-PU2200 series.

ADDED: Instrument definitions for the High End Systems Studio Color 575.

ADDED: Instrument definitions for a few Martin fixtures.

ADDED: Network device descriptions for Behringer WING, Bitfocus Companion version 3.2 and newer, Christie HS series projectors, Innovate Audio panLab Console, MA Lighting grandMA3, TheatreMix 3, and Yamaha DM7 series.

CHANGED: Carts now support up to 15 rows and 15 columns.

CHANGED: The minimum height of the inspector has been increased.

CHANGED: The existing network device description for Bitfocus Companion has been renamed to reflect the fact that it pertains only to Companion version 3.1 and earlier.

CHANGED: The network device description for Vor has been updated to reflect new OSC control options in Vor 1.6 and later.

We also included a big pile of bug fixes all across the program

We invite anyone and everyone to download this beta and send us your thoughts! The best way to do that is inside QLab via the “Contact support” menu item in the Help menu, or by emailing sup...@figure53.com with the subject “QLab 5.4 beta feedback” or something like that.

Happy cueing, all!

On behalf of the whole team at Figure 53,

Sam

—

sam kusnetz [he/him/his]

sound & projection design | USA 829 & ACT

503.201.2591

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

[dannax]

hello.
Automatically translated from Japanese.

I tried testing the beta version.

  CHANGED: The minimum height of the inspector has been increased.

I oppose this change.
When working on a Macbook Pro 14-inch, the inspector takes up unnecessary height, making the list difficult to see.
Depending on the tab, there is just a blank space at the bottom, which is meaningless.
Less efficient when working on a narrow screen.
You can change the height of the inspector yourself to a height that is convenient for you, so it is best to leave it as it is.

2024年5月16日木曜日 6:12:31 UTC+9 sam kusnetz:

[Chris Ashworth]

Hello Dannax,

Thank you for this feedback!

We have had some internal debate about this change — I have felt somewhat cautious about it, but others have argued that for most people the inspector is usually left in a much taller position anyway, and as we add more complicated controls to the inspector it is difficult to fit them in when the inspector is smaller.

I would be interested to hear if other people have positive, negative, or neutral reactions to the larger minimum height of the inspector.

Best,

Chris

[Mike Deyo]

Hi Chris,

I would also be interested in having the minimum inspector height be smaller. I understand the additional height needed for the mute/solo buttons in the trim tab, but the other tabs (maybe with the exception of the time and loops tab) now feel like they take up more of the screen real estate than they need to.

After some rough measurements, it looks like in QLab 4.3.8, the minimum inspector height is ~25% the height of my screen, and in 5.4 b2, the minimum inspector height is ~35% the height of my screen

I agree with Dannax, i think i'd prefer to have that 10% of screen height back

On my machine (2018 15" MacBook Pro) it looks like the mute/solo buttons are about 10 px tall. given that the trim faders scale with the size of the inspector window, i think i'd be ok with:

• restoring the minimum inspector window height to a size closer to what's in QLab 4.3
• shortening the trim faders by 10px
• adding the mute/solo buttons

I'm sure that at the minimum inspector height set to 25% of the screen, the trim faders would look stubby. But i think that if/when i need to make trim adjustments for a cue, it's likely that i'd increase the size of the inspector anyways, to whatever size gets me the fidelity i'm looking for

Finally, having the minimum height of the inspector set to 25% of my screen still gives me the choice of having the inspector be 35%, where the inverse is not true

So please add my vote to the "shorter minimum inspector window height" camp!

Thanks so much, and keep up the good work!

best,

mike

--
Contact support anytime: sup...@figure53.com
Follow QLab on Threads: https://threads.net/@QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
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 on the web visit https://groups.google.com/d/msgid/qlab/CADv1a4_HmF%3D6QQ%2BKNqdoa0JQcXAS4C1hSvYXPVuN7fwSeU9qGg%40mail.gmail.com.

--

Mike Deyo

Sound Human
315-430-3513

mikecheck.nyc

soundreferencenotes.com

Coming Up: Brooklyn Laundry (Winter 2024)

Coming Up: Twenty Sided Tavern (Spring 2024)

[Simon VB]

One more vote for NOT increasing the minimum height of the inspector!
Most of us (I think) use QLab on laptop computers in live context. Screen real estate is valuable.
As mike states above, having the inspector smaller still gives you the choice of increasing its size.

And yes, I know the inspector can be hidden, but if I'm honest, I mostly leave it open during shows to see the waveform display of the upcoming audio cue, just to make sure. Not a lot of height needed for that...
Thank you for reconsidering!

[Chris Ashworth]

Thanks all for the feedback everyone!  

We have a new build with a smaller change to the minimum height, which we’ll share soon to see how it feels.

One clarification is that the motivating constraint on increasing the height is in places like the 2D fade path controls.

-C

[jimsta...@zoho.com]

Thanks to Chris et al:

  Team QLab is as responsive to customer requests as I can imagine. Allstars.

But with my setup I didn't notice the change.

Jim