@em_tx

Thanks @citizenJoe for answering this question / helping out :) ShutterEncoder is a really powerful (and most importantly fast) tool for these kind of operations.

@dusx

Got it!

function main()
{
    var input             =    arguments[0];
    var values             =    input.split(',')
    
    return values;
}

So I configure the matrix to have a ',' separator between each value (integer, 3 digits), output the string in a trigger text actor then to the javascript actor with this code. Work perfectly for me.

Thanks you.

@dusx said:

This workflow is hugely optimized and allows you to bring in audio from any source along with the stage image recording.. this allows you to even mix in multiple audio sources if you like (narration being one use case).

Though, for OBS on macOS, you have to go to the trouble of making an "Aggregate Device" to capture the system audio. See this link for instructions on how to do that.

Best Wishes,
Mark

@dillthekraut said:

A different approach would be to have only one projector actor in a 'secondary scene' which is always active in the background (activate scene actor), and send the video outputs from each scene to it with the broadcast and listening actors instead of separated projector actors.

Here the tutorial about activating scenes in the background and the broadcast / listener actors.

This is what I do personally. Also @Elena , here's a template file for global projection mapping that I made a while ago: https://community.troikatronix.com/topic/5495/global-projection-mapping-simple-show-template?_=1634910899599

It completely avoids the issue of blend modes and User Actors because you only ever need to have a single Projector actor per Stage in the entire file.

As an advice in general. If I finish a project, I always archive the installation file of the Isadora version, with the actual project, I coded with it. Just in case, I need to reactivate it and have issues with newer Izzi versions.

I even keep the older version for a while in parallel in the same computer. On macOS, this is simple, as you can easily rename the applications name (adding the versions # e.g.). And install the second version.

@bonemap @jserembe

Version 3.0.7 will not work on Big Sur (no output on the stage). If you have Big Sur you have to upgrade Isadora.

Best Michel

@thatmattrogers

THAAAAAANKS

Dear @michel,

Well that's similar to the patch I have added, only the first scene has to be active for it to work.

Oh my! I didn't see you'd already done it! Sorry to duplicate the work and for not reading more carefully.

Can we just say "great minds think alike"? ;-)

Best Wishes,
Mark

@woland

The Javascript is from @DusX so I would say the credit goes there for this one.

Best Wishes

Russell

Hi there @thatmattrogers, 

If you wish to set your values when you enter your scene you can either use;

- A 'Enter Scene Trigger' with a Trigger value, connect that to the inputs that you wish to reset.

Or

- Use the initialize functionality of an Actor input. In general this is cleaner then using the above method, see our KB article explaining some differences if you work with Media inputs.

@dusx said:

// CREDIT: by zoidberg uniform sampler2D tex0; uniform vec2 resolution; const vec2 pointOffset = vec2(0.0, 1.0); void main() { vec4 outColor; // "upper" (a.k.a. "the top row") if (fract((gl_FragCoord.y+0.5)/2.0) == 0.0) { //gl_FragColor = vec4(1,0,0,1); outColor = (texture2D(tex0, (gl_FragCoord.xy)/resolution) + texture2D(tex0, (gl_FragCoord.xy - pointOffset)/resolution))/2.0; gl_FragColor = outColor; } // "lower" (a.k.a. "the bottom row") else { //gl_FragColor = vec4(0,1,0,1); outColor = (texture2D(tex0, (gl_FragCoord.xy)/resolution) + texture2D(tex0, (gl_FragCoord.xy + pointOffset)/resolution))/2.0; gl_FragColor = outColor; } }

 Hey thanks a lot! works ok for my puposes, I just needed a fast realt time solution, all the files will be re-encoded correctly some time.

Cheers

Fred

@juriaan

That's exactly what I was hoping for.

for some reason I skimmed straight past "Get Stage Image" when I was looking.

Thanks so much.

Note: the plugins folder is also easily openable from the Isadora Help menu. Just go to Help > Open Plugin Folder > Troikatronix Actor Plugins

This way you can install the plugins directly. On Windows each plugin is contained in a folder with a name ending in ".izzyplug"
You only need to copy the folder to this location and restart Isadora. (the shortcut simply makes finding the plugins folder even easier)
The default path for the Plugins is: C:\Program Files\Common Files\TroikaTronix\Isadora Plugins

@dusx

for me this would be a real game-changer. Isadora is an awesome interactive real-time performance tool, but enabling an easier media output workflow would bring it into the world of content creation without losing any of its distinctive heritage from the worlds of dance and theatre.

@bonemap 

Hey! That's great value you delivered!! Thank you for that! I'll take a closer look at these actors :)

all the best, kindly

jk

@citizenjoe said:

I copy a scene and duplicate it over and over again if I want to do that. Cmd/Ctl-D is really fast!

 This is what I do as well. 

When building a show I create a "TEMPLATE" scene with everything I might need in it, then duplicate it for each Isadora Scene I need to make.

@thatmattrogers said:

I still have to put in a table actor to map the key input to the desired scene.

 If you order your scenes sequentially according to the buttons, then you can just use a calculator instead of a table to handle whatever offset you need. 

E.g. if you need buttons with values 9-63 to trigger scenes 1-55, you can do this:

If you need the offset to go the other way, just switch the calculator to add.

e.g. if you need buttons with values 0-47 to trigger scenes 1-48, you can do this:

OK I now have a user actor which shows a green indicator for the current scene, has a lit button for "go" and "prev", and intelligently checks how many scenes there are in your patch and gives you a lit button linked to a jump actor for each one. Thanks to everyone who helped, as ever, any new task completed in Isadora comes with lots of new understanding for future projects.

If anyone has this same controller and would find this patch useful; here's the user actor that does all the stuff.

akai-apc-mini-control-final.iua3

@dillthekraut

I have changed both factors, it changes the velocity but it is working.

I went ahead and made an edit of my live drawing patch set up for tracking. You'll still need to watch Mark's tracking Guru Session because the patch is not at all calibrated for tracking. 

The edit is the second Scene. I added green Comment actors to draw your attention to things that are different from the previous Scene.