Kieran
Kieran
> A service that for example supports H264 should not care what codec OBS uses to generate the H264 stream I completely agree.
> Unless the internal encoder IDs are made into a stable API This would be great, also you wouldn't need to post so much information about the machine if the...
Seems like a Snort bug, it wasnt supposed to work like that, even the snort client itself expects the URL to match
I think its important to retain the hash of the video being unmodifiable, maybe add a metadata correction event that links to the kind 21/22 instead?