Thursday, October 1, 2015

Re: [Avid-L2] Help! MC 8.4 Media Drive Scanning Problem

 



Trouble is, I have no clue when Avid conciders a file to be corrupt.
It's not that hard to see if i file has indeed the correct metadata to be an Avid file, but that does not mean that MC conciders it a valid file...
 
So, I would nee as many as possible corrupt files, and even then that won't be a guarantee that it will work always.
 
On the other hand, it should be a breeze for an Avid coder to move corrupt files into the Quarantine folder.
 
 
Bouke
 
VideoToolShed
van Oldenbarneveltstraat 33
6512 AS  NIJMEGEN, the Netherlands
+31 24 3553311
----- Original Message -----
Sent: Wednesday, September 30, 2015 11:25 PM
Subject: Re: [Avid-L2] Help! MC 8.4 Media Drive Scanning Problem

 

Call me naive, but I've never really understood why no one has written a utility to ferret-out corrupt MXF files (hint, hint, Bouke).  For 20 years, Avid has displayed an acute lack of interest in addressing this issue (probably too busy differentiating Symphony from MC -- or rewriting the CC module).  However, I would think that some sort of batch utility that sequentially attempted to play every MXF file using, for example, the open source, MXF compatible VLC player, with a simple logging mechanism that stopped the batch process on the first file that could not be played back -- would somehow be feasible.  It would certainly be a utility that many, if not all, Avid-based editors and facilities would want to own.




---In Avid-L2@yahoogroups.com, <bouke@...> wrote :

Mc opens all files and extracts the metadata to put it in the database for fast access.
And yes, the files from another system should work, but if the scanning fails, something is very bad

Bouke

Sent from mobile





Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


__._,_.___

Posted by: "Edit B" <bouke@editb.nl>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (12)
this is the Avid-L2

.

__,_._,___

No comments:

Post a Comment