Closed conorom closed 6 years ago
Did a quick test on a mov format video and the additional step of excluding processing by Droid was required to get ExifTool output back. Fortunately I'm only interested in mp4 videos right now. Definitely seems like changing the characterization parsing to look for MediaInfo values per track is better than playing whack-a-mole with FITS configuration in the long run.
Out of the box, FITS now uses MediaInfo to produce the metadata for video, which separates metadata out into separate a/v "track" nodes in the XML. This means results won't be parsed correctly by the code here, which expects the format produced by ExifTool. I think this started in FITS 0.8.10
I guess either the parsing should be changed to handle MediaInfo's track-based output, or else steps should be documented on how to change
fits.xml
to get FITS to work with Samvera components. Perhaps by linking to this issue from Hyrax and hydra-derivatives READMEs, which (to my knowledge) are the two main places where recommendations on a FITS version are made.note: Most likely this affects all the formats listed for MediaInfo processing in
fits.xml
, i.e.:include-exts="avi,mov,mpg,mpeg,mkv,mp4,mxf,ogv,mj2,divx,dv,m4v,m2v,ismv,m2ts,mpeg4"
...however all my experience is with mp4, so the workaround mentioned here will focus on mp4.The easy workaround is to exclude mp4 (and/or whatever other formats) from processing by MediaInfo, thus reverting to ExifTool which will produce the output expected by
hydra-works
.FITS 1.0.5 is listed as "known to be good" in the Hyrax and hydra-derivatives documentation right now, so the steps below use FITS 1.0.5, but similar changes need to be made to get any version of FITS above 0.8.10 to work correctly with mp4s in the Samvera stack.
First, a sample of MediaInfo metadata output for a mp4 file, i.e. FITS 1.0.5 out of the box:
Now, steps to get the expected ExifTool output back. Edit
xml/fits.xml
:include-exts
for MediaInfoexclude-exts
for ExifToolexclude-exts
for FileUtilitynote: Without step 3, all recent FITS versions revert to using FileUtility, which results in empty metadata.
After these changes, the expected output is back: