That is a lot of data, have you started to edit it yet?
Nope. Just test footage at this point. Getting used to how the bird flies and handles. Only got a short flight at lunch. By quitting time, it was pouring down raining. So only one flight. Gotta get down to a camera store today at lunch and grab a ND8 or ND16. Had the SS up to 1/8000 with ISO 100 and the aperture tight at 16 which gave an average of -0.5ev. I like to shoot -1ev on the phantom due to the latitude spread on the sensor. Wanted to start there on the I1 and see what it looked like. Then will adjust +/- to see what this sensor best performs at. But with a mostly sunny sky at noon, those settings pretty much maxed in every point of the triangle Clearly a ND is going to be standard takeoff equipment on day shoots.
Shooting with raw is expensive. When I'm on set I'm trying to minimise the recording time as much as possible, that will make it easier to work with the footage later. Of course depending on what is shooting there could be different approaches. For film most of the shots we are shooting are around 10 sec long but the director says to all cameras to start recording about 30 seconds or minute before the action starts. I'm not listening to him and start the Rec after I see that the action will start shortly in any second. This way we can stay whole day on set with only 1 ssd drive (no junk footage). Later the editor is very happy because only 20% of the shot length is pure trash.
If you are going to shoot Timelapse then it makes sense to leave the rec for ever
I'm also on Win 10 and didn't had problems with the reader, don't have an idea of what it could be. Is there error message or some interaction from the comp when trying to connect the reader?
Clearly my old habit of rolling after takeoff and terminating the record before landing habit isn't gonna work with this bird. On the P3P, the MP4s are not that huge. So its not an issue to just roll it and slice it later.
As for the reader, no message, just it plain doesn't work. It gets out of sync I think. Like when I remove the drive from the reader, the software will pop up listing it. But I KNOW its not there because its in my hand. I plug it back in and now its not listed in the software anymore. Or more often than not, when I plug it in, I can see it in the windows drive list but the software has nothing in the dropdown selector at the top so no way to extract data. On my Win7 box here (using the DJI USB cable plugged into a USB extension plugged into a USB2 port worst case scenario) I could unplug it quickly, slowly, repeatedly, unplug the USB, plug it in with drive and without drive. No issue, always knew whether the drive is there or it isn't. But on Win10, its a freaking crap-shoot whether plugging it in each time will be in the proper sync. 80% or so of the time, its not in sync or doesn't recognize it. I tried it going through a hub, going straight into a front panel USB, on a USB extension, and using the USB3 cable from my Galaxy phone. Nothing made any difference. The one thing I did notice is that when I was in task manager killing the software, I noticed its 32bit. The machine is a 64bit box. Then again, so is my Win7 here, its 64 too. So I don't know.
I am sorry but this whole thing is f'ng moronic. There is NO need for this stupidity. I can't seen any reason why a FAT can't be written onto the drive to point to the dng files. Then a simple drag/drop would work on any device whether windows, apple, plugged into a NAS or SAS or one of those drive backpacks on the road. But I am sure the latter is why DJI consciously chose this idiotic path of hiding the data on the drive. So we have to buy more SSD drives from them with hybrid connectors and custom firmware rather than be able to dump the data easily and quickly on a portable unit on-site out in the field. And so we are stuck with idiotic software that can't even format the drive nor delete files from it after extracting them We have to use valuable battery power and time in the bird (gimbal) to format the SSD. AFAIK, we can't even delete ONE video from the SSD, Its either an all or nothing wipe.