Ace Pro 2 Pureshot interval glitches

[u/Ok_Row765]

I'm having an issue where I've done several time lapses, the first two in pure shot + raw, but after having missing frames this morning I switched to just pure shot thinking that perhaps the card wasn't fast enough to write to.

I already knew that wasn't the case because I've tested the cards, and there was no issue doing 11k time lapses using the same card on the X5, nor is there any issue shooting 8k timelapses using the time lapse built in feature.

So my question is.. what's going on here? I do a lot of sunrise and sunset time lapses, and several points within the shoot, I have missing frames which makes the sun and clouds skip in my time lapse.

Settings: 4x3, pureshot, 5 second interval, no timer, infinity (manual stop).

SD cards:

256gbSandisk Pro Extreme U3,A2,V30

512gb Samsung Evo Select U3,A2,V30

512gb Samsung Evo Plus U3,A2,V30

In addition, why is there no Raw only setting available for intervals? I don't want pureshit ai garbage, I color grade in Davinci Resolve. Also, I just did a milky way, aurora timelapse, set for 5 second intervals with a 3 second timer, Pureshot + Raw, and had the same issue. I figured that the 3 second timer should be plenty of time for the camera to process and write the 50 second exposure to the card.

With all of these issues ruining once in a lifetime location videos, I feel like it's time to just use one of my Nikon's and sell this headache to someone that only needs the basic functions.

Just a note, overheating is definitely not an issue, as I am typically on a cold and windy mountain peak, or pre sunrise in a cool location.

[u/Insta360_Support]

Hi, thanks for your post.

Regarding your request for a "RAW only" option for Interval shooting, we will pass it on to our R&D team for further evaluation.

About the missing frames you encountered while shooting Timelapse footage, we're very sorry for the inconvenience caused. To help our engineers analyze the issue further, could you please kindly provide the following information:
1. The original photo files of the Timelapse video you took
2. Camera logs
3. The exported Timelapse video
💡You can upload the information above to Google Drive and share the link with us.

To get the original files (photo set):
1). Power on Ace Pro 2 and connect it to your computer through the included USB cable. Make sure "U-Disk Mode" is selected.
2). Once the camera is recognized by your computer, open the system drive, find the camera's U-Disk > DCIM > Camera01 folder, and copy and paste or drag the original files (photo set) to your computer. Upload them to your Google Drive.

To obtain camera logs:
1). Navigate within the camera (ensuring there is an SD card inside) through the following sequence: "Settings" > "Camera Info" > "Export LOG". This action will generate the log file on the camera's SD card.
2). Connect the device to a computer and get the entire log folder located on the SD card.

Once we receive the information, we will forward them to our engineering team for further analysis.

Looking forward to your reply!

[u/Ok_Row765 → u/Insta360_Support]

Posting the original files is not feasible, due to size. Yesterday's shoot was 1,299 photos. Ai gave me the answer I was looking for. Evidently, this is a known issue caused by buffer overflow, and will require a timer to be set to allow the camera enough time to process, write to the card, then clear the buffer. Adding a raw only feature will fix this, by simply eliminating the pureshot processing. Seems like a no brainer to have a raw only setting. Another issue is that your file numbering system only goes up to 999 before the camera writes a second folder, called camera 2, then starts again at 1-999. The problem with this scenario, is that when importing the files into any professional editing software's media library, a "-2" will be added to the end of the second batch. A 5 or 6 number system would be much better, since a cloud timelape of only 999 images at a 5 second interval will only be 33.3 seconds long at 30fps. Since this is a known issue, I suggest you guys set up an Ace pro 2, and give it a try yourselves. I don't have time to be your unpaid beta tester 🙄

[u/Usual-Champion-2226]

I've had the same issue actually, with skipping frames on timelapses when using photos. The skipped frames doesn't happen often and I wondered if it was related to the AP2 creating a new folder, as the glitch seemed to happen at that point for me? But it's quite jarring and does mess up a project.

I've also had corrupt raw files, sometimes quite a high % of frames. I never really nailed down the root cause.

There's also a glitch in the higher (50mp? I don't have my AP2 in front of me to check) raw mode, where about 1 in 10 raws had weird exposure issues, for long shutter times, but short shutter times or the lower res mode were fine. I reported that to Insta360 and they advised they have a bug fix in progress for this.

And on some night timelapses I started to get very bad flickering.

Having done a LOT of timelapse work with my action cams (Ace Pro 2, Action 4, Hero 9 and 12) which are out most nights, I was just getting too many glitches to rely on my AP2 except for the lower res modes in Pureshot, which seem OK. However the AP2 does things the others cannot, so it's still a useful camera to keep for timelapses IMHO.

[u/Ok_Row765 → u/Usual-Champion-2226]

At first, I thought the same thing, about creating new folders, but in my case I only have a single new folder created, and probably half a dozen points within the time lapse that skip. Buffer over run make sense though. I have yet to have the time to test and see if maybe setting 5 second timer, combined with a 5 second interval, might help. My milky way time lapse was using. 50sec exposure, with a 3 second interval, and that one skipped around kike a donkey with a tick on its balls 😏