iFootage Moco 4+

Each time I’ve gone to use it for a time lapse it’s failed me. I can do extremely short time lapses in order to test to make sure the basics work. But when I try to do a time lapse running for even over 20 minutes, the app crashes. Every time. There are two overall faults to the ifootage shark nano, and together they make the entire unit a failure for me. First off, the time lapse function only works with very few cameras, despite all the shuttle release cables they give you, when I contacted their development team about updates to future cameras, they said that they didn’t even have a roadmap for other cameras. I have a canon Eos r, and R6. So that means I can’t do any time lapse with a DSLR, and now the app doesn’t work at all. So it is literally impossible for me to do any kind of time lapse on this expensive unit that I bought specifically to get quality time lapse. Get your ship together iFootage.

Connecting to your devices is quick and consistent and since a few updates ago, I haven’t had any problems with target control mode not allowing for tilts.

THAT SAID, having used this app for over 2 years PLEASE could we get a set A and B timelapse mode. The timeline feature is powerful and allows for all sorts of micro-control using key frames for each of the 3 axis, BUT for most of the timelapses I do (and, I suspect most people) a “set start” and “set end” feature—like target control where you can just use the control sticks to dial end each side of the move—(with, of course keeping Timelapse buffer, shots number controls) would be ideal. Having to program each axis separately and using a graph editor just takes too much time! Especially with more than one track.

PLEASE, PLEASE, PLEASE, give us a A,B timelapse feature. It would allow for much quicker setups and make me want to use this device even more.

About the only reason I’d use their app for recording, is for the camera-controlled Timelapse function. It simply doesn’t work.

If you do a shirt test, it’ll work fine. But any real Timelapse of 30m to 2 hours fails. Not just sometimes, every time.

I see a year old review that says the same thing, and the app hasn’t been updated in 9 months. Apparently the developers don’t care that their app doesn’t work.