@fred

Thanks, @fred. I have an implementation of MediaPipe constructed using the Isadora Pythoner beta module. However, as the version of Isadora with Pythoner has yet to be released, these options provide an alternative. I will have a look at PoseOSC, too.

Best Wishes

Russell

@Armando OH MY GOD !!!! I tried to connect a broadcaster to skeleton output property of the rokokko actor and putting a listener in data mode and it works ! It is just that listener type must t be set on data. when like that its value output becomes "skeleton" if attached to a skeleton decoder. The only confusing part is that the broadcaster value input doesn't show data not skeleton but just three dashes ! It works !!!!

Link to video

@woland

Thank you for your time. I had installed the patch you mentioned. v1.0.1

What I found was the problem to be was - in the Isadora Plugins Folder, under the properties for the RokokoStudio Live Watcher, Skelton Decoder etc, the various .dll and .qtr files, their Attributes had been blocked by Windows 10 because "it was downloaded from another computer". I checked  on the unblock option and hit apply and - magic -  they are talking to each other. 

Big thanks Isadora Community. 

As an aside Rokoko tech support advised to use Json in Rokoko's Livestreaming. That was wrong for me. JsonLz4 worked not Json.They also advised to avoid Mac.....??

Thanks Again

@juriaan Thanks. Too bad the 8 fader is sold out.... Great find !

@mr_j
Hi there Mr_j!

Was just about to ask the same. Sorry that I couldn't chime in before!
Let us know if you have any follow up questions.

- Juriaan

@juriaan For the sake of leaving a concrete example:

Imagine I have two pieces of software or hardware, maybe two x32 sound boards, and I want to have bidirectional control of each (maybe if I move a fader on one board, it moves the corresponding fader on the other). Both boards, being identical, obviously use the same OSC API (same OSC addresses, same payloads). If we point both boards at Isadora port 1234, Isadora's channel system has no way of telling us which packet came from which board. It makes it impossible to build this solution unless an intermediary piece of software, or multiple Isadora files on different IPs, are used. 

A simple OSC Direct Receive actor would go a long way. I've spoken with Mark before about how I would imagine it working, including OSC Wildcard syntax, where the actor could lean into the tree syntax of OSC and be given partial or complete address filters to receive info. But even just starting with direct receive on a given port would be very helpful.

Hi,

I searched a couple of days for answers/sample code that would get the Isadora OSC Multi Transmit module to work with a Nodemcu wireless microcontroller as the receiver. I had no luck finding any answers online, with many user group comments suggesting that the OSC Bundle method would not work with the Nodemcu at all. Perhaps those comments were old and things have been updated since. I did manage to program the Nodemcu to function with the OSC Multi Transmit in Isadora and to run multiple servo motors and RGB leds from a single OSC actor. I first made everything work with individual OSC Messages, however with six servos and nine channels of RGB Led going to my prototype it was just not performing well and I somehow knew that I could get something better with OSC Multi Transmit... and I did! 

As it appears there is so little by way of examples and information, I thought it might be useful to make some example resources available here. I used the Arduino IDE to format the Nodemcu code and upload it to the device. There are a number of tutorials for setting up a Nodemcu development board with Arduino IDE - like this one. So if you get that far and then are looking for an example patch with Arduino code, this might help. It has solution for servo and PWM channels and it is a prototype code available to anyone who wants to modify it.

isadora-gt-osc-gt-nodemcu.zip

Best wishes

Russell

A user over on the Facebook Group posted a video of actors sitting on a couch in front of a screen, with a projection of their words seemingly falling from the sky as they were spoken. As many of the comments identified, an easy way to get this effect accomplished in Isadora is to prebake the asset or even draw the words with Text Draw individually because, in scripted performance, the language (theoretically) is always the same. However, it got my wheels turning: is there a way to do this live, with improvised language? Turns out the answer is: yes!

There is a well-known speech recognition library for python, and I've become comfortable programming OSC into python scripts over the years, so I figured there would be a way to combine them to make it happen. Turns out, the folks over at Programming for People beat me to it, as they put out a YouTube tutorial of programming the functions a few years ago and sell a package of the source code and a Max interface for a few dollars on their website. I purchased the source code and began to tinker as it needed some updates to be compatible with current python versions, etc. I received a friendly email from the developer and after a brief exchange, we decided that I can redistribute my fork of their work free of charge, though I would encourage those of you who may end up using this to shoot a few dollars over their way in good will. 

As a result, here is OSCTranscribe! For those of you who want to tinker with the source code, you can follow that link to the git repository where I have the program hosted. Otherwise, you can grab the release for Windows 10 here.

When you run the program, it will print a list of all available audio devices it can bind to, and you just select the one you want to use. Then, you select the OSC network settings (defaults will be compatible with Isadora). Next, you use Isadora to send the following OSC commands via whatever triggers you want:

OSC API for Controlling OSCTranscribe:

/OSCTranscribe/calibrate {int thresh}: Setup, establishes the amount of quite space before processing

/OSCTranscribe/startListening: Setup, begins listening to the mic and sending to the learning system

/OSCTranscribe/stopListening: Stops listening to the mic and stops sending to the learning system

By default, you send these commands to port 7070. Then, you should listen for the following OSC message:

/OSCTranscribe/data {string text}: The words recognized from the audio stream in between pauses

Now, Isadora's OSC Multi Listener, set to Text mode, will deliver the spoken words as Text for you to pass to Text draws, formatters, Javascript, etc.

Here's a quick demo:

The recognition from the speech API is pretty good! Visually, a lot more tinkering could be done within Isadora to make this look more pleasing, but I will leave that to all of you to try out. Let me know what you think 🙂

Hi there @mclefferson, 

We would love to know or the suggestions that we gave you helped you out 🙂 If not, please feel free to send in a Technical support ticket.

https://support.troikatronix.c...

Thanks!

@dako-ark said:

obtain an output range of the signal from 0 to 100?

 OSC has a default range of 0 through 1.0 so the Limit-Scale Value actor needs to be told this initial range, and then the range to scale it to.
This looks like: 

Now, you should not be crashing when you move an actor around in your file, so please use the support link in my signature to submit a support request, and one of our tech team will assist you ASAP.

@dusx

yes thanks! I take good mark of this encouragement link;-)

I will feel more relax with the datas of the show stored in a text document,
if I need to change the patch after the scene progression has been recorded, it won't be a big deal to modify the architecture..

bests, 

@woland Super useful, thanks so much

@bennnid

for that purpose you can use the "Add password protection" in menu "File".

Here from the User Manual:

Saving Files as Run-Only

Isadora allows you to save your files as “run-only”, so that others can use the file but can only modify it specific ways. One place this might be useful is when Isadora is used to create installations that will be maintained by others. Making a document run-only means that only you will be able to modify the file.

Jean-François 

@liminal_andy

If you're comfortable sharing this, it'd be great to have a version of this on the TroikaTronix Add-Ons page (link in my signature) if it's not there already 🙂

Best wishes,

Woland

@peuclid

❤ 😉

While we love Zoom for all of the many settings it exposes to help us tailor our events, broadcasts, and live performances, it can be a bit overwhelming at times. In response, Jeff Widgren, the founder of Stream Sharks, has for the past several months been running an online Zoom support group called the Zoom Test Kitchen.

ZTK meets for several hours on Zoom twice a week, Tuesdays and Fridays, and is a space for Zoom users of any experience level or background to share questions, test their systems, and learn from experts about making the most of Zoom. It is, in my view, an essential resource for those looking to produce high quality work on Zoom. It's also a learning lab where I can test my apps, show files, and workflows in a helpful and friendly environment.

Zoom Test Kitchen can be found on facebook at www.facebook.com/zoomtestkitchen. See you there!

@liminal_andy said:

support for partial match on the address

 Yes, that is a great suggestion

Best WIshes

Russell

@liminal_andy said:

will bump to Group HD 720p for the duration of the call, even if the device leaves the call! 

 😄 That's a fun hack, thank you for sharing your knowledge here again!

After helping some others, I see that I didn't give info about how to set up ZoomOSC to work properly with this. Since it manages the user info based on ZoomID, and uses the /zoom/list command, you'll need a few settings in ZoomOSC turned on:

OSC Output Rate: (at least) 10ms

Galler tracking mode: TargetID

Here are my full settings to compare:

As a Dance tech guy I am amazed by what you have achieved Andy. Thanks !