You say every .mxf file; do you mean every .mxf file from that same source, or does the same thing occur when using a new .mxf file, that PPro (or AME) have rendered?
Did previous versions of PPro not encounter any problems, with the same .mxf files?
I had a bunch of those in a project I just finished. Ran chkdsk on my array and it found errors. I deleted the file, ran repair, then re-uploaded the file from the chip. Worked fine.
Has me worried about my 5-drive array that's 4 years old, though. Want to switch to M.2 but too expensive for now.
> I Don't change anything, problem start in autometicaly
Something must have changed, or you would have always had this problem. 🙂
I can't get the file you provided to misbehave.
Can you provide a project containing a sequence that references this media, as well as the output preset (.epr file) in use when you do encounter errors, using this media?
It may not make any difference, but Media Browser supports additional metadata from card-based file structures (when available), including spanning clips (>4gb). Drag-n-drop import misses that information (which means it's not likely to be involved).
If you reinstall Premier or move back to a previous version and the issue persists, the problem has to be corruption in the media file that's dropping frames. I cured it by deleting the file, running chkdsk with repair (windows), then re-importing the file and it worked fine. I'm sure theres a disk check utility for Mac that can repair a corrupt sector. Run that and see if it reports any disk errors, then run the repair and impot again.
In rare cases a cosmic ray can corrupt a bit on a disk, causing it to work one day and then not the next, or the disk surface starts to fail for no good reason. SSDs are not impervious to glitches either. Since it worked for a while then quit, the original on the card is probably OK. Hope you haven't wiped the card yet. (I always back them up to another drive before wiping a card.)
Hello, had the same issue with converted .mxf files.
Here is what our strategy was that seems to fix that issue:
1. Shift+Premier - delete cache files.
2. Do not open projects, just Premier and delete All cache files through preferences
3. The most important: Delete the local user account Windows cache by the folowing steps:
Initial Steps (Enter Recovery Environment):
Enter Recovery Environment (If you are unable to get into the recovery environment via a menu, you can turn off your system during the initial boot when the Windows logo is on the screen and the dots are circling. Do this at least twice and you'll see the message "Starting Automatic Repair").
Once the recovery environment loads select "See advanced repair options", then "Troubleshoot", then "Advanced options".
Change directory to your boot drive if necessary (for example, type c: and press <ENTER>)
Type "CD %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches <ENTER>
Type "DIR <ENTER>" and make sure you are in the right path. You should see one or more .db files -- usually just cversions.3.db. If there are no files in this directory see the addendum below.
Type "DEL *.* <ENTER>"
Reboot and test
Method #2 (Via Safe Mode and File Explorer - may require adjusting permissions):
Click"Start-up Settings" and "Restart" to reboot the system and get the option to enter Safe Mode.)
At the Startup Settings screen press "4" to boot in Safe Mode.
Log into your administrator-level account.
Open File Explorer and browse to %windir%\system32\config (example: c:\windows\system32\config)
Gain access to systemprofile (you may be able to just double-click it to gain access)
Drill down to %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches
Delete all files inside caches
Reboot and testFinally, create NEW Premier Project and import old project assets (sequence by sequence).