@quarterinchjack said:
My gut feeling is that I would need to dissect that original model and pull apart the separate limbs to be imported as a replacement for the pipe model - is that correct?
Yes, that is correct.
My gut feeling is that JavaScript is less work for the computer, but as @Juriaan said, I don't believe there's a "one-size-fits-all" answer in that it probably depends on the complexity of what you're doing and how you're doing it.
@DusX might know better than me.
@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): 3333
- OSC 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): 53000
- OSC OUT (OSC port for sending OSC to Isadora and other applications): 3333
Hi all,
This question relates to the excellent Guru Session #19 that Mark presented in 2021 that looked at skeleton tracking with a Rokoko suit. During the session he used a figure made from a simple 3d pipe model and explained how to replace that pipe with any other 3d model to hand. My question is can I use a fully formed pre-rendered human figure (made in Blender) instead of the figure made from the individual pipes? My gut feeling is that I would need to dissect that original model and pull apart the separate limbs to be imported as a replacement for the pipe model - is that correct?
Thanks for any help.
Andy
@woland Just to add my two cents, I have had an equivalent experience with the pjlink actor. Every time I use a "Enter Scene Trigger" with a "Send PJLink" Actor, Isadora crashes. I will upload a crash report when I am out of the theater. I currently am outsourcing it via Companion.
(additionally, when I am using the Send PJLink actor, Isadora stops being able to receive OSC commands. Before it gets triggered, everything works well. After it is triggered, nothing responds. I have had to shut down Isadora and redo stream communication to get OSC commands back into Isadora. I don't know if there is an actual causal relationship between these two things but in the heat of the moment, they feel connected)
I am wondering if anyone could point me in the right direction for a bit of logic I am trying to build for a video player module.
I would like to build a "Keep only one button on" latching strategy. I have many buttons on a streamdeck controller over many pages and would like only one of them to be on at a time. As an example, I might press Page2/Button4, toggling/latching it ON, and at a later point Page6/Button13. I would like the new Page6/Button13 press to trigger a 0 on the previous button and send the new ON to my player module.
I am using a cleanly laid out JSON to store all the midi values currently for snapshots and to easily pass value between modules.
My JSON looks something like this where xlp is the streamdeck page and xlb is the streamdeck button: {"xlp2":"{\"xlb1\":0,\"xlb2\":0,\"xlb3\":0,\ up to "xlb32"}","xlp3":"{\"xlb1\":0,\"xlb2\":0,\"xlb3\":0,\up to "xlb32"} continue with the same pattern to "xlp9".
Is there a way to store the location of last ON value (from the example, xlp2/xlb4) then change that value to 0 (off) on the new button press (for example xlp/xlb13), trigger an event to indicate the change, store and send the new ON to my player module?
I've thought about creating a flag in the JSON which would indicate the key from which the "ON" is located and then working with a comparator, I also looked at @dusx's multi toggler which uses javascript, but it does not seem like a fit for this problem.
Maybe I am overcomplicating this?
I am working with the developer at Trevliga Spel (he developed the excellent Streamdeck Midi Plugin) to try scripting this directly in the Streamdeck midi plugin, but thought I would try something in isadora, too.
Any leads would be appreciated.
Thanks, J
Happy to dive deeper with you, but I dont have an answer for you at this moment.
Will do some testing on my own and report back
@juriaan Ahaha. Understood. I thought it might be a simple answer. I know you have much more important things to do. I will just try some stuff and see where I end up. Thanks for reponding.
It depends on the amount of replications and this is such a deep technical question that we really have to dive deep into the codebase to figure this out for you 
For example I dont know or JavaScript code that is in memory needs to be re-initiliazed.
@woland thanks for this. I've got OSC>OSB working on my Mac but when I try to run it on a PC (which will be used for the installation) the messages are not getting through.
I've set the OSC port in Isadora Prefs to 3333
When the osc is sent using your user actor the OSC out in Isadora UI flashes
I've got the connection from OSC>OSB app working with a green light indicator in the UI
Enable Websocket server enabled in OBS Tools>Websocket Server Settings
Any thoughts on what I've missed?
Many thanks
Simon