Thanks Anton,
I tried with Alpha 64 & 32 but no menu in VL to go in Commandeline.
When I go to User…\Documents\vvvv\beta-preview\Packages> nuget install VL.Devices.RealSense -prerelease
Nuget is not recognize…? is this normal
In User…\Documents\vvvv\
there is only beta-preview…
Don’t see how to do.
A
Ok it’s works, Thanks for your help.
Great work @robotanton ! Works out of the box and as aspected. At least the vvvv Gamma part. :)
The range for the D435 and D415 are specified at ~11m. Well… didn’t expected good results in this distance, but my cam (D435) seems so be limited already at a depth of 3,7m. Tried different settings and light-situation but nothing really changed. What did you exprienced @robotanton or @u7angel, what was your maximum z-depth with the RealSense?
Just found the threshold for the depth-clipping. So: Everything is awesome!
Any chance, to get a “raw” depth image coresponding to the Kinect-depth image with floats in the R-channel for the distance in mm?
Searched fo it and tried several node-combinations and channel-settings for the depth-stream inside the “Config”-settings of the RealSense-node. But no success. Also the “Depth (Raw)”-node seems not work as expected.
Good news though: We managed to add the PointCloud-output as pos-buffer. Which works out of the box with DX11.Particlepack. So, fast homebrewn gpu-pointcloud-visualizer: ✔
But would be nice to also approach this texture-based, as described above. Any ideas?
@timpernagel Could you please provide an example or just explain the way to have a homebrewn gpu-pointcloud-visualizerGpu-Pos-Buffer in V4 with Particlepack ?
@Aurel will look into the realsense-project by the end of the week and will post the steps what to do here.
I just received my D435i, super tidy little camera! I have loaded up the demo patch, but not sure how to get it out into V4, and then how to pull that data into V4 to manipulate it, be that the pointcloud, or jhow to pull the video feed out into a dx11 renderer. Pretty exciting stuff!
@Aurel @SuperflysiNZ Here you go:
Just start the “START_Realsense.bat”.
The pack includes an modified version of the realsense package of @robotanton . What I basically did is to add direct vertex-buffer-output to vvvv:
Did also some “cleaning” of the main-vl-patch and only enabled stuff I need for the pointcloud. So note, that there is currently f.e. no RGB output.
hey all,
was patching with the Realsense when this error popped : stop() cannot be called before start() (full log here).
cannot give more details for now, will edit this post if that happens again.
cheerz!
Hey guys,
I am trying to get the RealSense running in VL, my D435(latest firmware) is recognised by the RealSenseCamera Node but I can’t get it to run. No red nodes or errors, the camera works in RealSenseViewer.
TTY Renderer in vvvv says:
TMPluginWrapperNode.Evaluate
00:11:24 ERR : Cannot access a disposed object.
Object name: ‘Config’.
Same thing happens on different machines/fesh installs/etc.
Does anybody have an idea what could be the problem?
Thank you!
Are you using it in beta or gamma?
If beta, please check the blog post here to get the version info of the last nuget compatible with beta.
You’ll have to wait for beta 40 to use the latest nuget again, because the VL shipping with beta is currently outdated.
@readme Thank you, that works! :)
Another VL noob question: It only works in the overview application patch, but not if I patch it in a template. Is there a way of using the overview patch as a subpatch inside of a template.value patch?
Thanks!
can you say what exactly doesn’t work in that case?
@joreg In that case isRunning stays 0 and no textures come out of the RGB, Depth, etc nodes. However I can choose the camera at the RealSenseCamera node. Sometimes there are errors in Pipeline or Config.
Thank you!
we’ve completely reworked this library. most notably you can now conveniently apply all filters in chains.
latest nuget requires beta>=40 or gamma >= 2020.1.3
@redisgreen please test again now and report.
