Welcome back to Isadora!
Isadora 3.0.8 is compatible with macOS Big Sur (11.7.6)
You can find the installer on our Get it page
https://troikatronix.com/get-i...
Please be aware that they are separate installers for USB Key edition and the standard edition.
Isadora 2.x licenses can not be used with Isadora 3.x, since you mentioned that you are using a USB key license you need to update your license key thru our online store.
https://sites.fastspring.com/t...
Currently we offer the update from Isadora 2.x to Isadora 3.x for 170 EURO, if you first want to see or Isadora 3.x is worth the investment you can always do so in Demo mode (without saving) or buy a temporary rental license so that you can at least saves your files.
If you need any assistance with this process feel free to sent us a Support request and our sales team will give you a hand 
You can reach them by sending them a support ticket.
https://support.troikatronix.c...
Please be aware that our support team can be reached during office hours.
Thanks!
- Juriaan
Hi there @Niek-0
Would love to know or the reply from @DusX resolved your query, if not feel free to let us know.
Welcome to the Isadora community forum!
You can use an Orbbec Astra on a MacStudio M2, with our OpenNI plugins which can be found here
https://troikatronix.com/add-o...
Please be aware that Isadora needs to run in Rosetta mode and that it is very important that you read the README files that come with the plugin.
From there you can sent out all the data using OSC / sent the video image out using Syphon or NDI
Well I was certainly making things more complex than I needed to. I ended up using the controller's toggle function, storing all controller values in the JSON and when recalling the JSON sending the controller values back to the controller. This activates the toggle and will set the effects to the correct state...when I get to that stage of the build.
KISS principal applied.
Just quick update on this. The JSON Bundler always seem to revert to object when I open my project. I have worked around this by including a "trigger text" actor to send a "key" to the jason bundler as a part of the scene initialization. This resets it to object. I'll see if this works moving forward, if not, I will use @DusX 's javascript option.
Definitely having issues with the bundler and unpredicably switching to "array". I am going to pivot to dusx's javascript method. Here is what i did to be able to add a custom key to the json values so i can use the isadora JSON Parser actor:
--------------
// input 1 (index 0) is the custom string for the key. The loop begins at 1 as opposed to 0
function main() {
var customString = arguments[0]; // takes custom key string from input 1
var output = {};
for (var i = 1; i < arguments.length; i++) {
// Creating a new key with custom string and index
var key = customString + i;
output[key] = arguments[i];
}
return JSON.stringify(output);
}
I just discovered, they already support the Loupdeck officially, as well as several other interfaces.
I don't use the original Software, so I can't compare. You can copy/move buttons between positions and pages. But only one at a time. But there is an export/import function, which can be used as a workaround to move whole pages.
The page up/down buttons can be moved and removed freely, and there is an internal button function to jump straight to a specific page.
The plugin link I gave you, was probably misinterpreted by me. It is a Loupdeck plugin which enables the Loup software to use the companion functionality (both softwares have to be running). There is a Streamdeck version as well. This way you use the original software for programming as usual, but implement companion buttons programmed in companion.
The plugins use the remote interface / API of companion, which enables remote control by several protocols, like OSC, ArtNet, etc. This way you can easily trigger buttons from a different device (e.g. a computer running Isadora, sending OSC to companion, triggering a button which shuts the light via Home Assistant or ESP). There even is a Web remote interface which emulates the physical interface in a remote web browser.
The companion open source community is very active and as it is used a lot in professional live media/ event productions, there already is a long list of of modules (called connections) with specific support for software and hardware devices.
I personally use the raspberry version with a pi 4b which is connected headless to the network, as a multi device remote interface. With a PoE+ HAT you even don't need a PSU anymore, or you go wireless with a Powerbank. (this isn't mine, but there are several examples for companion pi).
Javascript for the initial win. I did this and it works. I will see if I can do it with actors now. t_flag = toggle flag and v_out = value out. I wonder if it will hamper performance if I have hundreds of these. Do they only activate on changes or are they always running?
Oops spoke too soon. This will not turn the toggle off and on. More work!
// iz_input 1 "value"
// iz_input 2 "t_flag"
// iz_output 1 "output 1"
function main()
{
let v_out = arguments[0];
let t_flag = arguments[1];
if (v_out==127 && t_flag ==1) {
v_out=127;}
else {
v_out=0; }
if (t_flag == 0){
v_out=arguments[0];}
return v_out;
}
J
@dillthekraut Oh wow. Companion looks super cool. I am going to investigate further. I like that it is opensource. How do you find building multi-page interfaces? Is is easier to work with than streamdeck?
@dillthekraut said:
Have you tried it with companion?
No. I will look into it though. I am trying to make a build right now that I can live with for a few years. I ended up putting the Loupedeck up for sale and replaced it with a couple of Streamdeck+ controllers. They're super easy to program. The midi plugin for Streamdeck is pretty great and flexible.
Have you tried it with companion? There is an unofficial plugin which implements limited support for the Loup.
I don't own a Loup, but use Streamdecks with companion.
There is an open request for official support for the Loup. Maybe some day...