@plzhelplol

And regarding your second question;

I use the 'Output' value; the output is either a 0 or a 1 (a number value), if you connect that to a true or false (a boolean value) it causes 0 = false and 1 = true

That way we don't need a Trigger value.

@fred said:

We hear you @Woland - the limited staff is the reason for the rate of progress - no spite - just offering a work around - have a great day!!

My apologies, I was a bit grumpy because I'd been at the office for around 34 hours straight when I read your comment yesterday (and then stayed for another five). Hope you have a great day too :)

Great! thanks for the help.

@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

I've got some things that I've made that should get you there (might have mentions of things that aren't specific to your use-case, like the last line of the Comment actor in the bottom right of the screenshot that mentions NDI):

audio-routing-explaination.izz

read-me-sound-routing-setup.zip

@woland
Oh!!! So Great !!!
Didn't knew this Show-Hide Control actor !
Thank you !! :)

@citizenjoe

That could be a nice approach. Each layer object having a blur setting. I think I can understand how that might work.

@wjmackwood

If you follow the instructions on pg 90 of the manual, you'll see that you can use the CueMix FX software to create groups of the individual channels - which you can match to the channels you're outputting from Isadora - which you can then control using the CueMix FX software OR the Master Volume knob on the MOTU.
That would solve your problem of outputting too high a level to the speaker, as you can then use the Master Volume knob on the MOTU (or the CueMix FX software) to control the master volume of your chosen channels. You can then refine the levels in Isadora, and not have to worry about setting the level of the sound player actor. Which you should not have to do anyhow, as there ought to be an overall level control from the Mac to the MOTU. As @JJHP3 suggests, not having control over volume is most unusual.

@shahaf if you go down the python route go pro have a pretty good SDK that is well documented and has some examples for low latency streaming over wifi.

Here is the SDK: https://github.com/gopro/OpenG...

Fred

@juriaan

@morfin_mafer

Please outline your audio routing (virtual cables, loops etc..)

And let us know how it is being recorded? To a file via record stage? Or something else.

@konrad said:

But now I'm missing the sound in the recorded stage video. Is there a way to get a stage video with sound?

Stages have no connection to sound, they are purely for video output.

If you want to capture audio and video output at the same time you could use OBS. You will need:

The free software OBS.This OSC-for-OBS User Actor of mine to start and stop the recording.The free software OSC-for-OBS. The free obs-websocket plugin for OBS (required for using the OSC-for-OBS software). 

(My notes on this are a few years old, but that's how I've done this before.)

@jhoepffner Always right on the spot, Jacques !

@smoon

As I wrote on the other post, the OpenNI Tutorial can be found here: https://troikatronix.com/add-ons/tutorial-openni-tracker/

It makes this puppet with the "Puppet Two Segments" User Actors shown in your screenshot. Double-click them to go inside and I believe you'll be able to find the 3D actor inside it responsible for rendering each segment's location using a specific 3d model, and you can then change the 3D Model being used by that User Actor by changing it in that User Actor and then closing the user actor and choosing "Save and Update All".

More about how to use User Actors (in general) can be found here: https://support.troikatronix.com/support/solutions/articles/13000091626-isadora-101-tutorial-11-creating-user-actors

Here's another 3d line puppet by the ever-fabulous @bonemap : https://troikatronix.com/add-ons/line-puppet/

@smoon said:

I am essentially trying to understand :

- how I get this sort of 3D visual from the visualiser 

- how to alter the aesthetic of this 

The Skeleton Visualizer actor can be used for a very basic form of this like so:

The aesthetic is changed by adding video effects like Motion Blur or Shimmer in the video actor chain (after the Skeleton Visualizer, but before the Projector actor): 

Alternatively, you could send all this to a Virtual Stage and use the Get Stage Image actor to pull it back in, then apply effects to it, then send it to a regular Stage via another Projector actor. (This would be useful if you wanted to get multiple skeleton sources all together in one place before you apply the effects):

More about using Stage Setup to create a Virtual Stage can be found here: https://support.troikatronix.com/support/solutions/articles/13000064618-isadora-3-quick-start-with-stage-setup

@woland @jfg I appear to get stable results by using Blackmagic Design UltraStudio Monitor 3G units in conjunction with its accompanying Desktop Video Setup: https://www.blackmagicdesign.com/uk/products/ultrastudio/techspecs/W-DLUS-13

Mac (Isadora Stage) ➔ Blackmagic Design UltraStudio Monitor 3G ➔ Projector / Screen

Hope this is helpful.

Best wishes

Simon

Thanks as ever for your prompt and thorough feedback!  Read Text from File works fine for what I need. I'll get into the other two patches in the next days and see what they're about. All the best from Montana

@chris122

This is a known issue that has not yet been fixed because there were more frequently occurring issues, (this cosmetic issue only comes into play when people have projects with hundreds of Scenes, which is not super common), and because there is a workaround for this.

To understand the workaround, you need to understand the root of the issue: The Scene list has a max horizontal pixel limit, so when you create enough Scenes you go over this limit and the additional Scenes past this limit in the Scene List no longer visually show up in the Scene List (though they do still exist and function properly otherwise).

Workaround: If you hold down cmd (macOS)/control (Windows) then click and drag the right edge of a Scene in the Scene List (the little horizontal bar of “tombstones” below the Scene Editor with the Scene Names), you can resize the Scenes to make them less wide. For every Scene you make thinner, you make the sum total of the horizontal size of your Scenes a bit smaller, meaning you free up additional pixels to show additional Scenes in the Scene List. 

Here's a gif of that in action: https://jmp.sh/wHggJeLk

Depending on your project:

- You may just be able to eliminate blank space on either side of some of your Scene Names

- In more extreme cases you may need to try to make your Scene Names as short as possible to minimize Scene width while still being able to read the Scene Names to tell the Scenes apart

- In the most extreme cases (and/or cases where you don’t care about being able to read the Scene Names in the Scene List) you can make the Scenes the minimum width (which will result in not being able to read the Scene Names) but in these cases you can still use the Scene Select control to see the Scene Names of previous, current, and upcoming Scenes as well as to navigate the Scene List. 

@konrad

You can use the search bar found above the Toolbin to search for all 'midi' actors, or double-click in the scene editor to open a quick-search to find required actors directly in the scene editor.

@johnhorzen

I don't know why this only showed up as unread for me today, but adding multiple displays to the same Stage can be done with the little "+" button just above Stage Settings in Stage Setup. If you then drag the different displays around within the Stage, anywhere they overlap it should automatically handle the edge-blending for you.

Gif: https://jmp.sh/L3j7UYBL

If you are doing edge-blending, these User Actors of mine might also be useful for calculating how many pixels of overlap you want to have (generally around a 20% overlap is ideal): 

blend-resolution-calculator.iua4

blend-resolution-calculator-2-display.iua4

blend-resolution-calculator-h-and-v.iua4 

This tutorial of mine on how to put User Actors into your Global User Actor folder so you can use them in any project was made for Isadora 2, but the process is still basically identical: https://lucaswilsonspiro.wordpress.com/2017/08/28/isadora-set-global-user-actors-folder/

If you're not doing edge-blending, you can just add multiple displays to the same Stage as shown in the gif, but instead of overlapping them, you can just butt them up against each other at their edges so they have no overlap. Then, when you open IzzyMap for that Stage, you'll have a Stage that encompasses all three displays for mapping purposes.