Duffield

I'm working on a project where I need to capture an area of a desktop (assuming using [jit.desktop]), but am also trying to project and output video in fullscreen. I am working with a client but we might be stuck with a Mac Mini with two video outputs each to a projector which is part of the installation, so both ports would be occupied.

What I'm looking to do is have jit.desktop capture an area "off screen" with content running independently outside of Max. Is there any way to "virtually" extend the screen real estate and have a Max object capture it?

I tried to see if the multiple desktops in OSX (my version is 10.9.4) using Spaces could work with [jit.desktop], however, I could not get the coordinates (as I somewhat expected). I am assuming this is because [jit.desktop] reflects the pixel coordinate of the monitor display itself, not any virtual coordinates of the image.

What I'm looking to do is have jit.desktop capture an area "off screen" with content running independently outside of Max. Is there any way to "virtually" extend the screen real estate and have a Max object capture it? 

I tried to see if the multiple desktops in OSX (my version is 10.9.4) using Spaces could work with [jit.desktop], however, I could not get the coordinates (as I somewhat expected). I am assuming this is because [jit.desktop] reflects the pixel coordinate of the monitor display itself, not any virtual coordinates of the image. 

extending-jit-desktop-with-osx-spaces

http://andreacremaschi.github.io/Syphon-virtual-screen/

This is just what you need:
http://andreacremaschi.github.io/Syphon-virtual-screen/


Great find, LSKA! Thanks I didn't know that one...

On a related note, jit.desktop certainly has come a long way in terms of performance since its beginnings, but I would love to have a GPU accelerated version, that is: instead of capturing the screen to RAM and processing it in the CPU, it should copy the composited framebuffer of the operating system already present in the GPU/VRAM to a new texture. That would be super fast! (Vade did this with his v002 Screen Capture, but it only worked with Mac OS X 10.6. Since then Apple changed the API and it probably became more difficult to implement it...).

Jit.desktop hasn't made the transition to 64 bit yet... I wonder what Cycling's plans might be... deprecate or upgrade? I hope the latter...

By the way, here's a screen capture application I built with Max... didn't have the time to finish yet and iron out some bugs...

On a related note, jit.desktop certainly has come a long way in terms of performance since its beginnings, but I would love to have a GPU accelerated version, that is: instead of capturing the screen to RAM and processing it in the CPU, it should copy the composited framebuffer of the operating system already present in the GPU/VRAM to a new texture. That would be super fast! (Vade did this with his v002 Screen Capture, but it only worked with Mac OS X 10.6. Since then Apple changed the API and it probably became more difficult to implement it...).
Jit.desktop hasn't made the transition to 64 bit yet... I wonder what Cycling's plans might be... deprecate or upgrade? I hope the latter... 

Now to test whether you can still interact with a mouse on the virtual screen extension...

Duffield, if you have an iPad you can also use one of these apps:

https://avatron.com/applications/air-display/

Air Display can even use Mac or Windows computers as additional monitors.

I guess these have the advantage of being "real monitors", that is, you're able to see the content and interact with it.

Duffield, if you have an iPad you can also use one of these apps:
http://www.duetdisplay.com/
https://avatron.com/applications/air-display/
Air Display can even use Mac or Windows computers as additional monitors.

I guess these have the advantage of being "real monitors", that is, you're able to see the content and interact with it.


Thanks for the suggestion that would be fantastic for future projects just not this one!

My client is running an (archaic) Flash game that I want to use with jit.desktop. I'm using FLOSC to get some messages from it. It requires mouse controls, so I need it to be on another screen so they can play the game with mouse movements in a nice 1:1 ratio, and then we'll use jit.desktop and put it on a jit.gl.videoplane. This is where there's an inconvenient work around to everything.

Syphon virtual screen is recognized by the system as an actual screen, so mouse integration works. You can think of having a "local" preview of he syphon screen in a jit.pwindow, if you want to watch the contents before sending them to the projector.

Extending jit.desktop with OSX Spaces?