John Pale
Forum Replies Created
-
I’ve never used this, have no connection to this company and cannot vouch for this service, but these guys claim to be able to repair corrupt MXF files…
https://aeroquartet.com/movierepair/fix-mxf-files.en.html
-
The files appear to be corrupt. Other than going back to the original files on the camera cards, I don’t think there is much that can be done. Sorry.
-
Archiving becomes obsolete once time travel is perfected, Warren.
-
I’m guessing this applies to Avid DNXHD/HR Quicktime files…but would MXF still be readable? I wonder if re-wrapping the files to MXF would get around this.
On a related note….in Mojave, I get the warning that QuickTime 7 player is 32 bit and will be unsupported in future releases. This means that only the severely limited Quicktime X will function. Ugh.
-
That Date/Time Digitized column is additional metadata that is burned into the file, but is not normally able to be seen in Windows Explorer or Finder on a Mac. It’s part of EXIF data generated by the camera. Premiere (and Photoshop) read this data and rely on it more than Windows or MacOS. I’d look at the camera that created the files and adjust the date/time on it.
If you want to see for yourself, right click on the top bar and select “Metadata Display”. Do a search in the search field for Date Time Digitized. You will see that metadata is in the EXIF Schema for EXIF Specific Properties. This is not part of the standard set of metadata that you see displayed in Premiere or Windows Explorer/Finder.
-
There’s probably a better way to do it, but several times I’ve duplicated the clip and masked out the subject, subtly applied keyframed blur (only a very small amount) to the background clip, so that the focus appears to change a bit. The lens blur in AE might be more realistic, but in many instances the difference isn’t so great that I feel like it’s worth the extra time to round trip.
-
Its always been like that with track based keyframes. (consider the track a container, which can have its own keyframes, regardless of what you put in it)
Use clip keyframes if you want them to move with the clip. -
512 MB is really low and falls below what is supported for GPU rendering.
https://helpx.adobe.com/premiere-pro/system-requirements.html
-
They are cheap because Avid end-of-lifed them. They won’t work with any recent OS and they are pretty specifically for an Avid environment. Don’t waste your time and money trying to use them for what you need to do. The Adrenaline hardware barely worked Adequately for the purpose it was intended.
-
I haven’t updated yet….but this was a problem a few years ago when using third party I/O cards. I have Blackmagic. An update from them fixed it.