Basically, yes.
Put another way for a different perspective....
A key frame is not a measurable unit. In the abstract, it is conceptually a 'marker' relative to other variable units/intervals (frames, seconds) which ultimately determine the value of the key frame itself (in time) according to the nomenclature/terminology chosen by any given vendor of a given product.
This is precisely what drives me crazy when I see folks preach "Make absolutely, unequivocally, so help you God, sure that your I-frame is set to '1'." Compared to what if the vendor says 15 or 30 and Blue Iris folks preach "equal to the frame rate for best responsiveness and frame rate" -- which is a conditional Blue Iris caveat, not a 'feature' by any means.
Key frames provide different functional characteristics for different conditions and applications. That's why they can and should be changed when doing so can provide a more desirable result..., and also why more vendors are using a 2 second interval for H.265 hi-res cameras..., which show up as half of an I-frame in the BI status window and are all too often considered to be incorrectly configured cameras followed by "the I-frame must be set to 1" even if the vendor says 2, 10,20, or 30. Blue Iris says it should be ONE, dammit!
Granted, the general IP video standard is 1 key frame every second regardless of everything else -- or however one wants to muddy the waters with proprietary or brand based terminology. The point is, to proclaim it's the correct interval is just flat out wrong and incorrect/bad advice. And again, compared to what?
Sorry for the mini-rant. I yield the floor.
