Richard Bucker

Insta360 First Review

Posted at — Nov 21, 2021

I’ve been practicing with my Insta360 trying to get efficient and ready for my first game. I hate giving away the ending… but it was a fail.

The equipment: I have the insta360, the GPS remote, a 15' tripod, and 128GB memory card.

The tripod is made of light alluminium but is quite rigid. Even so there was a stiff breeze and the camera swayed a little.

The bluetooth remote worked quite well in that it had better than advertised range. The challenge here is that the remote has two buttons and a small display. The display is supposed to give you the status of the remote’s batter and the camera’s batter but it really did not help. The remote is suppose to let you trigger the camera mode from still picture, standard video, and timelapse video but it really sucks at that. And then the trigger.

In my experience I recorded a 1hr soccer game in timelapse. That was not what I intended.

And while my 128GB card was barely used in the timelapse storage….

a short 15sec burst created 2x 22MB files.

a 15min timelapse video produced a 60sec video in 2x files of 6xxMB.

Two files you ask? That’s because there are two cameras. The software is useful enough to stitch the videos together.

While I do not have 15min of standard video I’m calculating 12-16GB per 15min. short standard video (22MB/15s * 4 * 10m = ~880MB * 2 = 1.6GB) however my timelapse video was 600MB for 15min. The desktop software would not de-timelapse the video. However, if the timelapse video is real at 1.2GB per minute then 10min is 12GB.

If you record at 5.7K@30fps, the video’s size is around 800 mb when the recording it up to 1 min. In other words, the recording will be around 1:30 per GB of storage. –Insta360

The numbers do not match up so it will require some testing.

There are two ways to transfer the video files to my desktop. [a] plug the camera into the USB-C of the laptop or [b] extract the card and pug it in with a card reader. (b) was faster and by a lot. Operating the software connected to the software is a terrible idea. And it’s so very slow!!

So I went back over the remote documentation. It says it does things but not really. It’s not bad design just bad implementation and the cause of my issues. I would click the mode button and the remote would not change mode until you pressed the enter button. Reading the manual more closely and experimenting I did learn something…

Press the mode button twice then press the enter putton. The display changes. Repeat until you get into the mode you want. The “picture” mode is obvious. The timelapse vs standard are less obvious.

Lastly, I purchased 2x 256GB memory cards.