Primary and secondairy steams resolution confusion?
CompletedSummary
In NX Witness a camera by default shows a 800 x 480 stream. Changing the resolution from "auto" to "low" resolution makes the stream 1920x1080. The "high" resolution stream is 800 x 480.
Environment
- Nx Witness Version: 5.1.0.37133
- Client OS: Windows 10 Pro 19045.3086
- Server OS: Ubuntu running Docker (latest available image)
- Network Topology: 1 VM running Docker with NXWitness and a single DHI-VTO2202F-P. All wired in the same network; Docker uses macvlan.
Reproduction Scenario
- Start NXWitness and auto-detect the camera.
- Fill in the credentails.
- Open in the camera view and press "i" to view information.
- It will show "Hi-res" with a resolution of 800 x 480.
- Right clicking on the camera display and selecting "Resolution" -> "Low res" will show "Low-res" with a resolution of 1920 x 1080
- Opening "Camera settings" -> Advanced will show primary stream with 1920 x 1080 resolution and secondairy stream with 800 x 480 resolution. Resetting both stream to default will pick those resolutions.
Expected Behavior
I expect "Hi-res" to be the higher resolution stream and "Low-res" to be the lower resolution stream.
Actual Behavior
In NX Witness a camera by default shows a 800 x 480 stream. Changing the resolution from "auto" to "low" resolution makes the stream 1920x1080. The "high" resolution stream is 800 x 480.
Additional Information
Motion detection complains about the resolution of the secondairy stream to be too high for motion detection. Changing that to the primary stream fixes that.
On previous versions this seemed to work as expected.
-
Hi Robin Brouwer,
I hope this message finds you well. While reviewing our community discussions, I noticed that there hasn't been a response from other community members regarding your query. Could you please confirm if your question is still relevant? If so, I'd be more than happy to explore ways we can assist you.
Best regards.
0 -
Hey Norman,
Thank you for reaching out to me. The question is still relevant as the issue still exists on my current version Nx Witness Version: 5.1.1.35712.
Best regards,
Robin Brouwer0 -
Hi Robin Brouwer,
I transferred this topic into a support ticket, and our support team will work with you to investigate the issue.
0
Post is closed for comments.
Comments
3 comments