Thanks for publishing the solution. It worked in my case also to downgrade the AMD driver version to Adrenalin 24.3.1. Just a question: Do we have here an AMD problem or is Isadora's detection of the OpenGL version incorrect? The information in the Isadora popup indicates some discrepancy between the information the hardware info delivers and the detection of Isadora's startup routine.

Anyway, it works. I turned off the AMD update detection and hope not to get issues in other software.

gunther

Hardware: AMD Ryzen 7 8700 w/ Radeon 780M Graphics 4.20 GHz, 32 GB RAM, Win10

@woland thanks for your quick reply. It's been some time since I've done the virtual audio routing. Is there a resource for best practices? On Mac

@chaoticboophe said:

Is isadora the right software to manage this or should I be using something else?

Isadora is great at being the glue that connects a bunch of things together.

@davidcoll said:

I'm hoping for something more straightforward than some routing/mixing kind of thing with soundflower or the like. 

Unfortunately no. The sound analysis actors (Sound Level, Sound Frequency, and Sound Frequency Bands actors) only work with audio coming in through Live Capture, not audio being output by Isadora, so you'd need to use virtual audio routing to bring that output audio back into Live Capture for audio analysis.

@webmammuth

Ask and ye shall receive.

Gif: https://jmp.sh/IzN83Di1

File Download: control-panel-control-panel-recording-indicator-2024-12-12-4.0.2.izz

Screenshot:

P.S. @mark I love the Show-Hide Control actor. It makes so many new things possible to achieve in a very easy and elegant way 

@gapworks said:

Speed Change and reverse mode. Any help highly appreciated ! I need it by tmw.

 I don't have time to do it for you by tomorrow, but I've actually had a large amount of success workshopping GLSL Shaders with ChatGPT. If you copy the GLSL Shader code into there, tell it you want additional inputs, tell it what you want those inputs to do, and tell it to match the special formatting used for GLSL Shaders in Isadora by feeding it the following text from part 3 of the TroikaTronix GLSL Shader Tutorial:

The really exciting opportunity offered by the GLSL Shader actor is the ability to manipulate shader parameters in real time. Shaders accept real-time input through a mechanism known as uniform variables. For example, if you wanted the shader to receive a floating point number, you would add a line like this.
uniform float myVariableName;
This defines a floating point number called myVariableName as an input. Then, you would use that variable in your code as needed. The trick here is to make that variable available to you as an input to the GLSL Shader actor. This is achieved using a special comment line that you add to the shader like this
// ISADORA_FLOAT_PARAM(name, id, min, max, default, "help text");
In OpenGL Shader Language, any line that starts with "//" is a considered to be a comment; in other words, it is ignored by the compiler. But it is not ignored by Isadora. Using comments like the one above, you can create an input for the GLSL Shader actor that sends it's value to a uniform variable in the shader
Let's go though each part of this special comment in detail
// ISADORA_FLOAT_PARAM — This portion simply identified what kind of parameter is being defined. In this case, single floating point number.
name — This is where you define the name of the variable. This name must exactly correspond to the variable name given in the uniform variable — statement in the shader code. You cannot include spaces in this name; if you need a space, use the underscore (_) character instead.
id — This identifier, which can be from 1 to 4 characters long, uniquely identifies the input. Should you re-arrange the order of the inputs, Isadora uses this identifier to ensure the links to that input are maintained. For each shader program, this identifier must be unique.
min — For numeric parameters, this defines the minimum possible value for the input.
max — For numeric parameters, this defines the maximum possible value for the input.
default — For numeric parameters, this defines the the default value for this input when the actor is added to the scene. This input is only meaningful if you add the source code for this shader to the Isadora's GLSL Plugins file. (More on this feature later.)
"help text" — This defines the help text that will appear in the information view for this input. If you share your shader code, you can help those who use it by providing useful, descriptive information about this input. Isadora's philosophy has always been to make it easy for the user to use the program; giving useful details in the help text supports that philosophy.

Hello,
I'd like to have a big light in the controls saying "RECORDING" when record stage is ON.
Is there a way to do this ?
Just a simple indicator light...

Is there an actor that can get me these numbers? I'm hoping for something more straightforward than some routing/mixing kind of thing with soundflower or the like. 

@chaoticboophe

Regarding Projection mapping; checkout IzzyMap (a feature within the program)

@chaoticboophe

Hi Chaotic! Welcome to the Isadora community

Regarding NFC: You can use a Arduino with our Firmata actor or a simple OSC signal trigger to communicate to Isadora. Isadora can then handle the sequences.

Regarding handling different systems; Isadora supports OSC / MIDI / TCP / and even more if you use our Python or JavaScript actors to communicate to an different system.

Abelton could be a MIDI > MIDI or a OSC > OSC connection. 

Mocap; We support natively the Rokoko SmartSuits (https://www.rokoko.com/), including Gloves in an upcoming update of the product.

You can use Isadora in Demo mode for free, the only limitation is that you can't save. We have cheap 1 week / 1 month rentals which you can find here:
https://fastspringstore.troikatronix.com/