Fryemoon,
In regards to age ranges, I think those categories could grow organically ( yay! buzzwords! ) You could create different censorship contour profiles ( i.e. when Dad watches, turn up the violence -- hypocritical? possibly, but the power would be in your hands) First things first, however... let's try to do 1 edit
I'm having enough trouble getting my code to compile and accessing the different VLC_* data structures. This goes for blacking or pixelating a portion of the picture. I agree that would be desirable feature but also beyond the scope of a first attempt. First things first
MetalheadGautham,
Obviously I'm not done doing the edits ( and I'm not especially good at C/C++ ). Been working on a skunk-works project for work that should wrap up soon. Yes it should be easy, and if you're able to produce the code faster than I, please do! I'd much rather write Python code anyway
As far as creating a "new standard", I'm not currently aware of a standard format for specifying edits and then classifying those edits so that people are able to produce censorship profiles. Its not that tough to parse a text file -- writing code that lives all by itself with no dependencies is easy compared to trying to read other people's code that has grown over 10? years.
I looked at SubRip
http://en.wikipedia.org/wiki/SubRip to which MetalheadGautham alluded. True, it is a standard, but adding these features:
- edit type ( with very specific limits)
- multiple category ratings per section
Would so drastically extend the original SubRip spec that it would be nothing less that a re-write of the SubRip spec. I have no illusions about this code. If I ever get it working ( or someone else!) then it will probably not be accepted by the VLC community, and it will not spread to other free media players, much less media hardware like dvd players. The market for this feature is probably small and is also a politically incorrect group. So given these facts, who cares about conforming to a standard when this code is probably a singleton ( possibly an orphan) and no-one has even written any censorship files yet. I've also looked at JSON and YAML, ( as posted above, I do hate XML ), but none of these data formats express the idea of the edits with edit ratings properly. Really, this is just a bikeshed issue. Writing a parser for the data format I specified above, or traversing an XML tree are approximately the same difficulty, the parser is less than 5% of the total problem and is a problem I have solved before at work. I'm not trying to create an idiot-lect and I do know that writing a flexible language is extremely difficult, but I think the risks are relatively low. We can always turn around and specify a version at the top of the file and revert the idiot-lect at a future date.
Thanks for your thoughts guys.
Regards,
L{DiracDeta(t)}