That doesn’t make sense though. Time Lapses don’t use the cloud. They are on the SD card and do a peer-to-peer connection to the phone for the download, etc. There would be no benefit to do that.
One would think the download would be much faster using p2p.
For real. There must be some kind of bottleneck. Maybe in the SD card controller or something. The card may support fast read/write speeds, but maybe the controller doesn’t. Or, it could be that the timelapse is recorded in full video and then when you “download it” is when it finally renders it into a Timelapse, and cherrypicks the frames out and reconverts it into a new normal video file. I have noticed that timelapses appear to be setup that way and some cameras have really limited processor and RAM, so that’s part of why it probably takes so long. and then you consider it is using the Phone as a WiFi storage to move the newly rendered video to…I suspect it’s less about “downloading” as it is about “converting remotely” that makes it so slow.
2 Likes
I don’t think this is the case. What I see when I pull a microSD card is a time_lapse subdirectory off the root and then time_Task_########## subdirectories within that. Inside one of those are three files: .start, .end, and record.h264. I can play the record.h264 directly off the card in VLC, and that plays like a normal time lapse (not like continuous video), so the scheduled frames are already present in that file. I think there is some kind of conversion (to .mp4) at the time of download, though, because that’s what ends up on my phone, though I don’t know if the camera or the app is responsible for the conversion, so I don’t know where the bottleneck is.
Anyway, I just found this topic and voted for it, because having to leave the app open on the time lapse download screen is annoying and seems like it shouldn’t be necessary.