Multiple Cuelist Control

[arcmusicman]

First, thank you for creating a fantastic piece of software. However, I am encountering issues using multiple instances of the module connecting to QLab on the same system. Here is my setup: I have two cuelists I need to have independent control over: Cuelist A and Cuelist B. I configure each instance of qlabfb in companion to have a unique name, connect to 127.0.0.1, and enable TCP feedback. After that, I refresh the page and select 'Specific Cuelist' A for one and 'Specific Cuelist' B for the other. Then, using the feedback variables, I populate some buttons to show the current playhead cue number and cue description. It all makes sense, but does not function correctly most of the time.

Instead, the behavior is this: regardless of the qlabfb connection instance referenced by the companion buttons, the QLab cuelist controlled and feeding back data is the one most recently in the foreground. This may be a QLab limitation or it may be your module.

I have tried multiple approaches to solve this issue: -Referencing the public IP address instead of localhost -Moving the cuelist to another workspace and referencing that workspace instead (even assigning different pin codes to the different workspaces) -Restarting QLab/the Session/Companion in different order

Frustratingly, the multiple cue lists occasionally work correctly, but it is very rare. This issue has persisted across multiple setups/systems/operating systems all running the latest public release of Companion.

Any insight you could offer would be greatly appreciated.

[arcmusicman]

First Config

Second Config - referencing the local IP as a test...

On the few occasions it works....

[istnv]

Do you have a showfile you can share? If not, I'll try and put something together. I have some time to set up my macbook and dig into this. Are you Paddy on Facebook?

[arcmusicman]

Thanks for responding!

Yes I am Paddy on Facebook, and I will send you the show file tomorrow when I get to work. Have a good night!

-Patrick

On Thu, Nov 19, 2020, 12:27 PM John Knight Jr notifications@github.com wrote:

Do you have a showfile you can share? If not, I'll try and put something together. I have some time to set up my macbook and dig into this. Are you Paddy on Facebook?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/42#issuecomment-730618070, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHZEVIEYTUJKNVMUF543SQV5SZANCNFSM4T32NGXA .

[arcmusicman]

I recreated the issue here again. Any help would be greatly appreciated!

-Patrick

On Thu, Nov 19, 2020 at 12:27 PM John Knight Jr notifications@github.com wrote:

Do you have a showfile you can share? If not, I'll try and put something together. I have some time to set up my macbook and dig into this. Are you Paddy on Facebook?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/42#issuecomment-730618070, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHZEVIEYTUJKNVMUF543SQV5SZANCNFSM4T32NGXA .

[istnv]

Are your label buttons the playhead/next cue or the running cue?

[arcmusicman]

The label buttons are the playhead cue.

On Sat, Nov 21, 2020 at 2:56 PM John Knight Jr notifications@github.com wrote:

Are your label buttons the playhead/next cue or the running cue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/42#issuecomment-731649013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHZADSTWVCG26FC7EVFTSRBAR3ANCNFSM4T32NGXA .

[arcmusicman]

Have you been able to reproduce the issue?

On Sat, Nov 21, 2020 at 2:56 PM John Knight Jr notifications@github.com wrote:

Are your label buttons the playhead/next cue or the running cue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/42#issuecomment-731649013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHZADSTWVCG26FC7EVFTSRBAR3ANCNFSM4T32NGXA .

[istnv]

Yes. When the patch gets included into the build it should work correctly.

[arcmusicman]

Fantastic, thank you very much! Is there an interim version I could use for the shows opening this week?

On Mon, Nov 23, 2020 at 12:23 PM John Knight Jr notifications@github.com wrote:

Yes. When the patch gets included into the build it should work correctly.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/42#issuecomment-732405458, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHZFCZ3MURVPPA34ROOTSRLAE7ANCNFSM4T32NGXA .

[istnv]

Looks like it is in today's build.

[arcmusicman]

Awesome, thanks for the update!

On Mon, Nov 23, 2020 at 1:49 PM John Knight Jr notifications@github.com wrote:

Looks like it is in today's build.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/42#issuecomment-732446412, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHZEFFNCUTIC4F2U6UB3SRLKH5ANCNFSM4T32NGXA .

[istnv]

Closing this. Re-open if it is still an issue.