Cyril Concolato

The email said free-form because I wasn't really aware of ``. Now that I know it, I'd like a mix of free-form (maybe through title) and URL + assert id...

Initially what I had in mind was something like: ``` The following links point to invalid files exercising the "shall" above. They should be reported as invalid by validation tools....

@tabatkins any thoughts on the above?

@tabatkins what can I do to help here?

This reminded me of https://www.w3.org/TR/rex/

Sorry, I should have provided that info. Here it is: npm version 5.3.0 node version 8.4.0 [email protected] tsc was not installed. Installing it (v2.5.2) does not change the situation.

If you have a mp3 JavaScript parser, that would be doable. It's not in the roadmap yet though.

Actually, the ISOBMFF spec now says that: > the 'codecs' MIME parameter may document the original format, if the environment using that parameter separately documents the existence of transformations such...

Thank you for the details. I was not aware that Android's native media player did not support fragmented mp4. It is not possible at the moment to write unfragmented mp4....

mp4box.js does not support generating non-fragmented files. Do you have more details on the use case? All players that support fragmented should support non-fragmented. Also, have you considered using MP4Box(.exe)...