Nadahar

@valib It sounds like you've had a really bad situation. It's a bit strange to take in that a "small accident" can give so serious consequences. It's certainly a reminder...

@Sami32 I takes a bit of time for me too to come up with something, especially since part of the H264 level code was very... unstructured. I've tried to clean...

@Sami32 I did spend 2-3 couple of hours on this, so it didn't take me 10 minutes 😉 If I were to use the GitHub editor or Notepad, I don't...

@Sami32 Their level will not be parsed - this has nothing to do with parsing the profile. How could one parse level from that? I can take a look at...

@Sami32 Maybe it was copy/haste? Space will make it not parse yes, as none of the examples I saw had space. It's easy to modify the regex tough - or...

@Sami32 I put "my commit" first and your second. Unfortunately there were so many conflicts between them that when I removed everything from the second commit that conflicted with the...

@Sami32 Sorry, that was my fault - I forgot to include the examples and didn't see that they could have spaces in them. The regexes is now updated to :...

@Sami32 > In my code i leaved this other AVC level sample as well: Stereo [email protected] / [email protected] > > And this case is not correctly handled here. Both of...

> Why LEVEL ? is that in a standard specification ? This isn't only designed to interpret the specification values, but user configuration values as well. Remember that it's case...

@Sami32 The case-insensitivity flag is set in Java, outside of the regex-string. Therefore, when you test the regex outside UMS, add ```(?i)``` in front to get the correct result, e.g:...