Thanks for the report, please check out latest develop with the fix.
Stereo depth decimation filter not correctly setting data size
Hello @GergelySzabolcs, running into the same issue with release v2.24.0.
I notice that the device-side firmware is controlled via the CMake variable DEPTHAI_DEVICE_SIDE_COMMIT
. I see you updated it in this commit in the previous conversation to b3aeaf23ff5857fc8f79d412ceefc08da23e7aad
, but as of v2.24.0 it is currently a95f582a61ec9bdbd0f72dec84822455872ffaf7
Is there a chance that this was regressed to the previous behavior during development? Also, do you have a changelog of device firmware releases? The single hash is a bit opaque to debug the release history.
Hi amusco-outrider
Thanks for reporting, will check at the office tomorrow.
Regards,
Jaka
Any update on this?
Hi amusco-outrider
Shouldn't be a problem, tested with 2.24.0.0 main branch, the output size was (460800,) 640 360
. Any other info you could provide?
Thanks,
Jaka
Hi following up here
I can confirm I am no longer seeing this behavior on v2.25.1.0 with python however I am still seeing it with the c++ API
@jakaskerl Kind of what I figured which is weird, let me get a minimal cpp example together and I'll post it
- Edited
Sorry about the delay on this one, I created a minimal example and could not reproduce the issue
But then I tried setting all the configs to be the same in the full pipeline and the problem manifested again.
After some digging it seems that using `stereo->setDepthAlign` is causing the issue, it seems to scale the resolution to the targeted socket (expected behavior) but ignores the reduction from the decimation filter
Interesting, I am aligning it to a depth camera frame (e.g. left mono)
For reference these images show the difference in what is output with setting the depth align and not setting it
Here is the depth image output with setDepthAlign used
Here is the depth image output without setDepthAlign used
@jakaskerl Cool thanks!
Sorry for the roundabout explanation of whats going on