@tlaloc

There is no problem panning your inputs using the AU Matrix Mixer. However, you will not be able to achieve frequency analysis on 8 channels of audio as you can see the inputs are currently limited to 4 and audio analysis is done as a mono track (I believe it is the first channel of a multi-channel track). There is currently no way to select the channel to be analysed from a multi-channel audio track.

Best Wishes

Russell

@mark_m said:

x64 version of Windows

 Yes, a 64bit version of Windows is required. 

Hi, I think that you can use the Screen Capture ALPHA actor in Isadora to mimic the use of the Syphoner app.

Best wishes!

Ismael

@artoo

Hi there Artoo,

Thanks for getting back to us with the solution.. Very weird.. And it was not at all to say that you aren't knowledgeable about the subject. It was more to share the process with other users that are reading this thread.

I was hoping that the Private Address option of Ipad OS was messing things up for you..

Anyhow glad that you got it to work in the end!

- Juriaan

@jfg

Well I made a Philips Hue connection that you can find here

https://community.troikatronix...

@peuclid

Note the final image where you say 'NO' in your comment works with the addition of a Trigger delay (sorry I missed that).
This will ensure the loaded image is pushed into the Freeze, and that any updated Picture is also updated.
This method with the freeze is what I have been using for years (we didn't have GLSL at that time), I don't know if there is any performance benefit?
It does seem the default GLSL is the easiest approach 🙂

@timp95

This article was written for Isadora 2, but most of this is unchanged in Isadora 3 (Isadora 3 added a few things and improved some behaviors).

This article explaining the composite mapping method was also written for Isadora 2, but is also still relevant.

Best wishes,

Woland

As described in Ryan Webber's article (see link at the end of my reply), you can use the print() function in combination with the Monitor window for debugging Javascript code.  

This code worked :

function main()
{
    var outhex;
    outhex = (arguments[0].toString(16)).toUpperCase();
    print (outhex);
    print ('\n');
    return [arguments[0].toString(2), outhex ] ;
}Important: At first, the Javascript actor outputted only the digits of the Hex code, no letters A-F. It seemed to me that it converted the string back to integer due to automatic data conversion. After connecting the output of the Javascript actor to a Trigger Text actor it worked.

Cheers, Gunther

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

@dusx

reloading the actor helps a lot - sometimes I forget this - so everything works - thanks a lot for the support (best forum ever!) - merry Christmas !!

@guevarajorge

You can also use Syphon / Spout within Isadora! Simply go to Stage Setup > and check the Checkbox 'Syphon' / Spout to enable the output. 

@bonemap said:

A local parameter input/output mode switch would provide a great deal more transparency for mutable data points.

 It's on our list 🙂

@mark_m

That is an amazing solution. Thank you for sharing!

@jrhooker said:

Which is to say: Yes, they are all vid-ci (I took out the ffgls cuz they were doing very little and that didn't help). 

The most efficient path to use is vid-gpu. But vid-ci is generally also very efficient because it is also on the GPU. There is a small conversion that needs to happen to turn vid-gpu into vid-ci, but it probably isn't super significant.

Part of the issue could be the effect itself. Some effects simply process the image in one pass. But some will process each pixel multiple times -- the most likely example being any kind of blur. Those effects can be very expensive, even when the GPU is very fast. Also, any GLSL shader that contains a for/next loop is a suspect. Look for something that starts with "for (..." in the code to see if a GLSL has a for/next loop.

What QC actors do you rely on? Eventually Quartz Composer will go away entirely -- it has been deprecated (meaning no longer supported) since Catalina. It's good to know what users use so we can develop replacements if necessary.

Best Wishes,
Mark

@jjhp3 Well damn if a glass of Bushmills didn't clear my thinking - I can use the mesh tool and all is well!

@craigw

What is the trigger for the change of the Movie? It doesn't appear you are using Loop End, so I imagine you are changing them manually?

@kirschkematthias

you can try to extract the sound track as an AIFF or wav file and to synchronize the movie player (volume=0 or only video track) with the Sound Player:

Then you can use the routing of the Sound Player actor. Depending on the required precision of the synchronicity between image and sound it can work

best 

Jean-François 

@jfg Thank you for feedback. 

The setting on the audio card is on 8 channels, everytime I change it form stereo to 8 channels. 

On the Mac I also make my sound card the standard output for audio of my Mac.

And also in Isadora 

@erik-nerinckx

Hehehe. Glad that you enjoy our Isadora 101 Videos! If you need any assist feel free to drop an message on the forum.

- Juriaan

@pieter-vh said:

I bought a hdmi-splitter and tried it yesterday: one signal to the projector, the other to the Atem, and it worked perfectly

Another reason this is a better option is that it means the work required to record everything is offloaded from the show computer to another device, so it ensures your show computer isn't spreading itself too thin.

When I want to take production stills from a live feed or record my output, I use the splitter method and then do the recording on a second computer (sometimes with a second Isadora patch that gets triggered to start/stop recording or capture a still image to disk based on OSC triggers).

@kylewurtz

The problem is that you have a jump actor in your Audio Scene which you activate in the background, so the Keyboard Watcher and the Jump actors you put inside that Scene are functional and thus can and will cause a jump to the next Scene; Scene 3.

Here's the solution:

1. Change your jump function in your first Scene to jump OVER the Audio Scene like so: 

2. Then delete your jump macro from your Audio Scene. (Since you only ever use Activate and Deactivate Scene actors on it, you never need it to jump to another Scene.)