Forum Replies Created
-
Posts
-
Hi Ronald, sorry for the delayed reply. This is not something we currently support, but, it *might* be possible in an later version, as Assimp version 3.0 supports some limited saving of 3D data.
Additionally, if you are attempting to work with Core Image Kernels after the output image from the v002 Open Kinect beta 5 (meaning, running filtering on the output image from v002 Open Kinect, not directly rendering to some geometry), do know that Core Image, as used in QC, clips floating point values. Use a GLSL Shader in a Render In Image patch, set to Float 32 bit. That technique seems to work much better in 10.8 than in 10.7. Core Image clips values to 0.0, 1.0 – which is fucking ludicrous because it can support much higher range values.
If you send the output to the v002 Rutt Etra (3.0), in both in RGB as XYZ mode, do you get high fidelity depth in 3D?
I tested rather extensively on 10.8 and 10.7, and have no issue (in fact, working on a 3 kinect show using the software), so im not sure where this issue is coming from.
You do know that the Kinect depth from Kineme is lower bit depth, and not as accurate due to outputting an 8 bit depth image. Perhaps you are seeing that here. If you are just comparing the images visually, thats not really an accurate way of determining fidelity of the output, since the v002 Kinect outputs a floating point image, ranges in – (less than 1) and + (greater than 1), and the Kinect outputs an 8 bit depth image, 0 – 1, in 256 increments, clipped (so values above 1, get crushed to 1, and values below, clipped to 0).
What.. exactly are you trying to do?
The only gotcha is getting to IOSurfaceRef, so you can lock for pixel buffer access, right @bangnoise (unless they do a glReadPixels or other type of OpenGL asyncronous read back).
Not sure what you are seeing. Is Unity or OF applying nearest neighbor filtering when drawing the image? Can you send / post a screenshot?
Few options.
One, fiddle with texture filtering in OF or whatever is drawing and make sure it uses bilinear filtering when drawing.
Two, apply a morphological based AA filter like FXAA (we have an implementation for QC on the v002 QC plugins page you can look at) in OF.
Three, in SVN on Google Code for Syphon Framework, on trunk branch, we have an newer version of Syphon Framework which implements options that allow your to specify depth, stencil and MSAA options for rendering into a Syphon Server. That may not be much help due to Unitys render engine, and how the plugin sends frames (normally sending an already rendered texture that was from a camera, so you have no opportunity subvert Unitys renderer). Maybe you could finagle something there but Unity is super finicky about OpenGL State and inserting things into their rendering path.
And finally, my suggestion is to use Unity’s post processing shaders, and send the output of their FXAA implementation, and use that as the source texture for Unity.
That or option 1 sound good. But, without more info, im not sure what the issue is.
Well, to be fair to Apple, the new Retina MBP’s do support a ton of shit that the old OS wont be able to use, stuff they dont advertise that well, like hardware accelerated AES instruction sets, which FileVault can use so that encryption works super fast, and almost 0 cost to the CPU.
Same for the new Airplay Mirroring APIs. 10.8 does leverage hardware in ways 10.7 can’t. *shrug*
Interesting.
I suspect part of this is due to weirdness of floating point image support in OSX prior to 10.7 and 10.8 – many bugs have been fixed that allow floating point in OpenGL and in QC to wok better. There may also be an issue with driver support for that hardware.
Any chance you can try this plugin on 10.7.4 or 10.8.1 ?
Thanks.
Awesome. I just realized I forgot to comment in a set of lines above the scrollback. Do one more pull, then you will have a bit of a performance boost (I commented out some texture submission optimizations, to see if they were causing an issue, and forgot to comment one set of those back in).
Thanks for getting back to us that you are in the clear. Appreciated.
Thanks for the report. Can you try a pull off of the github, and see if the latest commit fixes it?
I was able to re-create (sorry about that), and think the fix is pretty easy.
Hi.
Sorry for the late reply – I was traveling. Thanks for the report. This is a known issue, and we seem to have it fixed.
Here is a new version of the v002 Movie Player. This is an experimental build, it has some new code which is an attempt to fix some performance problems which we inadvertently introduced in Beta 4. This also has the fix for 10.7 and 10.8 exception throwing in the QC Editor when stopping the composition or disconnecting the object.
Thanks.
http://v002.info/downloads/beta/v002%20MoviePlayer.plugin.zip
This is marked as Beta 5 – please let us know here how it works for you.
We dont have any plans to make a Serato plugin. That said, contact the developers – Syphon framework is free and open source, they could implement it pretty easily.
Just as a note, this is marked as Beta 2 Release 2 (in get info), so you know what the versions are. Thanks.
Thanks. Bangnoise and I took a look at this, and think we nixed the issue. Any chance you can try out this build and report back?
I realized I was testing a version with some changes, not the release (apologies for that) – and was able to re-create.
This linked build should have the fixes for your bug – as well as a fix so that when a Syphon Server is publishing an image that is disconnected, or is sent a “nil” image, it continues to send the last frame, and doesn’t “vanish” (a request from other users).
Please let us know how this works for you, and thanks for finding and reporting the bug.
http://syphon.v002.info/downloads/SyphonQCBeta2R2.plugin.zip
I still cannot reproduce here, but @bangnoise can. What computer, OS, and GPU do you have?
Hrm – I can’t re-create this here.
https://dl.dropbox.com/u/42612525/Syphon%20QC%20Issue%2020.zip
Resizing the Servers viewer seems ok with both GL and Image input, client always outputs an image – but I do get some occasional visual garbage if using OpenGL mode and resizing quickly.
