bareimage

Due to the massive issues with real time rendering on Macbook Retina I have returned my top of the line computer and returned to my 2010 computer. I did however get windows laptop to work with touch designer, VVVV and Max.

I have decided to give a spin to my last iteration of source code that drives my ongoing project Invisible Beast. By mistake I opened my project twice. The result was layering of two projects in the output window of the project. Perhaps this feature has been documented at the Max Msp for Win but I did not find any references for it.

It appears that two jitter programs can access the same rendering context simultaneously. This is impossible on Jitter for Mac. I am yet to figure out the practical use for this behavior. But I think it would be possible to use it for VJing and life coding. It would be also awesome to be able to direct output of the rendering context to other applications, such as Resolume or VVVV.

Windows lack an architecture for visual content sharing akin to Syphon on Mac. If the content sharing would finally be possible we would be able to free our creativity....

PS I am sorry if I am naive, I am self taught max msp developer, and most probably people know about this behavior already....

I have decided to give a spin to my last iteration of source code that drives my ongoing project Invisible Beast. By mistake I opened my project twice. The result was layering of two projects in the output window of the project. Perhaps this feature has been documented at the Max Msp for Win but I did not find any references for it. 

It appears that two jitter programs can access the same rendering context simultaneously. This is impossible on Jitter for Mac. I am yet to figure out the practical use for this behavior. But I think it would be possible to use it for VJing and life coding. It would be also awesome to be able to direct output of the rendering context to other applications, such as Resolume or VVVV. 

PS I am sorry if I am naive, I am self taught max msp developer, and most probably people know about this behavior already....


jitter-bug-windows-or-a-ray-of-hope-for-syphon-like-integration-windows

this is simply the result of opening two render contexts with the same name. they will both draw into the context window of that name.

only one of the jit.windows gets to keep that name (the first one to open), the second gets a new, randomly generated name.

this is simply the result of opening two render contexts with the same name. they will both draw into the context window of that name.
only one of the jit.windows gets to keep that name (the first one to open), the second gets a new, randomly generated name.

Hello, Robert! Well it is impossible to do on the mac. You can't have two patches rendering to the same window. This just a small difference how macinosh and window version of max msp work.

But this got me thinking, would it be possible to access the same context from let's say vvvv?

Hello, Robert! Well it  is impossible to do on the mac. You can't have two patches rendering to the same window. This just a small difference how macinosh and window version of max msp work. 

But this got me thinking, would it be possible to access the same context from let's say vvvv?


Jitter bug @ windows or a ray of hope for syphon like integration @ Windows