@eamon and All,

So I worked with Eamon today via Team Viewer to address his issue and we got everything working. Mostly, the issue seemed be related to the fact he had scaled the two 4K displays (LG Televisions actually) to 50% using the Displays System Preference. (Eamon's instinct here was a good one: I don't have 4K content, so let's save some bandwidth.)

But, there were several other anomy'salies that were in macOS itself, e.g., the System Profiler reported the resolution of one of the displays to be 7680 x 4320, even that would be an 8K display not a 4K one; this finding was especially strange since two two displays were exactly the same make and model, and certainly do not offer an 8K resolution.

Our action item will be to double-check that using the scaling to something other than 100% will cause Isadora to do something wrong. But right now, I do not feel this is some widespread issue that others will face, especially Ince most users would not

Thanks to Eamon for getting me access to his machine and for standing by as I went through this process remotely.

Best Wishes,
Mark

@citizenjoe

Thanks Hugh, I should have indicated that up front. 

Best wishes

Russell

@mark said:

Please @Woland log this as a feature request.

 Logged :)

Hi all, thanks for the advice. I'm helping out a friend with this one and just realized my mistake - it's out of range so it defaults to the max value. The  Gets are going into routers so the value is capped at the number of outputs. He didn't put calculators in to subtract the base value to get within range. Not sure why it didn't work in my patch earlier, but probably user error too. Thank you all for taking the time to help! This is what happens when you are under the gun and it's late at night...

@woland @peuclid @liminal_andy @Kathmandale @Fred @Bodo 

Just want to thank you all again for all your help and insight. We're opening our show tonight, if anyone is interested in viewing the piece you can stream directly on our Twitch! We have two showings, tonight 20:00PST (Vancouver/LA time), and tomorrow (Sunday) same time. 

Fingers crossed that Skype continues to behave for us! All of your tips and suggestions have been immensely helpful. 

Grateful always for you all!

thanks! I missed the other post. I’ll follow that. There are interesting leads

cheers

On a Mac, check out Better Touch Tool. It can accept midi triggers as inputs and use them to trigger pre-programmed window sizes (as well as almost any OSX function and a million other things).

On Windows, I believe AutoHotKey can resize windows, but I'm not sure how to trigger that from Isadora. Though since you're operating, it sounds like a pair of custom hotkeys (in and out of the scene) would do most of what you're hoping for.

@django Nice work! Thanks for sharing your process.

@woland

exactly and perhaps easier to do an equivalent to "Get URL Text" an actor "Send URL". I use at this time the QC Webbrowser to send command to a PTZ Camera but sometime this old QC actor crashes without any reason.

I hate Apple for this yearly OS change. No time to work on other things (sound , etc…)

The return problem in different controls is solved for me on Mojave.

Thanks for all

Jean-François

@msanii @ianpep 

The Zoom version that reinstates NDI virtual input for Mac OSX is as follows:

May 24, 2020 version 5.0.4 (25694.0524) Download Type: Manual Download here: Download Center 

Re-enable virtual camera support Support for virtual cameras will be re-enabled for users on client version 5.0.4.  

I can also confirm that it is load hungry coming out of Isadora using what appears to be about 30% of load resources.

Best Wishes
Russell

@mark_m

Amazing! Pete is indeed one of our directors. I'll pass your greetings on. Small world.

@mark

I've experienced the black flicker when using Electron Capture App (https://github.com/steveseguin...) to send a video stream from OBS.Ninja into Isadora. Electron is a frameless, streamlined browser window that would be perfect twinned with the Screen Capture actor were it not for the black flicker issue.

@vjmc said:

Out of curiosity, has there been any development on the OSC web socket that I believe was mentioned in the session

As of now, no. I am focused back on the main Isadora app at the moment. If we can roll that into the fall release, we will. You can read more about our plans in this forum thread.

Best Wishes,
Mark