Collaboration Playhead

[daan....@gmail.com]

Using collaboration in Qlab 5, the playhead is separated from the selection while editing on a second computer. I understand this is needed, because a person working on the 'main' computer would go crazy if his current selection and playhead is skipping around when a person on the second computer is editing cues.

However, I'm in the situation where the main computer is at the backstage and I'm programming at the front of house.

Right now I am getting used to using the "V" (preview) key to start cues from the second computer. Or today I will try setting "Spacebar" to be the preview key. This way the selected cue will play instead of the current selection/playhead on the first computer.

However I think it would be handy to have an option the secondary computer can have ownership over the current Playhead position. I guess every computer needs to have an individual settings for “Lock playhead to selection”.

In my case: I would turn “Lock playhead to selection” off on the main computer, and enable it for the secondary. This way I can use the spacebar as normal.

Anyd thoughts on this? Am I missing something? :-)

Best, Daan

[micpool]

If you select a cue and press L  to load the playhead will move to that position

Mic

[Daan Hazendonk]

Thanks that helps :-)

Op donderdag 3 november 2022 om 14:07:28 UTC+1 schreef micpool:

[Chris Ashworth]

Thank you Daan!

I’ve added your thoughtful email to our issue tracker for this

-C

[Daan Hazendonk]

Hi Chris, thanks!

It would even make more sense if two users are in different cue-lists, they can both have their own playhead and use the GO (spacebar) as normal.

Working on a show right now, not being able to have my own playhead when working on a secondary computer totally makes it impossible to use the collaboration function because I keep forgetting the playhead is somewhere else as my selection.

So I switched back to Screen Sharing with the primary computer ;-)

Also editing sound effects is not possible. Hope that would be possible in the near future but I can see why that's not implemented yet because of the UI of the effects.

Best, Daan

Op vrijdag 4 november 2022 om 18:48:35 UTC+1 schreef ch...@figure53.com:

[Chris Ashworth]

Helpful thoughts Daan, thank you.

Regarding the audio effects, yes, this is quite challenging.  There are a few approaches we could consider:

- create a generic UI on collaborator machines to send “raw” properties over to the primary machine Audio Effect

- force collaborator machines to have the same Audio Effects installed if they want to edit the effect

- (possibly others?)

It’s a bit thorny, but it’s on the radar as a concern

-C