This is why I still haven't bought the Mavic Pro 4, even though DJI in Australia offered me a discount, we need answers on an All-I workflow from somebody, but as DJI effectively caused the problem it's up to them to lead the solution.
I have read mac users rolling back the OS to an older version is the solution. Not a great solution, but at least it works.DJI really blew it with All-I simply (I assume) to avoid paying the ProRes license. We'll see if they fix this with a firmware update but as it stands there are very few people with Macs that would be willing to take the time to convert the All-I files into something workable.
yeah, all gets a bit messy Dave, it would be fixed tomorrow if we got the issue onto both DJI and Apple's radar.I have read mac users rolling back the OS to an older version is the solution. Not a great solution, but at least it works.
"Get a PC." —Bill GatesI have read mac users rolling back the OS to an older version is the solution. Not a great solution, but at least it works.
I have over 100tb and that's after a huge consolidation of data. It's impossible to run a stock footage library on the cloud so I have two physical copies of every drive in the edit suite and another physical copy in a separate building in case of fire.I completely understand your frustration at the All-I situation. I can't imagine an All-I or even a ProRes workflow and the ungodly amount of storage it would take. I have over 20TB of storage just for my home video and I am trying to figure out how to add more - and that's just for my video.
Please don't mention fire. I have no offsite backup.I have over 100tb and that's after a huge consolidation of data. It's impossible to run a stock footage library on the cloud so I have two physical copies of every drive in the edit suite and another physical copy in a separate building in case of fire.
Ok, I meant a jello avalanchePlease don't mention fire. I have no offsite backup.
So that's the reading you get with your M4Pro connected to your computer and pointing BM Speed Test at it?Hi, I use FCP for editing and IF I really want to use AI-Stuff, I simply use Proxy-Files for editing. I really don‘t see a difference.
And to be honest, there is not really a difference for me ( as a hobby ) of using AI or the H265 File. Because of the better quality in F-Stops it‘s better to use DLog-M, as you may know.
I started the Blackmagic-Test with the Creator M4P and have much better results than the guy in the video as you can see. It‘s not super fast but really fast enough.
System is a Mac Studio M1.
View attachment 183706
Greetings,
Oliver
Yes, exactly.So that's the reading you get with your M4Pro connected to your computer and pointing BM Speed Test at it?
To be clear - Thats your reading with your M4P directly connected to your Mac ?? Or is it just the NVME ?View attachment 183707I copy all the files to my drive, create panos or AEB in Lightroom and then move to FCP. I work from my NVME.
When I use the 5GB stress test I get 500 Read and 270 Write. When I use the 1GB test I get 500 Read and 480 Write. That tells me that SSD in it has a small cache or for whatever reason it doesn't enough speed to continue writing. To me that's an indication of a mediocre ssd and actually a fairly disappointing speed. I tried to do a test on the SD Card but Black Magic just froze and became unresponsive. This is on an M4 Studio Max.Yes, exactly.
Let me check, if there‘s a difference between the original cable and a normal one….
Oh yes it is, with a Apple-USB-C cable , which I got with my iPhone or so, it is beginning at 300 and going down to 77MB/s Write and around 40 MB/s read.
Changing cable again…
Yes, again about 344MB/s write and read 568 MB/s. So cable matters.
Greeting,
Oliver
We use essential cookies to make this site work, and optional cookies to enhance your experience.