Thanks for the report 
I've never used a Loupedeck, but I'm a big fan of my Streamdeck (which I use every day). I like it for many of the same reasons, it's super easy to configure. I don't think I ever needed to hit the manual/documentation to figure out how to do anything; from launching webpages to triggering Isadora with OSC and from making pages to setting custom icons and text for different buttons, it was all just very apparent how to do it.
Hello,
I just wanted to post a couple of observations about the Loupedeck Live Controller vs the Stream Deck+ controller.
After doing a bunch of work on the Isadora side to work with the Loupedeck, I found that programming the Loupedeck controller is show-stoppingly difficult. You can't drag buttons, you can't copy/paste buttons on the interface, and you can't use CTRL+C and CTRL+V to copy and paste "Custom actions" in the actions bar. When you copy/paste actions, you have to use a menu, and then the screen scrolls back to the top, so you have to scroll down to get to the pasted action. In addition, the MIDI plugin is adequate but not very flexible. Also, you can't easily display dynamic information or toggle button states. Editing actions involves lots of scrolling and clicking, and adding custom icons requires several layers of interface to click through - it's not drag and drop.
Having used the Stream Deck in the past, I assumed that configuring the controller on the Loupedeck would be similar. I absolutely love the Loupedeck hardware, but with 800+ buttons to program, the software is a show stopper for me. If I were doing just a few pages, I think I would stick with it, but instead, I picked up a couple of Stream Deck+ consoles to replace it.
The Stream Deck software allows for copying of buttons, moving buttons, easily switching between profiles... it takes me a tenth or less of the time to configure a page. The UI is really designed for quick configuration of buttons and dials. What's extra excellent is the MIDI plugin. While it's not perfect, it's very configurable and allows custom scripting that enables the execution of any number of MIDI commands/notes, etc., and also allows displaying dynamic text and graphic information on each button. It allows for very rich programming of the interface.
I'm using a Stream Deck XL to trigger clips, so it's also helpful to have everything under one piece of software.
yeah I tried your request
"If you leave the 3 screens connected and active stages in Isadora but play the video on one screen does is still give the error. Can you try this for each screen (send a test signal via Isadora to the other screens)"
and sadly the same problems
nice thought though
G
@dusx Thank-you. I am always happy to hear about different ways of doing things incase one method does not suit the patch.
I am not sure what you need to send and in what format, but an older tutorial I write might be helpful to you.
see: Using data from web APIs in Isadora: part 1 (dusxproductions.com)
Feel free to open a support request, and we can look into your issue for you. (link in my signature)
@jtsteph said:
And just to confirm here, the output from the JSON Parser is always text? I am using the Text Parser to change the data type to integer currently. Is this best practice?
Yes, JSON is text, and the data is untyped. Text Parser is a good choice to use, You can also pass the 'text' number into a JS actor, and simply pass if back out with out modification, the JS actor will allow you to mutate the value to a number. It sounds like you have it working well though.