-->EXTRA : New wireless controller for QLab : EXTRA<--

[Erik Rosales]

Hey there QLab forum!

Ive been kickstarting a Swedish controller for quite a few times now. The Flic button. And when I got their latest upgraded button I contacted the crew over at Shotcut Labs to ask if they could implement some extra features to an upcoming show we are creating with my group Sirqus Alfon. Ive been working a lot with their previous versions but felt there where quite a few important things I wanted to ad. Since Im also living in Stockholm where they have their headquarters, I set up a meeting with them... And they've listened! 

So now the button can send OSC messenger across any network! 

They've also added a super low latency mode so that all the clicks are reacting with zero lag. And now you can monitor the Flic battery status, so that you won't start a show with low battery,,,

I wanted to share this with all of you guys, since this is my main place of getting fresh and great ideas on how to solve QLab matters ⚡️Lets keep up that sharing spirit!!!

Hope you guys like it. And since Im in contact straight with the developers, you could comment in this thread, if you want to have other features added as well (I can't promise that they will do as we please, but at least I have their attention 😎)

Here is a link to their website:

https://flic.io

All the best. Erik and Sirqus Alfon / D1gits

[Nordland Teater]

I have just recieved my first flic, but i cant get it to work with Qlab... I have entered the same that you have in your picture, but Qlab cant find the button.. What do i do wrong?

[Erik Rosales]

Hey there Nordland Teater. 

I think the problem might be that you need to name the cue list you want to trigg to something. In my case I have named my main cue list to GoMain. And therefore I have specified the osc string to point to the GoMain list:

/cue/GoMain/start

But you can name the list to whatever you want 👍🏼

Tell me if that solves your problem. All the best. Erik

[micpool]

On Thursday, May 21, 2020 at 5:29:25 PM UTC+1, Erik Rosales wrote:

I think the problem might be that you need to name the cue list you want to trigg to something. In my case I have named my main cue list to GoMain. And therefore I have specified the osc string to point to the GoMain list:

/cue/GoMain/start

But you can name the list to whatever you want 

Just to avoid any potential confusion.:

the OSC message  

/cue/GoMain/start 

will trigger a cue list NUMBERED GoMain

It won't trigger a cue list NAMED GoMain.

In this screenshot, the 2nd cue list from the top is the one that will respond.

Best 

Mic

[Erik Rosales]

Thanks for clearing that out Micpool 👍🏼

[Johan]

Tackar för detta Erik.

Jag tar mig friheten och för det vidare till Pygméteatern i din hemstad, som jag vet använder flic också.

Thanks!

[Erik Rosales]

Grymt Johan! Kul att höra att det kommer fler till användning 🔥

Allt gott!

[Patrick Spadrille]

I'm sorry to ask a question not related to Qlab but since you appears to Flic's OSC capabilities very well, i have something to ask. I would like to use Flic to  power up on a digital mixer (Behringer X32) and then move some faders up or down. Flic is compatible with Homekit, so i can use Homekit to turn the digital mixer on with a smart plug. And since Flic can send OSC messages, it can send as OSC message to the digital mixer to move the faders. But, i have 2 questions :

       - Can the flic button be at the same time trigger a device via Homekit AND send an OSC message? 

       - Is it possible to have a delay before sending the OSC message? Because the digital mixer need some time to boot (a few seconds) before being able to receive any OSC message. What i need is that pushing the button first trigger the associated smart plug in Homekit and then, a few seconds later, send an OSC message to the X32. Does it seem possible?

[m...@stevensokulski.com]

Hiya,

The Flic does support chaining actions, so you can set the "single click" action to activate a HomeKit scene and then send an OSC commands to the mixer.

However, I don't think you can establish a delay between the two. In my experience, the X32 takes a couple seconds from when you "flip the switch" (or turn on the outlet in your case) before it will respond to input.

Also of note: To make the button HomeKit compatible you'll need the hub.

[Patrick Spadrille]

Thank you for your answer. I still have 2 questions. Can I also use a fixed iPhone as a hub to connect to HomeKit? Can I add a bunch of “fake actions” to simulate the delay I need between the smart plug and the OSC command?

[Steven Sokulski]

Can I also use a fixed iPhone as a hub to connect to HomeKit?

Sadly, I don’t think so. I do a fair bit of tinkering with HomeKit devices, Homebridge translation, etc. and iOS apps aren’t able to emulate HomeKit devices at this time without the help of a separate device.

They potentially could’ve made the buttons themselves pair to Apple TVs or HomePods, but that’s not something the end user could do.

Can I add a bunch of “fake actions” to simulate the delay I need between the smart plug and the OSC command?

I don’t know enough about this to answer that, sorry.

On Feb 17, 2021, at 9:20 PM, Patrick Spadrille <patrick....@gmail.com> wrote:

Thank you for your answer. I still have 2 questions. Can I also use a fixed iPhone as a hub to connect to HomeKit? Can I add a bunch of “fake actions” to simulate the delay I need between the smart plug and the OSC command?

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/T33bUDooLy0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/7f74bcc2-f622-43b9-a147-dd271f87e20c%40Spark.

[Patrick Spadrille]

I will have to experiment when i receive my first Flic buttons. 

Since you know very well Homekit, do you know any way to make Qlab control Homekit? I'm exeprimenting with the OSC plugin for Homebridge but so far, without any luck. Have you try such a solution or another?

[Steven Sokulski]

I’m sorry to say I haven’t had occasion to use OSC around the house. You might try opening an issue on the GitHub repo for the plugin.

I use a particular plugin for my garage door opener and that developer has been amazingly receptive with support and feedback. Maybe you’ll have similar luck.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/673d481d-0184-462f-b256-cf61735e129fn%40googlegroups.com.

[Svante Axbacke]

Would it be possible to use the Flic Hub to send messages over the network? I'm thinking about if I want to send message where there is quite a distance between the button and the Qlab computer, it could be nice to have a little hub close to the button instead of a full computer.

/Svante

[Erik Rosales]

Hi there Svante! Please pass this information to the Flic crew... I have presented this idea to the crew. But I guess they work on things that will benefit the largest amount of people... With that said. I more people articulate this need maybe they will make it happen : )

/Erik

[Magnus Aaen]

Hi all.

Magnus from Nationaltheatret Norway here.

I have now used several flic buttons paired to the flicHUB to send osc messages to QLab, so the actors can trigger their own sound-cues.

Never failed after a little programming help from our good saint over at the flic HQ.

They wrote a script to put into the flicHUB, and I have modified it to my needs. Mainly telling the hub to send an osc message to QLab whenever it is pushed.

The hub is connected to the network and is placed approx. 20 meters away from the buttons I use. Even with a full hous of 700+ people, no trubble with connection.

In my most recent show (premiere next week), I use three buttons. 

One placed on an old phone, for the actor to push when answering the phone, so the ringing stops. (All handled by QLab.

The second one is placed on a "mechanincal" bird, with a wireless reciever and a small speaker inside, so that when the actor pushes the button, the bird sings (and fades over to the main speaker system).

The third one is used by a actor who "spits" cherry stones into a bowl, and he pushes the button when the "stone" hits the bowl.

/Magnus

[sir...@gmail.com]

Cool setup, Magnus! I'm happy it works so well for you!

I got an interview with the Flic crew about the way I use their button. You can read about it here:

https://flic.io/blog/combining-art-and-tech-an-interview-with-erik-rosales

Now I'm looking forward to seeing how to use their new Flic Twist. Right now, it's not good for my needs, but I have their attention. So, things might change with new features that work within a theater/show setup :)

/Erik

[Thomas Dam Jensen]

The Flic buttons appear very smart, and I can envision numerous beneficial applications for theater use. However, if anyone is in need of a wireless controller for QLab with range up to 1000m (line of sight), you might want to check out the SchwiftyBox WRC. This is admittedly a direct promotion, as I manufacture them myself. They function as wireless MIDI controllers and are specifically designed for use with QLab. The handheld remote, though a bit larger than a Flic button, has 8 buttons, and can also function as a foot-controller.

Thomas.

[Ryan Joyner]

Hi Magnus! I have a Flic and LR Hub set up and configured through the SDK to send an OSC message to QLab. It all works great...but only once. Since you have been using this same method, I thought you might have run into something similar. My code is super simple:

Any thoughts on why it would only trigger once? 

To clarify, the button blinks when I press it, triggers the sound effect, then the hub seems to no longer listen for another "buttonDown" event. When pressed a second time, the button blinks, the hub blinks, but no message is sent to the log or any other indication that it "heard" the buttonDown event.

Cheers,

Ryan Joyner

[Magnus Aaen]

Hello Ryan!

This notice got caught in my spam filter. So sorry for the late reply.

I can have a look on this on monday, when I'm back at work.

Have you tried numbering your cue i QLab, and have the flicHub send the message cue/1/go (if you number it 1).

I have'nt tried with other messages than the cue/(number)/go.

Good luck, and i'll get back to you on monday.

Magnus

--
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 a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/T33bUDooLy0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/d702a299-1c70-40e9-8bb3-b1b9c52cccbcn%40googlegroups.com.

[Ryan Joyner]

Hi Magnus,

I have in fact tried that, haha. Unfortunately, the cue does work, but only the one time. It will only work AGAIN if I either use the SDK to toggle the stop/start button again OR if I reboot the LR Hub.

However, as I was writing this, Flic responded to my topic on their community page and released a 4.3.5 firmware update to address the issue. All seems to be resolved.

That said, I am getting a bit of variation in the lag between pressing the button and the cue firing. Any tips for mitigating that? I don't mind a tiny bit of lag, if it's consistent...

Cheers,

Ryan 

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/CAOrSppUq%3DhE5HD4cYwFyqv744TvNMXAXKOuUWKGY_Dd5MSiekg%40mail.gmail.com.

[Magnus Aaen]

Yeah, i remember we had trouble with old firmware as well.

Whats the distance between the button and the hub? I noticed last time, that if my body was between the button an the hub, and I also hid the button in my hand, and walked approx 15 meters away from the hub, it lagged.
So maybe try to get the hub closer to the button?

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/CABHk2W5_Kj-ZpZEh4trU0yaiJqKWybpwnJtwZpQ8oxE-hin49Q%40mail.gmail.com.

[Magnus Aaen]

 

 

Hi Ryan!

 

Hope the issues got resolved.

 

My script look like this :

 

// main.js

var ip = "10.115.136.158";

var port = 53000;

var oscClient = require("./osc").create(ip, port);

var buttonManager = require("buttons");

var knapp1 = "BH39-D08515";

var cue1 = "/cue/200/go";

var knapp2 = "BH39-D09088";

var cue2 = "/cue/201/go";

var knapp3 = "BH39-D09221";

var cue3 = "/cue/202/go";

var c = 0;

 

buttonManager.on("buttonDown", function(obj) {

        var button = buttonManager.getButton(obj.bdaddr);

        c++;

        console.log("Knapp " + button.serialNumber + " down #"+c);

 

        //knapp 1

        if (button.serialNumber == knapp1){

        oscClient.send(cue1, function() {

                console.log("Sendte " + cue1 + " til " + ip + ":" + port);

        });

                }

 

        //knapp 2

        if (button.serialNumber == knapp2){

        oscClient.send(cue2, function() {

                console.log("Sendte " + cue2 + " til " + ip + ":" + port);

        });

                }

               

        //knapp 3

        if (button.serialNumber == knapp3){

        oscClient.send(cue2, function() {

                console.log("Sendte " + cue3 + " til " + ip + ":" + port);

        });

                }

       

     

});

 

I had no issues with this, it always works and I had no trouble using more buttons than these three in this project.

 

The var c = 0 function is just to count how many times the button got pressed. This was because it crashed after 30-something presses in an early firmware.

I just didn’t bother to remove it.

 

Fra: Magnus Aaen <magnu...@gmail.com>
Dato: fredag, 13. september 2024 kl. 23:53
Til: ql...@googlegroups.com <ql...@googlegroups.com>
Emne: Re: [QLab] Re: -->EXTRA : New wireless controller for QLab : EXTRA<--

Yeah, i remember we had trouble with old firmware as well.

Whats the distance between the button and the hub? I noticed last time, that if my body was between the button an the hub, and I also hid the button in my hand, and walked approx 15 meters away from the hub, it lagged.
So maybe try to get the hub closer to the button?

 

fre. 13. sep. 2024, 22:43 skrev Ryan Joyner <ryanswi...@gmail.com>:

Hi Magnus,

I have in fact tried that, haha. Unfortunately, the cue does work, but only the one time. It will only work AGAIN if I either use the SDK to toggle the stop/start button again OR if I reboot the LR Hub.

 

However, as I was writing this, Flic responded to my topic on their community page and released a 4.3.5 firmware update to address the issue. All seems to be resolved.

That said, I am getting a bit of variation in the lag between pressing the button and the cue firing. Any tips for mitigating that? I don't mind a tiny bit of lag, if it's consistent...

 

Cheers,

 

Ryan 

 

On Fri, Sep 13, 2024 at 1:32 PM Magnus Aaen <magnu...@gmail.com> wrote:

Hello Ryan!

This notice got caught in my spam filter. So sorry for the late reply.

 

I can have a look on this on monday, when I'm back at work.

 

Have you tried numbering your cue i QLab, and have the flicHub send the message cue/1/go (if you number it 1).

 

I have'nt tried with other messages than the cue/(number)/go.

 

Good luck, and i'll get back to you on monday.

 

Magnus

 

 

man. 9. sep. 2024, 23:18 skrev Ryan Joyner <ryanswi...@gmail.com>:

Hi Magnus! I have a Flic and LR Hub set up and configured through the SDK to send an OSC message to QLab. It all works great...but only once. Since you have been using this same method, I thought you might have run into something similar. My code is super simple:

 

 

So now the button can send OSC messenger across any network! 

 

They've also added a super low latency mode so that all the clicks are reacting with zero lag. And now you can monitor the Flic battery status, so that you won't start a show with low battery,,,

 

[Christoph Hintermüller]

Hi there,

I run a small show production in Germany and have been using QLab for five or six years now. Recently, I started integrating Flic buttons to control QLab, which has been working well so far.

The threat here was really helpful! 

1. Let’s say I have a list with two cues. When I send the command /go, the first cue starts as expected. However, when I send the same command again, the second cue starts, but the first cue is stopped automatically. Ideally, the first cue should continue running.

2. If there’s a third cue and I send the /go command again, the second cue stops abruptly. There are no active triggers in QLab, so I’m unsure why this is happening.

Additionally, I noticed a strange behavior when adding a second Flic button to the hub. Even though the second button has no assigned functions, it somehow stops all running cues when pressed. This doesn’t make sense since it’s unprogrammed.

Do you have any insights into what might be causing these issues? Your guidance would be greatly appreciated.

Looking forward to hearing from you.

Best regards,
Christoph

[Magnus Aaen]

Hello.

This sounds strange. 

I've only used the flic to trigger specific cues, and have not had that problem when using it that way.

Maybe you should reach out to figure53 or the makers of flic? 

They are usually fast to answer!

Magnus

To view this discussion visit https://groups.google.com/d/msgid/qlab/7ed24161-63d4-4167-aa77-0ab77fe5c93en%40googlegroups.com.