Issue 23 in syphon-implementations: Problem with multiple instances of JSyphonServer

[syphon-impl...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 23 by cifah...@gmail.com: Problem with multiple instances of
JSyphonServer
http://code.google.com/p/syphon-implementations/issues/detail?id=23

Like I've said in the forum
[http://v002.info/forums/topic/multiple-syphon-servers-in-processing/] I
have found that it's not possible to send separate Textures on separate
Syphon Servers.

In attachment a quick project that shows this behaviour.

There are two Syphon Server and two PGraphic, in the draw there is a call
to the method sendImage, one of them is commented.

Steps:
1 - Run the project as is and take a look at the list of avaible server,
there is only one server called "multiplesyphon - 1" that shows a white box
with grey stroke
2 - Uncomment the second call to sendImage (row 34) and run again, and take
a look at the list of avaible server, there are two servers "multiplesyphon
- 1" and "multiplesyphon - 2" but the first is empty, the second contains
the grey square

Attachments:
multiplesyphon.pde 1.3 KB

[syphon-impl...@googlecode.com]

Updates:
Owner: andres.c...@gmail.com
Cc: v...@vade.info

Comment #1 on issue 23 by v...@vade.info: Problem with multiple instances
of JSyphonServer
http://code.google.com/p/syphon-implementations/issues/detail?id=23

I do get a second image, however it flickers occasionally. My gut from
looking at this is that it appears that some OpenGL state is not being
properly tracked inside of Processing, or inside of jSyphon/Syphon for
Processing that is causing the issue. This might be texture attachment /
buffer binding issues, I dont think the issue lies within Syphon framework,
as that stuff is super tight and works everywhere. Some glue code that is
managing states is not being called.

Another interesting effect is that the FPS counter for server 1 is 0, and 2
is 120, so clearly something somewhere is not happy.

I've assigned Andres to this, but I will also take a peek later when I have
time. Thanks for taking the time to make a simple reproducer.

[syphon-impl...@googlecode.com]

Updates:
Owner: v...@vade.info
Cc: -v...@vade.info andres.c...@gmail.com
Labels: -Priority-Medium Priority-Critical

Comment #2 on issue 23 by v...@vade.info: Problem with multiple instances
of JSyphonServer
http://code.google.com/p/syphon-implementations/issues/detail?id=23

Oh god. Yea, its jSyphon. jsyphon_JSyphonServer.m line 10 or so

static SyphonServer* _myServer;

Thats not good. Thats a huge issue, but one that should be easy to fix.

[syphon-impl...@googlecode.com]

Comment #3 on issue 23 by v...@vade.info: Problem with multiple instances
of JSyphonServer
http://code.google.com/p/syphon-implementations/issues/detail?id=23

Quick note, it appears the common methodology to get around this is to
stash object pointers in java longs, and have wrappers on the Java side
that hide those nasty raw pointers from the rest of the world and then
convert from the long to a typecast id as the address of the NSObject on
the "obj-c side"


IE: on the Java side you have something like, long nastyPointer; private
native void doThingy(long pointer); public void doThingy() {
doThingy(nastyPointer); }

This means anything using jSyphon would need to be updated, but I think
thats really only Processing at this point.

[syphon-impl...@googlecode.com]

Comment #4 on issue 23 by cifah...@gmail.com: Problem with multiple

instances of JSyphonServer
http://code.google.com/p/syphon-implementations/issues/detail?id=23

Any update? :)

[syphon-impl...@googlecode.com]

Updates:
Status: Fixed

Comment #5 on issue 23 by andres.c...@gmail.com: Problem with multiple

instances of JSyphonServer
http://code.google.com/p/syphon-implementations/issues/detail?id=23

Fixed on the github repo:

https://github.com/Syphon/Processing/issues/10

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings