Closed digitensions closed 1 year ago
Looks similar to issue #223
Can you provide the output report when trying to apply the policy?
mediaconch -f -fx -pv 1 -p <policyfile> <mp4file>
Thanks, here you go!
Ah I forgot to add the extension back on to the file before I checked, so pls ignore the extension fail. The policy checks the file prior to renaming without extension. Many thanks!!
I guess the problem is that the ""Duration field exists"" test fails?
You can modify the line this way:
<rule name="Duration field exists" value="Duration" tracktype="Video" occurrence="*" operator="exists"/>
But I will make a patch to also support the current syntax.
Thanks. I don't recall now if this error was present before but certainly the MP4 example I have used has passed MediaConch tests from V18. Appreciate your help. I can make that amendment to the policy and test to see if that's the fix quickly.
That fixed it, thank you! My mistake to have the 'exists' missing. Don't worry about a patch!
I have used has passed MediaConch tests from V18
It may have worked previously due to an unspecified default value for operator
attribute and it default value have changed with one update.
@g-maxime is it easy to consider default value for operator
attribute exists
?
A note for any onlookers, the change means that the pass statement is still returning a 'pass!' first, but then lists all the 'or' statement fails afterward which might impact how your automated processes read/understand the outcome.
Eg, pass! N_123456_01of01.mpv -- [pass: MP4 access transcoding checks] -- [fail:Video/Width is 1280] -- [fail:Video/Width is 1024] -- [fail:Video/Width is 768] -- [fail:Video/Width is 720] ....
My mistake to have the 'exists' missing. Don't worry about a patch!
This is a regression, so fixed.
Hi there,
Installed the splendid MediaConch to a new server this week, with Ubuntu 22.04.1 LTS. I'm running batch MP4 transcoding scripts for access copies across several servers, and have earlier installations of this software working fine on Ubuntu 20.04 (version 18). Both the new and old versions are using the same policy, pasted at the bottom of this issue.
The installations for this server for MediaConch (first use of mediaconch-server): libmediaconch0_22.09-1_amd64.xubuntu_22.04.deb libzen0v5_0.4.39-1_amd64.xUbuntu_22.04.deb mediaconch_22.09-1_amd64.xUbuntu_22.04.deb mediaconch-server_22.09-1_amd64.xUbuntu_22.04.deb
The MP4 files are FFmpeg encoded from varying preservation masters using similar FFmpeg command to this:
ffmpeg -i <infile> -map 0:v:0 -map 0:a? -disposition:a:1 default -dn -c:v libx264 -crf 28 -pix_fmt yuv420p -movflags faststart -vf yadif,crop=704:572:8:2,scale=1024:576:flags=lanczos -nosdin -y <outfile> -f null -
The policy is returned 'failed!' and listing items from the sections of 'or' policy that do not match the file, but not returning the ones that do match. Feels like a failure to notice it's 'or' and not 'and'. This doesn't fail in V18 MediaConch tests run against the same files in parallel. They pass fine.
I've also noticed some problems with mediainfo v22 reading MP4 files on Ubuntu 20.04, can give more info on MediaInfo issue tracker if needed and not linked.
Happy to supply and more additional data.
Many thanks! Joanna