-
|
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 14 replies
-
|
Arrows up/down bext to the number points the stream directions so: |
Beta Was this translation helpful? Give feedback.
-
|
Sure, the most important thing is to adjust the settings to your own requirements, I just wanted to be sure you are aware of the consequences in the form of an increased lag. If you have an alternative for |
Beta Was this translation helpful? Give feedback.
-
|
On the other hand, you're using a slow USB 2.0, which unfortunately favors compressed MJPEG (BTW it may have cause problems with HyperSerialESP32 described on the HyperSPI project as well). You must do some tests and assess which grabber setup produce lower lag and has lower impact on the CPU. |
Beta Was this translation helpful? Give feedback.
-
|
Good point, the only thing is, if I want 60 FPS with YUV there is no option: |
Beta Was this translation helpful? Give feedback.
-
|
Don't you have nv12 (on ms2109 I supposed, maybe nv12@60 works only on Windows)? If not then with MJPEG@60. |
Beta Was this translation helpful? Give feedback.
-
|
I do not have nv12 with this grabber. Running on a pi 3b. I will switch to MJPEG@60, any tips on resolution? |
Beta Was this translation helpful? Give feedback.
Arrows up/down bext to the number points the stream directions so:
USB grabber: captured~600 frames and forwarded to HyperHDR instance ~600 frames.
Instance: received and processed (including image to LEDs colors processing) ~600 frames. On the output (also ~600) is not the image anymore but LED colors.
You have a smoothing enabled so the smoothing received 600 LEDs strip colors and forwarded 5000 final smoothed LEDs strip colors to the LED device (not on the screenshot but can be read from it).
LED device received 5000 LED strip colors and successfully wrote all of them (5000) to the physical device.