[SOLVED] Bug in Screen set up Isadora 3.1.1?

eamon

Hi Mark

I will open a ticket after this post.

I will happily stop using the Jump Desktop to dial if that cures the problem!

It has been a very long week and I am looking to automate the start up process etc. I will revert to 3.08 f12 and try this with a syphon client as aside from the manual set up, it should work for the presentation.

I can confirm I did not see this behaviour in 3.0.8 f12.

I am accessing the Mac Pro 2013 via Jump Desktop from a Macbook pro Retina 13".

I will fill out a ticket and hopefully this is a simple fix for all. I can only imagine the amount of work involved and devoted to getting to 3.1.1 and all for me to mess it up!

Eamon

mark

@eamon

I assume by now you've opened a ticket. In the meantime, this morning I attempted to replicate your setup as best I could and have one possible thing that could be wrong.

SUMMARY

The main thing I want you to do is to ensure that the 'window cpu mode' input of the Screen Capture actor is turned on. That's because when 'window cpu mode' is off, the Screen Capture window can only capture exactly what is on that display. If this input is turned off, and Isadora's user interface is in front of the Google Chrome browser window, you will see Isadora's User Interface at the output of the Screen Capture actor, not the Google Chrome content.

I've got my fingers crossed that this might be the problem. Please report back if you find out it is true.

DETAILS

Here are the details of my test:

I am running Isadora on a MacBook Pro 15" laptop with Catalina (10.16.7)
I have two displays attached in portrait mode. Since I only have 2K displays, I changed the scaling of the displays to 720p to simulate the fact that you said "I am running the TV's in HD and not 4K as there is no need." (If you can verify that you did this by changing the Scaling in the System Preferences > Displays that would be helpful.)
I am using Google Chrome as the browser with a single window open. The Window is behind Isadora's user interface. (I also tried it when it was behind the Stage on Display 2 and Display 3)
I am using two Screen Capture actors (v1.0) to capture from the Google Chrome browser window. These two actors have different crop settings to capture different portions of the browser window and the 'window cpu mode' is turned on.
The only thing I'm not doing the same as you is using Jump Desktop.

Everything worked as expected. Adding Projectors, changing the crop of the Screen Capture, Isadora recognizing that the displays were scaled to 720p, etc. Everything I could think of that could go wrong with this setup, did not go wrong. It all worked as I would expect.

However, when I turned the 'window cpu mode' off (which is incorrect) I saw something that looked a bit like the photo you posted to show what was going wrong: I saw Isadora's user interface on the stage. This is why I've asked you to ensure the 'window cpu mode' input of the Screen Capture actor is turned off.

Best Wishes,
Mark

eamon

hi Mark.

The mac pro in question is not scheduled to come on till approx 11am irish time. I will attempt to do a screen recording then of my steps.

My plan was that on my working monitor isadora would be behind chrome. The site I am accessing is set to an aspect ratio for the 2no. Screens. As a result, I have the chrome browser near enough to full screen without full screen being active. This was just to allow me to see and capture all of the site.

I did turn the win cpu to ON as I figured I would need it to ensure chrome was always on top.

The only time I had isadora to the front was for set up. When I start the mac, it auto launches Isadora & Chrome via the normal method in system preferences.

I hope that helps.

Eamon

eamon

Hi again.

When I just looked again at the image of the screens posted, I have noticed that the Windows CPU Mode is set to OFF. On that image which is one of the links posted yesterday, it is set to OFF and the problem is visible.

See image:

pxl_20211023_124751034-resized.jpg

Eamon

eamon

@mark

I seem to be unable to access the computer in question this am. It will be Tuesday am before I can probably access it.

If I can provide any more help to track this bug in the meantime, I will do so.

I also sent a reply to your earlier email.

Eamon

jfg

@eamon

I don't know if this is the problem you have that I could produce or reproduce. Anyway by me this problem is coming from the captured window. If I move the captured window only a few pixels outside of the limits of the visible screen, I lost the capture of this window and get the middle of this screen captured.(picture 2) Moving the captured window in the limit of the screen I get back what I want (picture 1)

and a screen record:

update: I have the same behavior in 3.0.8f12

best

Jean-François

mark

@eamon said:

I seem to be unable to access the computer in question this am. It will be Tuesday am before I can probably access it.

Let me know what you find out. Thanks for your help and understanding.

Best Wishes,
Mark

DusX

To be clear, are you setting your 4k display to HD in the system preferences for displays?
Or are you doing this in the Stage Setup dialogue in Isadora?
If you use the Isadora Stage Setup, you can easily have the display image only appear in one corner when using a custom size.

This image shows a setting which will make the display appear in only 1/4 of the 4k display.

eamon

@dusx

I have set the displays from 4k to HD in the system preferences of the mac e.g. they are set to 1080 x 1920.

I would always set up the screen ratios in system pref and then scale accordingly in whatever program I am running.

In Isadora's Stage Set Up, I have also had to set the ratio to custom and marked them screen(s) as 1080 x 1920 as the default was 1920 x 1080.

Sorry for the late reply.

Eamon

mark

@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