ARAMP1
Pulling my weight
Well, I was making that harder than it needed to be. Thanks.
Wow, that dropped me down from around 30% to 1%.
5.2.7.0 - RTSP sub-streams for high-MP cameras
- Thread starter fenderman
- Start date
Wow, that dropped me down from around 30% to 1%.
1% seems a bit unrealistic... but if everything is working for you then that is amazing.
It wouldn't be that hard for Blue Iris to enable copy/paste from different resolutions and aspect ratios, just by re-scaling what you copied to fit where you paste it. In fact it would be great if Blue Iris gave you a list of resolutions that had motion zones defined for your camera and let you copy from each of them. But all of this requires work and someone would have to suggest it to the developer.
beepsilver
Getting comfortable
[/QUOTE]I'd like to give this sub stream feature a try. I have mostly all Dahua 5231 ZE cameras. How can I find what the camera's sub stream address for BI is? Here's an example of one of cameras. It's working in BI but that Main Stream address looks weird (/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif). Thanks!
Attachments
Very happy with this new feature!
I have turned on & selected sub-stream for all 28 cameras and now have CPU (at idle) sitting at around 10% instead of 40%
Stable with 5.2.7.1
Not stable with 5.2.7.2 (crashes when selecting individual cameras and have to kill the service to restart)
Good things take time.
I have turned on & selected sub-stream for all 28 cameras and now have CPU (at idle) sitting at around 10% instead of 40%
Stable with 5.2.7.1
Not stable with 5.2.7.2 (crashes when selecting individual cameras and have to kill the service to restart)
Good things take time.
On all my Dahua cameras (including 5231 ZE)..... I used /cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
(i.e. copy and paste your main string but change the zero to a one under "subtype"
Thanks! Have you tried using sub stream 2? Just curious because it has a 1080P option and I could use it with a low frame and bit rate.
I
[edit=forgot to enable substream 2 in the camera... just did that and now it works on BI at 1080p using subtype=2]
just tried 1080p with subtype=2 and it did not work for me
[edit=forgot to enable substream 2 in the camera... just did that and now it works on BI at 1080p using subtype=2]
cool
5.2.7.2 worked for me..... until I tried to maximize individual cameras. At first it worked (and showed the full resolution stream when double clicked on a camera) but after several cameras were switched to sub-stream, it became unstable and would crash when individual cameras were selected.
Happy enough with 5.2.7.1 for now
The most significant improvement for me is UI3. Before this upgrade, the CPU usage would go up to nearly 100% when someone logged in with UI3... now there is hardly any change in CPU usage - this is a massive improvement over just using "limit decoding" which is what I was using before, to keep 28 cameras [~1300 MP/s] down to an acceptable CPU load
5.2.7.2 worked for me..... until I tried to maximize individual cameras. At first it worked (and showed the full resolution stream when double clicked on a camera) but after several cameras were switched to sub-stream, it became unstable and would crash when individual cameras were selected.
Happy enough with 5.2.7.1 for now
The most significant improvement for me is UI3. Before this upgrade, the CPU usage would go up to nearly 100% when someone logged in with UI3... now there is hardly any change in CPU usage - this is a massive improvement over just using "limit decoding" which is what I was using before, to keep 28 cameras [~1300 MP/s] down to an acceptable CPU load
I always use UI3 to view cameras so hopefully it won't be an issue for me. I have 11 cameras running, CPU used to be around 45%. Now it's running pretty steady around 18%.
CPU usage got wrecked because you did not disable "Require/decode all camera frames when streaming" here, which is enabled by default.
I also just see BI crash when I double-click a camera. I never saw it open the full resolution stream. Afterward, I had to kill BlueIris.exe (running as service) before the local console would re-launch successfully.
ahh, I see. thanks for that... I had a feeling I had missed something out somewhere. Love your work!
bit of a weird issue for me... when i setup substreams I setup now motion detection rules... I came from A, B, C, D, E zones to just a simple "A" zone.
However, whenever I playback the last motion detection, it seems that it is still adopting the OLD motion detection rules (zone crossing) rather than the new A only zone?
However, whenever I playback the last motion detection, it seems that it is still adopting the OLD motion detection rules (zone crossing) rather than the new A only zone?
Wow. This could be HUGE! If this works! My cameras support two different stream formats.. if I could take advantage of hardware acceleration of h264 for live view on the substream AND high quality direct to disk space saving of h265 for mainstream. I’m sold
bit of a weird issue for me... when i setup substreams I setup now motion detection rules... I came from A, B, C, D, E zones to just a simple "A" zone.
However, whenever I playback the last motion detection, it seems that it is still adopting the OLD motion detection rules (zone crossing) rather than the new A only zone?
That makes a certain amount of sense
Another reason why BI should be taught to rescale motion zones and use only one motion zone set regardless of resolution. I guess you should tell BI support. He probably won't respond but hopefully will see your message and put it on his todo list.