Hi Folks,

Just a wee advert to say that we're performing our Isadora Powered Show "Natalie Inside Out" at UP festival in Brussels next month, March 2024. Come and see it, come and say hello, come and hear me speak french like the vache espagnol!

https://upupup.be/show/natalie...

@quarterinchjack said:

I don't suppose you know of a way to package that up as a skeleton output that the decoder would recognise?

Unfortunately, it is not currently possible to programmatically create data with the special type "skeleton".

@dillthekraut said:

Mutable values (the ones with the green connectors) take the ranges from the actor values you connect them to

It sounds like this to me too. The Set and Get Global Values actors' 'value #' inputs/outputs start with a default range of "MIN" and "MAX". They can only have a set range if they're manually given one through a user setting a range via the Property Inspector or if they're connected to an input/output of another actor that has a set range. Perhaps a manual range was set for one instance of a Get Global Values actor that you were using for something, then you copied it and used it somewhere else.

It's worth saying that if you disconnect a mutable actor from the actors around it, right-click it, then select "Reset to Default Values" it'll set the ranges back to the default.  Another tip I'll give is that you can select the links connected to your mutable actor and use Actors > Detach Link at Input and Actors > Detach Link at Output to just take the links connected to a mutable actor and "store" them temporarily by attaching them to a random Gate actor or something, then you can free up your mutable actor, reset its values to default, then re-instate its connections using Actors > Detach Link at Input and Actors > Detach Link at Output to take them back from the "storage" Gates.

@miketutaj

Thanks for offering to share your workaround. It would be wonderful if you could post the file here for others to use if/when they run across this thread.

@jtoenjes said:

this behavior seems to be particular to Oculus screen cast

 There might not be anything we can do about it then, unfortunately 😞

@fred Thanks for this. I have to wrap my head around it since I'm not a programmer...

@simon said:

I've set the OSC port in Isadora Prefs to 3333

 I believe this is your problem.

In the screenshot, you've got the OSC IN port on OBS for OSC as 3333 and OSC OUT port as 53000.

The port in Isadora Preferences is the port on which Isadora receives OSC so I think you've got your ports switched in OSC for OBS, meaning both applications are listening on port 3333.

I think these should be your settings:

ISADORA
Isadora Preferences OSC Port (OSC port for Isadora to receive OSC from OSC for OBS and other applications): 3333OSC Transmit Actors (OSC port for Isadora to send OSC to OSC for OBS and other applications): 53000

OSC for OBS

OSC IN (OSC port for receiving OSC from Isadora and other applications): 53000OSC OUT (OSC port for sending OSC to Isadora and other applications): 3333

@woland Amazing resource! Thanks SO much...  - John

@woland Thank you! Just want I needed! Thanks - FAS

@jtsteph said:

This is going to be particularly helpful when it comes time to build logic for cycling or shuffling clips in banks.

 Yay! I love being helpful 🙂

@dusx Thanks. I did add a very small delay to the envelope generators and that seemed to make a positive difference. I tested many variations of with and without auto fader... the added delay has basically fixed this problem. Setting the initial conditions when opening the patch is my next task. It's a bit bizarre when first starting up, though I bet that's the auto fader doing its thing.  Thanks again. The same patch has produced another set of questions and I will post them separately.  - John

@nic

As mentioned in the other thread, we do not support the Azure at this time and it's also not on the list of things we're trying to put in place in the near future. It would be nice to have everything, but unfortunately we don't have the resources to do that, so we have to prioritize other features right now.

Best wishes,

Woland

It would be helpful, in the preferences/general tab, to have the option to pull thumbnails from the middle of a clip. I have many clips that start black and then an animation begins. The thumbnail currently show these as just black frames.

@acmsinclair

Look into GLSL Shaders

hi guys,

is anybody here has managed to re-create the old 32bit freefame plug-in "Luma Offset" (which was in the Pete's Plug-ins add on folder)?

or do you know a shader or a FFGL wich could reproduce its behaviour?

thanks a lot if you have a solution...

@woland

But i've found it!

In this isadora setup i can control tow leds on the arduino.

The code is in the next picture. Now to the next step, but the communication is there!

@woland. Thanks for letting me know. I sketched something in using the in-range actor that's working. I'll clean it up and use that.

@woland. "Voila" - so much simpler.... thanx

AMAZING. I cannot tell you how much time this will save me as I work through my midi controller patches. I am half done and it has been a slog tracing connections. As always, I really appreciate your input and expertise.

@jtsteph

They'll be replaced automatically, but if you're interested in using the beta version right off the bat, feel free to send in a ticket using the link in my signature and I'll send you the form to sign.

Best wishes,

Woland