You really do sound biased.
You are criticizing Milestone for naming their VMS 'XProtect'??? That's like someone objecting to Avigilon naming their VMS 'Control Center'. Both are product names and fairly generic ones at that. I don't see a reason to object to either.
HDSM is marketed as a technology, and a major claimed differentiator, not simply a brand name, ergo the debate about what it is and what it does.
Chesapeake & Midlantic
No, I agree. It absolutely is misleading and unethical for one manufacturer to have an advantage over another just because they managed to think up a cool product name first. I think that the only reasonable solution would be for all manufacturers to be forced to refer to their products by code number. Instead of "XProtect", it'll just be "Video Surveillance Recording Software Product NCC1701-D" or whatever.
Really, this is the only fair solution, I think you'll agree.
-Sent From My Mobile Telecommunications Device Designed in Cupertino
I was implying that if vendor a does a half baked proprietary version of something as complex as video compression, and the base name of the compression algorythm is a basic protocol like ONVIF or a base h264 compression and a vendor puts a spin on it, let's not get all stuffy trying to hold them accountable to be true to some ultruistic standard, where one firm claims to be complaint while accusing all others of bastardizing the standard.
Yes, I'm guilty of bias to the extend of us knowing and caring very little about about the technical features of the vast majority of competitors. We provide and warrant our solutions based on what we know well, and are willing to write checks to gaurantee the results. Let's all make our clients happy with whatever we choose to sell and support and we all win. Attacking product A or B, in an educational forum is BUZZ KILL.
if HDSM2.0 (trademarked name) is a derivative of SVC, then so be it, and referring to something their marketing department might dream up, and how they present it as misleading, has a negative undertone. The original HDSM1.0 was an adoption of wavelet compression, and if HDSM2.0 adopts portions of SVC, and are able to enhance it their benefit their is nothing misleading about that. The following article does a good job of explaning basic SVC as a building block, not the end-all be-all, and every I'll defend every VMS company's freedom to innovate and dream up new names for enhancements to basic technologies. Reading the available documents about HDSM 2.0, they've incorporated the basic H.264 SVC extensions, and created a proprietary extension to further divide the frames. a good article on basic SVC is http://www.robotics.net/2013/02/04/reality-of-h-264-svc/ for unbiased details.
If there was a button to nominate a thread to "Pointless discussion of the year", I would click it on this thread. It's not even clear (to me) what is being discussed here.
Good job of distortion. This thread is a derivative of another complaining of AV not officially stating that HDSM2 is adopting one o more h.264 SVC extensions. Is avoiding any public announcement specifically stating that Misleading?