+1New user here! We have the ruleset “preservica-default-video-transformation” defined in the access representation section of our preservation policy. The policy is set to run on ingest and dynamically, and apply everywhere.
As I understand, this should migrate video files to MP4 upon ingest, but currently, no MP4 files are being created. The video files we’re adding are .mov / quicktime / x-fmt/384 - and this file type is included in the ruleset. Any ideas?
Best answer by chriskemp
Hi Alison,
I'd suggest trying to run the Create New Representation workflow against the .mov assets one at a time - this workflow is currently in Classic only.
From that point it's a waiting game - the workflow should progress through the following steps:
Once complete, you should be able to play the new .mp4 access representation in both Classic and New Gen.
Hope this helps, and please post back if you need more help!
I would expect a migration to happen, yes. If you look at the monitor, does it show any information about attempting to do it?
+1Hi Richard,
Thanks for replying! No, it doesn’t attempt to migrate. I’ve just tried a new file and watched the process through.
The upload display identifies the size and format correctly (video/quicktime), then runs through the following processes while preserving:
Our policy’s pretty basic, and I can’t see anything that would cause a conflict. We have Preservica’s default normalisation rulesets for documents, spreadsheets and images, then default access rulesets for documents, spreadsheets, images, audio and video. According to the video ruleset, video/quicktime is supported for mp4 migration. Grateful for any suggestions!
Alison
+1I’ve just had a look at the process monitors in the classic dashboard - there’s one failed process in the post-ingest tasks for the file - “Timeout executing tool /usr/bin/ffmpeg on file”. Does that shed any light?
+1Digging more into the reports in Classic, I can see it flagged in the Assets Not Matching Policy report, under RepresentationCreation.
Also, in Administration > Background tasks, there are 6 failed tasks (type = migrate) that correlate to 6 ingested .mov files.
So the policy would seem to be set up correctly. Is there anything else I can try?
Thanks,
Alison
Hi Alison,
I'd suggest trying to run the Create New Representation workflow against the .mov assets one at a time - this workflow is currently in Classic only.
From that point it's a waiting game - the workflow should progress through the following steps:
Once complete, you should be able to play the new .mp4 access representation in both Classic and New Gen.
Hope this helps, and please post back if you need more help!
+1Thanks so much Chris!
I tried this out - it still didn’t produce an access rep. The report at the end recorded an error during the ‘migrate batch’ stage. The error message was ‘timeout executing tool /usr/bin/ffmpeg’.
I now have screenshots of the process and resulting error, which is really useful, so will raise a ticket in the meantime.
+1This has now been resolved through the service desk, who extended the timeout limit for their migration tool. Hope this helps someone else : )
Alison
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
