Hi David,
A fairly straightforward way to use the latest MediaInfo library seems to be by using the "OLDXML" output option. This gives you the old style XML output with an additional root element around it, so it only requires a small change to the existing XSLT as far as I can see. The new style XML output from MediaInfo does look a lot cleaner, e.g. units are no longer part of the value, and there is an XSD. So it would be worth investing some time in rewriting the XSLT at some point, it can probably become a lot simpler.
I've implemented the "OLDXML" solution in our fork here:
(it also includes some changes to the pom file, the URL for the central maven repo seems to have changed)
I've included v20.08 of the MediaInfo libraries. For Linux I added the one for Redhat 7 x86_64.
I can create a pull request if you think that this is a useful solution for the time being, until someone finds the time to rewrite the XSLT for the new XML output. I haven't done much testing though, none at all on Windows and a little bit on Linux/Mac. I've tried the following setups:
- using FITS as a web service in Tomcat on a SUSE Linux Enterprise 15 SP1 server, using the MediaInfo library for that platform
- same as above but using the Red Hat 7 x86_64 MediaInfo library
- using FITS locally on MacOS 10.15.6 using the MacOS MediaInfo library
- using FITS locally on an Ubuntu 18.04 VM using the Red Hat 7 x86_64 MediaInfo library
All seem to work OK. I do experience some stability issues with MediaInfo on the server, it looks like it can't cope very well with multiple requests at the same time, but that's not new, we were having this issue with the currently included MediaInfo version as well. I had hoped that this would be solved by changing to a newer MediaInfo library, but alas...
I also got some test failures when building the application (Differences in XML for file ...), not quite sure how serious those are.
Best regards,
Paul