-
Corrupt MPEGHD422 files
Shooting job for the last 3 days, on Sony FS7, 1080/30p recording on 128GB “G” cards. On two different clips, both about 2 to 21/2 hrs in length, on two different days and I think two different cards the clips are corrupt. When played in Premier Pro CC, newest version, they start with a bright red, solid frame that goes on for about 10 seconds, then I get video of what we were shooting, but no sound.
I put the clips in Catylist Browse and they play fine as do they in Edit Ready. I did a transcode to ProRes 422 in Edit Ready and the clip is fine and as expected…audio and video. Anyone ever run into this?
Also one more note and I have no idea if this is any way connected to the issue, but ur roducer was using a PC Laptop and wasn’t too swift in handling video files and he did his transfer first before i could do it on a Mac. Is there any way the files could have been corrupted in the PC before I got to them with the MAC?
Thanks…Jim Watt
-
4 Replies
-
Hi Jim,
no real answers for you but I have some suggestions.You may have a workflow problem. MXF supports the notion of “related” files and the FS7 is a big user of related files. What you need to do is to copy the whole card of data onto the PC [or mac]. This guarantees the Clip and its related files are together on your computer. Then when you drill down the folder structure in Premiere Pro the software can locate everything it needs.
When you use the XQD card as the source of data it will look fine there, the related files are together on the card.
When you transcode using Catalyst Browse the clips will also be fine because Browse will have pulled the related files together.When you say Premiere Pro shows a red screen I’m guessing the screen isn’t just red, it will contain a message about corruption in multiple languages?
It is possible that Sony have made changes to the format of the data and Adobe has not kept up with the changes however as your format is MPEGHD422, which is now well established for broadcast acquisition, I think that is unlikely.
The best way to deal with this is to try and get a short clip that reproduces the problem and then raise a support ticket with Adobe and supply that data.It is theoretically possible for your producer to have corrupted the files but very unlikely. However they may have passed on the problem caused by the workflow issue I mentioned above.
Good luck and keep us posted.
-
Thanks for the observations Mark.
The entire file structure was transferred in both incidences of the problem, so it is a puzzle.
We seldom shoot single clips of 2 hrs in length, which both of these were, though we had a couple others that were nearly that long, with no issues. Hopefully will not run into this again (2 hr clips). The boredom factor rises exponentially for anything over an hour.
Thx…Jim
-
Jim,
ok, the problem I mentioned would be repeated for all clips so definitely not that one.I did think of another one though. A two hour clip would be huge. One weakness of Premiere Pro is that is does not do a good job on cache management. Often the cache will be left on the C drive for a default install so even if you have sized your data disks adequately you may be out of space on the cache.
So go to Edit > Preferences > Media and then push the “clean” button.
If you work with small projects you can get away without doing that for quite a while but it always gets you one day.
mark
-
Hi Mark,
Very familiar with PP cache issues and that could have been the case on the producer’s laptop, but not on my MacBook Pro nor my IMAC, so again, it’s a big unknown. I’m editing all day today so I’m going to roll a couple of 2 ½ hr clips with the FS7 just to see what happens. I’m pretty sure I’ve never shot a 2 or 2 ½ hr clip before…as in never ever and I’ve been shooting for 50 years. I also hope never to do it again:). I’ll let you know what happens and thanks again for taking an interest in my problem.
Thx…Jim
Reply to this Discussion! Login or Sign Up