[laserpilot]

Thanks Tom!

I got the FBO setup working ( https://vimeo.com/59377121 )

and it seems to run pretty well despite being such an unintended use.

The one tricky bit I’m running into is how to sync my frame updates with open cv. Usually the Open CV updates in OF are only updated when there is a new frame from the videograbber, but with ofxSyphon I don’t seem have access to this kind of information.

Is there an easy way to get the frame update information from Syphon into ofxSyphon so I can try and limit frame drops? What parts should I take a look at?

[laserpilot]

edit: nevermind (i think)…found got some answers on the OF forum once i found the right thread. Not possible at the moment due to potential threading issues (at least it wasn’t a year ago)…ultimately i was looking to use it with opencv: http://forum.openframeworks.cc/index.php/topic,7791.0.html

[laserpilot]

Strange..I’m actually getting halfspeed framerate when I try and send stuff as a textureRef and don’t draw to screen…but i think it’s because the ofxEDSDK doesn’t have a method to getTextureRef() like ofImage does so I have to copy the EDSDK pixels into an ofImage and get that texture…I’ll have to talk to Kyle about how to properly add in something like that so I don’t have to copy…but it might be just a way of swapping around my pointers the right way or using another texture call.

Currently doing it like this:

else{ //or publish as a texture and don’t draw to screen
if(camera.isLiveReady()){
ofImage img;
img.setFromPixels(camera.getLivePixels());
individualTextureSyphonServer.publishTexture(&img.getTextureReference());
}
}

[laserpilot]

Ah ok..that makes sense. I’ll look into how oF handles that stuff..I’m sure someone has figured that out before in that community.

The texture drawing makes sense…I’ll try and make a toggle to only capture the texture and see how that goes.

[laserpilot]

Thanks bangnoise!

-Good to hear it works on a 7D

-re: Icon..absolutely, I will change that today…i went for quickest ugly icon i could make and only had the recorder lying around

-Not sure why it’s crashing on exit, but It might have to do with how threading is handled for ofxEDSDK…there isn’t a camera.close() function in there yet, so I imagine either that isn’t closing correctly or threads aren’t being unlocked correctly when the app exits

-Ah yeah..I knew I had been able to minimize syphon windows before..I had been working in OF for so long that I had forgotten that piece. I’m at best a beginner/intermediate C++ coder so I don’t know if I have the know how to address that yet.

[laserpilot]

Yeah I could reproduce it with the client maxhelp patch if I added the fullscreen command to jit.window. Thanks for looking into it.

[laserpilot]

Closer! I have the images co-mingling fine now, but now if I fullscreen my jit.window, syphon’s effects go away (i’m just doing an additive blend between the quartz comp and my jitter stuff). The app name and server name are lost from the umenu’s. I can bring them back if i stop and start the quartz comp or open and close the viewer window..then they just instantly pop back in. Fullscreen just isn’t being friendly.

[laserpilot]

Awesome! Glad I could be useful…im even considering using this for a show in a week..probably not..but if it worked fine under stress it could save me some time

[Author]

Posts