- Mar 10, 2014
- Reaction score
What resolution is your sub stream?
Default setting for substream was 1920x536. I turned it down to other (and only other) option of 960x262 and that has dropped the CPU usage by about about 12 percent. Thanks for pointing me in the right direction!What resolution is your sub stream?
I'm running 20 cams on an i7-6700, so maybe it's time to upgrade.Yeah that would be it. I'm surprised you get such a large increase in CPU from such a small stream though. Your BI server must not have a very strong CPU.
What URL does it show you for remote access? I can't seem to get mine to connect to it after I loaded Hikvision firmware.Correct, yes. This one. These are my first Hikvision OEMs but they appear to run the Hikvision firmware--i.e., remote access uses the Hik-Connect, not AnnkeVision platform.
I access the camera locally through the IP address. Haven't set up remote viewing via browser.What URL does it show you for remote access? I can't seem to get mine to connect to it after I loaded Hikvision firmware.
Yes this is 1 of the issues I mentioned as wellI like the physical dimensions of the Dahua turret compared to the Hik/Annke.
But it has an unexplained problem. The video it produces is not nearly wide enough for the field of view, and it shows in the form of fairly severe aspect ratio distortion.
It is pretty obvious that this will be a problem just looking at the specs. The video's aspect ratio is barely any wider than a standard 16:9 camera, yet the field of view is about double the width.
Here are some samples from Andy that he shared a few pages ago. I've cropped a few pieces.
For a baseline, this is the "4K-T 1/1.2CMOS" (a standard 16:9 camera):
View attachment 145228 View attachment 145230 View attachment 145233
These are from the "4K 180" daylight pic:
View attachment 145229 View attachment 145231 View attachment 145232 View attachment 145234
See the problem? Things appear unnaturally tall. It is not just a display choice as is weirdly common in the CCTV industry. This is actually a problem in the source video. A little simple math done on the specs shows why this is happening.
Based on the specified field of view, 180° horizontal and 48° vertical, the height is about 27% of the width. (
48 / 180 = 0.267)
The video resolution actually produced by the camera is not even close to matching this. The video resolution is 4096x1800, so the height of the image is about 44% of its width. (
1800 / 4096 = 0.439)
27% is a long way from 44%, and that is why the distortion is so obvious. This camera should be producing a much wider image, given its field of view. I wonder if this is one of the "bugs" noted by @Wildcat_1 when he was preparing to review the Dahua 180° bullet? Anyway now that I've noticed it, I cannot un-see it.
Compare to the Annke/Hikvision dual-4MP cam. Its advertised FOV is 180° horizontal and 44° vertical, so the height is 24% of the width, and the video resolution is 5120x1440 so the height is 28% of the width. These numbers are much closer together, and this is why the Annke images shared earlier in this thread don't have a noticeable amount of stretching compared to the Dahua cam.
Some distortion is to be expected because they have to stitch together video from two different sensors and make it look good. But right now it is looking like Hikvision did a much better job of it. Hikvision's video is actually 32:9 which is exactly what you would expect from combining two 16:9 sensors. Dahua's aspect ratio is 20.5:9.
I stupidly forgot that I put a dummy IP address in for the gateway when I initially set it up, which is why it wouldn’t talk to Hik-Connect. Just wanted to let everyone know this isn’t a problem. Hik-Connect via P2P does mess up the stream settings for main and sub-streams though so I turned platform access back off and set the dummy gateway again, then setup my BI server as the time server for the camera also.After putting the hikvision firmware on yours can you still connect to P2P with Hik-Connect? I know we shouldn’t be, … I created a separate VLAN with internet access and can’t access my internal network, but I want to be able to connect P2P while out of town because I still don’t have my BlueIris setup fully yet and I can’t seem to get it to let me connect.
Yes he already got the turret sample last Thursday. bullet one video will be released this week. The 2 cams use same fw. So won’t be big difference.I want to see what Wildcat's review says.
am I slated for in-stock #2, #3, and #4? I call dibbs!Our cameras will be ready next week, so can start selling soon.