Hi Mark,

first: thank you a lot. really 🙂 In fact, your suggestion works pretty good, setting better the chroma key and lowering the camera/eyes++ resolution gives me better results: performance monitor says between 150 and 180 cycles, working with all resolutions to 400*300\. (I tried with three of chroma/eyes++ working together) and video seems set to the minimum! I want the patch working with 3 colour detected (red, green and blue) and now I am thinking maybe it is possible my idea: my final goal is to run this patch on a mac "middle class" or lower (i.e. an i5 or similar, 8Gb ram), do you think it's possible? Now I'm going more test... Stefano

Dear Joe,

Re-registering will help only if you have purchased the Core Video upgrade. If you do not have that upgrade, you won't see the Syphon actors in 1.3.1f06\. I'm rushing to get a new pre-release done so that this problem will be solved. If your need is very urgent, email me privately and I can get something to you. Best Wishes, Mark

yup. I did and you sent me an email on this regard

Dear Moeye,

I cannot reproduce this behavior with 1.3.0f24 or the latest pre-release on Windows 7\. I do not have a running copy of Windows XP to test, so I cannot try it there. My only suggestion is to ensure you have the latest version of QuickTime from http://apple.com/quicktime -- see if there is an update and if updating helps. If not let me know and i'll see what else I can do. Best Wishes, Mark

Thanks Mark
works

Glad this is sorted 🙂

It's defiantly in the latest one.. Just checked.

Dear Ale,

Try this test: in your .izz file, create an empty scene. Then send the MIDI or OSC to Isadora. Does the frame rate change in the Status Window? My guess is that the frame rate will remain solid. If not, then it could be that whatever you're doing when you receive the data is what is slowing down Isadora. For instance, changing the 'speed' of a movie frequently can cause very heavy CPU load depending on the codec. If you were to connect a MIDI continuous controller to the speed input of a Movie Player, and you were receiving lots of MIDI values very quickly, it could cause the whole program to slow down. In any case, I can take a look if you send me your patch and indicate which scene is causing the problem. Please take into account that I am in the midst of an artistic residency, and it may take a day or two before I get back to you. Best Wishes, Mark

Dear Mark.
Izzi version with this problem is 1.3.1f06, QT 7 play them without problems, like anything else that plays video in my mac. Drivers are up to date.
And again, doing the same thing in 1.3.0f24 works fine.

Best
Ale

An update of my Modul8 Layer OSC remote control Actor.

Some bug fixes, but still not perfect.
When you copy or add this actor inside a patch, you have to change the layer n° (to update osc message inside the actor).

Best
Philippe
65f8b1-modul8-layers-osc-remote-v1.2.iua

Hi craigw,

I've had that kind of issues with isadora too. I think there is a "trick" that can improve your performances. For this you have to use the AMD GPU with eyefinity ( and 6 outputs on the same card ). All your video outputs must have the same resolution. You need to create a eyefinity group with all your outputs. Isadora will see it as a single monitor ( with super high resolution ). You use it as a single stage, and then you use several projectors, to place each image where it has to be. No garanty it works, but I've had in the past good results doing this. Feedback any result if you try it. Mehdi

Dear Kerstin,

What version of Isadora are you using? The version number is shown in the "About Box" which you can open from the "Isadora" menu found in the menu bar. If you are using the current release version (1.3.0f24) I suggest you upgrade to the version at http://troikatronix.com/download/isadora-pre-releases/ -- it is stable, and fixes several bugs. You can always go back to 1.3.0f24 if necessary, but I suspect if you're using 1.3.0f24 that the latest pre-release will solve the problem. Best Wishes, Mark

@Michel

that was it, thanx !!

recording stage problem is solved in Isadora 1.3.1f06 

some 3rd party QC plugins can cause strange graphical UI behaviors in IsadoraCore  (screen capture) one of them, in my setup the plugin was active in the scene, other programs using the QC components could be as well sources, and Quicktime components, noticed changes in Izzy and QC with OSX 10.8, they can lead to unexpected never  seen before crashes, think it is important to keep track of what you install and how to clean up again.

best

bts

IsadoraCore 1.3.1f02 OSX 10.8 3rd party QC plugins

Thanks for the quick response!  I'd been using 1.3.0f24, but once this problem started occurring, I updated to 1.3.1f02.  I'm using a MacPro with a quad-core Xeon running OSX 10.6. 16GB RAM.

After doing a bit more tinkering, it seems this problem crops up when the actors are triggered to become visible, I click to another scene before the track is over, and then come back to that original scene and those actors that were triggered earlier start playing.  Using the speed control fixed the issue.  And as far as using these 10 movie players instead of just one edited track, that's just laziness on my part.  These were just placeholders, as I didn't know which tracks we'd end up using and in what order, so I just plopped them in to give the director a listen. Mark, I will upload the crash report when I get back into the theatre this evening.  Thanks so much for all your help, and for the very useful suggestions on the "best practices." Doug

Dear Marloeke,

It's not that way on my machine. Click on the word 'value' in the Value Delay Line actor -- what does it say in the inspector? Minimum and Maximum (at the top) should be MIN and MAX. The default settings for Scale Min and Scale Max are be MIN and MAX. Do the same for the the word 'delay' in the Value Delay Line actor. Minimum and Maximum (at the top) should be 1 and 256\. The default settings for Scale Min and Scale Max are be 1 and 256. Are you're settings different than these? If so, you may need to change them back. Best Wishes, Mark

Weird! But happy it's solved.

Best, M

Dear Mark,

Thank you so much for such a quick response.
The version that I'm using is IsadoraCore 1.3.0f24.
And speaking of which, I just checked and realized there are newer Pre-Releases version already! I'm going to try the newest version and see if this helps. I'm glad that you asked!
I'll also try deleting the Preferences if this happens again and see if that helps. I'll report it back here.

Dear Hugh,

Well then, we're very close. FreeFrame plugins are supposed to return a code that says FF_UNSUPPORTED when you ask it if it has a feature and that feature is unsupported. Your problem plugins are returning FF_FAIL, which, by the book is the wrong response. I guess I should simply be looking for FF_SUPPORTED, which is what I'm going to do. So I think you'll have everything working in the next version. Best Wishes, Mark