-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in v2.15.0: color stream shown blank in realsense viewer exept for YUYV #2306
Comments
Same situation. With v2.16.0, the color stream works only in YUYV format. |
Same issue here. Verified camera is working properly by seeing expected outcome on a Ubuntu 16 laptop. For what it's worth, issue seems to be affecting realsense ROS interface. Echoing /camera/color/image_raw only returns zeros, hence a black screen. |
[Realsense Customer Engineering Team Comment] Thank you for pointing out this issue! We were able to replicate the issue with RealSense Viewer in Ubuntu MATE and will work to create a fix shortly. |
Yes, seems to be affecting all non-x86, non-Android platforms. |
The tabbing is off in that file actually. What you need to do is tab over the #ifdef AVX2 block and add an extra #endif after line 606. This fixed it for me. |
@dorodnic Would you like me to fork it, fix the bug, and make a pull request? |
Should be resolved in v2.16.1 |
[Realsense Customer Engineering Team Comment] Able to confirm v2.16.1 resolves color stream issue in previous versions of LRS. We will close this issue now. |
Issue Description
I open realsense viewer and start color stream in RGB8, which results in a blank screen.
Depth, infrared streams and color stream in YUYV format work fine. The only color stream format that works is YUYV.
When I sync and build librealsense with "tags/v2.14.1" everything works correct (all color stream formats work). When I sync and build with "tags/v2.15.0" I get blank output for RGB8 color stream.
My kernel is patched and "hardware clock" is shown when I click on "info" in the depth stream window.
This is the console output - the last line with "Non-zero status (-71) in video completion handler." looks fishy:
[ 208.314353] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[ 208.335144] usb 4-1.2: New USB device found, idVendor=8086, idProduct=0ad3
[ 208.335150] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 208.335155] usb 4-1.2: Product: Intel(R) RealSense(TM) 415
[ 208.335160] usb 4-1.2: Manufacturer: Intel(R) RealSense(TM) 415
[ 208.335165] usb 4-1.2: SerialNumber: 812113024034
[ 208.368715] videobuf2_vmalloc: loading out-of-tree module taints kernel.
[ 208.374167] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) 415 (8086:0ad3)
[ 208.376065] uvcvideo: Unable to create debugfs 4-3 directory.
[ 208.376250] uvcvideo 4-1.2:1.0: Entity type for entity Intel(R) RealSense(TM) 415 RGB was not initialized!
[ 208.376258] uvcvideo 4-1.2:1.0: Entity type for entity Processing 2 was not initialized!
[ 208.376266] uvcvideo 4-1.2:1.0: Entity type for entity Intel(R) RealSense(TM) 415 RGB was not initialized!
[ 208.376272] uvcvideo 4-1.2:1.0: Entity type for entity Camera 1 was not initialized!
[ 208.376500] input: Intel(R) RealSense(TM) 415: Int as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.3.auto/usb4/4-1/4-1.2/4-1.2:1.0/input/input6
[ 208.376898] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) 415 (8086:0ad3)
[ 208.377249] uvcvideo: Unable to create debugfs 4-3 directory.
[ 208.377369] uvcvideo 4-1.2:1.3: Entity type for entity Processing 7 was not initialized!
[ 208.377376] uvcvideo 4-1.2:1.3: Entity type for entity Extension 8 was not initialized!
[ 208.377382] uvcvideo 4-1.2:1.3: Entity type for entity Camera 6 was not initialized!
[ 208.377592] usbcore: registered new interface driver uvcvideo
[ 208.377596] USB Video Class driver (1.1.1)
[ 380.462643] uvcvideo: Non-zero status (-71) in video completion handler.
The text was updated successfully, but these errors were encountered: