![]() They can also make an undocumented "running change" on the manufacturing line to different chips or different cache or different controller, which can have a negative affect. However any manufacturer can have a bad production batch. In theory we should not have to do these things - the drive should just work. The drive must be rigorously tested over a longer period. I always do a burn-in test on mine using a 3rd-party utilityĭoing a quick test with Blackmagic Speed Test is not very useful. I've seen a few cases where one would hang when formatting, so I changed those to HFS+ format and it seemed to work.ĭo not assume that any drive (inc'l a brand-name SSD) will work perfectly out of the box. I have about 30 Sandisk Extreme Portable 4TB SSDs (not the Pro version) and they have been mostly reliable. If those are Sandisk Extreme Pro 4TB SSDs, there have been recent reports of problems with those. Resetting SMC and NVRAM, as well as starting up in Safe Boot mode, may help. ![]() The error mentioned in the dialogue window you saw could also be due to a bad macOS installation (be sure to read the linked article). Yeah, the cable, SSD drive itself, or even the port to which it's connected could be having issues. Could this also be a faulty SSD card and thats why it keeps failing after reformats? Thanks for your help on this. EditReady is very fast in its processing and when used to transcode the source file into ProRes 422 does so like Compressor (but, again, maintains more of the original metadata in my experience). Other tools, like ShutterEncoder (which is a nice tool for many things), don't carry through some metadata. EditReady is nice because it maintains metadata and creates an actual timecode track in the file, if needed. Re-wrap in EditReady makes the MXF file into an MOV file with no transcoding. Is using "re-wrap" EditReady different than Compressor transcoding to ProRes 422? I have Catalyst Browse. To be clear, it's not an issue with FCP using FS7 footage.ġ. There are several potential failure points, so it's best take things one step at a time. The original camera file structure has sidecar and potentially other metadata files that may not have been copied properly to the ExFAT drive (separate issue from the ExFAT drive not playing well with FCP). You could also try processing the footage using Sony's free Catalyst Browse software. Processing the files in EditReady can help "clean" the camera files in some cases. You could use the "re-wrap" function or you could create ProRes 422 (or proxies) in EditReady, and then import either into FCP directly. And then if there are still issues? Try and edit project around Fs7 camera?īesides the ExFAT format issue, you could try processing the FS7 through EditReady (a worthwhile tool to have available). ![]() So it sounds like I need to go get backup footage and put it back on an APFS drive in original format and try again.
0 Comments
Leave a Reply. |