Screen Capture actor (Alpha) - Bug Reports & Updated Versions

jfg

for me on Mojave is all OK. I tried today with two screen and a videoprojector as third output and used 3 screen capture actors sent to the second screen. No problems: crop works in all cases, list of windows in all actors, windows chosen through names too.

best

Jean-François

dachhu

After yesterday I have updated and Windows 10 to absolute latest, updated geforce Nvidia to the Max and gave my memory a good scrub and now it all seems hunky dory, but haven't used a secondary screen yet. will expore more. Thanks for your hard work. David

mark

Dear All,

Below is an updated to the Screen Capture ALPHA actor. The following bugs have been addressed:

1) The Crop Function should now always work, whether for a display or a window. (@kikko)
2) I've verified the 'window list' works on macOS Catalina. (I did not see it fail previously, but tested it again @sommerdi)
3) It's not a bug on my side, but as @dachhu's post above shows, it's essential that your GPU drivers are up to date if you're running Windows and you want to use this plugin.

In terms of the issues mentioned by @kikko and @dachhu about capturing the internal (laptop) display as well as external displays, this is something we have to work on. As @kikko mentioned, OBS exhibits the same limitation, and our team member @DusX has also experienced it on his machine. This only seems to come up when you've got both a primary GPU (takes more power) and the Intel Integrated Graphics GPU (which takes less power) installed. I cannot reproduce this on my Mac Book Pro running Windows via Bootcamp, because it only "sees" the one AMD primary GPU and uses it for the internal and external displays. So, on my computer, it works as expected.

I have an idea about solving this, but it's going to require me using TeamViewer to get on @DusX's computer remotely to see if it might work. (Unless someone in Vienna has a spare Windows laptop they want to drop off to me -- if that's the case, let me know.)

In any case, I've fixed all I can and look forward to hearing more about your experiences using it.

To try the latests, download screen-capture-v0.9.3.zip

Best Wishes,
Mark

tomthebom

@mark

Hi Mark, thanks for the update... I am working on a 2.9Ghz i7 Macbook from 2017 with High Sierra and I still have no luck when it comes to capture a window from the window list in GPU mode.
All I manage to see is a capture of my whole computer screen. (And yes, I can crop it.)
First after switching to CPU-mode I manage to capture any window from the list, although lots of items are pictures from my menu bar- is there any chance to turn this off? Best wishes to Vienna!

mark

@tomthebom said:

Hi Mark, thanks for the update... I am working on a 2.9Ghz i7 Macbook from 2017 with High Sierra and I still have no luck when it comes to capture a window from the window list in GPU mode.

I'll go test on High Sierra right now.

But RE: this comment "although lots of items are pictures from my menu bar- is there any chance to turn this off?" I cannot find a way to sense what is a "real" window and what is a User Interface element. For some nerdy info, here's the exact call I'm making:

CGWindowListCopyWindowInfo(kCGWindowListOptionOnScreenOnly | kCGWindowListExcludeDesktopElements, kCGNullWindowID)

You would think that kCGWindowListExcludeDesktopElements option would exclude all those unnessary windows. In any case, I'll look into this too but I'm not hopeful.

Best WIshes,
Mark

dbini

i'm happy to report that v0.9.3 is working perfectly for me on Mac - High Sierra. :)

Michel

@tomthebom said:

although lots of items are pictures from my menu bar- is there any chance to turn this off?

unfortunately not.

Best Michel

mark

@tomthebom said:

I am working on a 2.9Ghz i7 Macbook from 2017 with High Sierra and I still have no luck when it comes to capture a window from the window list in GPU mode.

I don't quite know what to say. Here's a screen shot of the plugin working on High Sierra. The window list appeared as it should.

Best Wishes,
Mark

mark

To All:

I was able to remove the excess windows from the list by examining certain properties in each window. Now you won't see the menubar and all the widgets inside the menubar.

I simply re-uploaded using the same version number. So all of you should download screen-capture-v0.9.3.zip again to get this improvement.

Best Wishes,
Mark

jfg

@mark

Dear Mark,

you are really the best. It works fantastic

best

Jean-François

tomthebom

@MarkTroika

Thanks a lot Mark, somehow I managed to get it to work.
And the list is very neat now... Thanks for your effort!

jfg

@mark

it is not possible to answer to your NDI watcher post.

best

Jean-François

kikko

@mark new release tested:

- crop issue solved!

- some menu bar still alive

- in window list still missing Isadora one

- if turn on windows cpu mode and choose any of the window appear on window list, the load drop down a lot

- something very weird happen: if moving very fast the mouse arrow pointer on the display chosen in display field, the load drop down a lot

Waiting for your news about GPU issue.

Thank you!

Francesco

mark

@kikko

Thank you for the interesting results.

In window list still missing Isadora one

Yes, When I first wrote this plugin if I included Isadora's windows, it crashed. I will investigate as time allows. But is it important to capture Isadora's own Windows? I didn't think that would be important.

Some menu bar still alive

You mean in the 'window list' menu? Or?

If turn on windows cpu mode and choose any of the window appear on window list, the load drop down a lot

Well, it could be that that capturing from some displays is itself heavy. I need to work remotely on @DusX's computer to see this, because I don't have those problems on mine.

Something very weird happen: if moving very fast the mouse arrow pointer on the display chosen in display field, the load drop down a lot

It could be that by moving the mouse you are causing the display to refresh more quickly, and that lowers the load.

Waiting for your news about GPU issue

Again, need to remotely work on @DusX's computer. But since OBS doesn't solve it, I cannot promise I will be able to do better.

Thank you!

Your welcome!

Best Wishes,
Mark

sommerdi

@ mark ...

I still have to topic with Catalina .... maybe i have a missunderstanding ...

dbini

@sommerdi

i think that if you are on GPU mode, you will never be able to capture a window that is hidden because the GPU isn't drawing it. That's why Mark has made the CPU mode.

Juriaan

@mark

In window list still missing Isadora one

- Regarding this question that you asked, no I dont see why you would use this tool if you can use Get Stage Image for that purpose..

CitizenJoe

This is similar to my post in the other thread, but updated with observations of v0.9.3 on Windows:

It only works in CPU mode;
On my main laptop display, it captures the whole window as expected;
On the second display, it only captures a portion of the window. Please see the attached image;
Even though it's not showing anything in GPU mode, the load is around 250%! Switch to CPU mode and the load immediately drops to 40%;
It will not show Chrome windows on either display, but has no trouble (on Display 1) showing work, excel, thunderbird, etc.
the Actor sees all the windows that are open in the window list, including Chrome, regardless of which display they are on;

Cheers,

Hugh

mark

@sommerdi said:

I still have to topic with Catalina .... maybe i have a missunderstanding ...

You are seeing the correct behavior.

With CPU mode off, Isadora can only capture exactly what you see on your screen. That means you will not be able to see the contents of any window that is behind (obscured) by another window. With CPU mode on, Isadora can capture the contents of a window even if it is obscured. However, this leads to much higher CPU usage on MacOS.

To be really clear about this, here's a screenshot of a browswer window displaying the front page of https://giphy.com and then Isadora's window in front of it.

If I capture this with CPU mode off, the area being captured is correct; it is the bounds of the window displaying Giphy in the browser. But the image that is captured is exactly what you seen on the screen: the Giphy window with Isadora's window in front of it.

Total CPU usage in the Activity Monitor is about 20% in this mode which is pretty good.

Now, if you turn CPU mode on, then you can get see the contents of the giphy in the browser window, even though it is behind the Isadora's window. Here's the captured image in that mode.

>>> But total CPU usage in this mode is 73%!! <<<

By using CPU mode, you can capture an obscured window but you are slowing down your computer – especially when the window is large.

I hope that makes things clearer for you.

Best WIshes,
Mark

mark

@citizenjoe

Basically, there are severe limitations when using the Screen Capture actor when you have both a high performance graphics card (GPU) and the Intel Integrated Graphics GPU -- this is not just problematic in Isadora, but in programs like OBS which is highly developed in terms of screen capture.

The problem is that the high performance GPU and Intel Integrated Graphics two separate GPU's that do not share images. You can't capture a display from one when you're running on the other.

To be explicit:

1) Restart Computer - Windows Boots Up. The main display (display 1) of your laptop uses Intel Integrated Graphics to show you the computer's desktop, windows, etc. Note that additional displays (display 2, display 3, etc.) are ususally assigned to the high performance card and should not face the limitation I'm about to describe.
2) Start Up Isadora -- it gets assigned to your high performance GPU because the operating system see it needs high performance features. (This can be adjusted, see below.)
3) Add Screen Capture actor which is running in Isadora on the high performance GPU. It tries to capture display 1, but the image for that display is on the Intel Integrated Graphics GPU and Isadora cannot access it because the two seaprate GPUs do not share images.

As I said, this is a problem on OBS and other softwares too. I have not tried the procedure in this video, but it suggests forcing OBS to use the Intel Integrated Graphics instead of the high performance GPU. Try following the procedure in the video, but replace OBS with Isadora as you follow the instructions. In theory (again I haven't tried it myself yet) this should allow you to use Screen Capture for display 1, but with the cost that Isadora is no longer running on your high performance GPU.

I hope that helps you understand the problem. If you try the procedure in the youtube video above, let me know what happens.

Best Wishes,
Mark