You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered an issue with MediaInfo not returning some metadata for an MXF file in a newer version of FITS ( toolname="MediaInfo" toolversion="22.09"), vs. FITS 1.5.5. (toolname="MediaInfo" toolversion="0.7.75")
There is a regression for sure as I see well the channel info in the file.
But files says that channel layout is EBU R48 "2a", so stereo (L+R) and D-10 audio stream says that 4 channels are active, so it is incoherent. What is the truth? As it is SD content, I would bet on stereo and I think that I'll show something like "L R ? ?" instead of previous "L C R, LFE" (I am a bit lazy and don't plan to look for the source of this info in the past).
My main concern is getting the metadata that had been available before.
I checked with (the very old, 7 years) 0.7.75 version, and "L C R, LFE" comes from the idea that a 4-channel is by default "L C R, LFE" but in reality SMPTE ST 365 (D-10 Audio) and SMPTE ST 331 (the SDTI storage format used in this MXF) indicate the count of channels but no default channel mapping, so we removed this output on purpose and it won't be available again because it is wrong.
But in the case of your file, we see another piece of metadata, from AS-11 UK DPP (which was not supported in 0.7.75) so we plan to add "L R" (because AS-11 UK DPP metadata in this file says that) even if it is a 4-ch track.
I discovered an issue with MediaInfo not returning some metadata for an MXF file in a newer version of FITS ( toolname="MediaInfo" toolversion="22.09"), vs. FITS 1.5.5. (toolname="MediaInfo" toolversion="0.7.75")
The 30MB file I used is in this share drive:
https://drive.google.com/drive/folders/1kWy6yRxyDLhkVtSbFwTBPZa9TgPPnV63?usp=share_link
MXF_44_1_1_fits.zip
The issue was reported in the FITS project here:
harvard-lts/fits#369
Thanks
Paul
The text was updated successfully, but these errors were encountered: