![]() ![]() ![]() The "key frame interval too high" problem is not related to the macOS version or SecuritySpy version: they key frame interval is decided purely by the camera itself based on its settings, and SecuritySpy has had the same tolerance for this for many years. My Mac is setup to give a different set of addresses on the vlan, and it also sees the request and makes an offer, but apparently too late, as the camera has accepted the one offered by the router. ![]() The problem is the cameras' DHCP requests still get seen by my broadband router, and the cameras end up with the wrong address. But I haven't quite figured out out to program my NetGear switches to avoid broadcast traffic leaking from the vlan to the untagged network. I have also attempted (and failed) to isolate the video traffic to a subnet, so that my own intranet would not see the video traffic at all. For the record, I upgraded the main backbone to 10G (which can go directly into the Mac mini at 10G), and other switches aggregate traffic into the 10G switches. I have been attempting to reconfigure the network, so far unsuccessfully, but I don't think I have done anything that should affect this issue. I don't recall seeing these (or perhaps seeing them so often) previously.įailed to record video frame 5575,818 The key frame interval from the network device is too high, locate and change this setting in the device (may be called I-frame interval / I-frame rate / GOV length / Intra frame period)) I am indeed seeing a much higher frequency of SecuritySpy errors with Catalina, all regarding the key frame interval being too high. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |