AndrewFromIdaho
New Member
- Joined
- May 7, 2015
- Messages
- 7
- Reaction score
- 1
- Country
- United States
I'm confused about how looping should work, how I imagine looping should work, and what's going on with my Mini 0806.
I got my Mini 0806 hardwired a couple months ago. I hadn't actually downloaded anything until yesterday, when my wife mentioned she'd been nearly run off the road by another driver, who then proceeded to do a bunch of burnouts at an intersection.
Now, for this whole time, I've had my Mini set on 3-minute loop mode, with 1 32GB card in slot 1, and 1 64GB card in slot 2. And in my mind, the way this should work is:
Is my camera functioning "correctly" in a way that I don't understand, or is it not functioning correctly?
What I'd like is for my camera to record everything while I'm driving, then go back and re-record over the oldest footage once it runs out of space. Is this possible?
I'm not sure what firmware I was running, but when I discovered the issue I updated to the May 12, 2015 update.
I got my Mini 0806 hardwired a couple months ago. I hadn't actually downloaded anything until yesterday, when my wife mentioned she'd been nearly run off the road by another driver, who then proceeded to do a bunch of burnouts at an intersection.
Now, for this whole time, I've had my Mini set on 3-minute loop mode, with 1 32GB card in slot 1, and 1 64GB card in slot 2. And in my mind, the way this should work is:
- The camera records video in 3-minute increments until the card is full
- When it's done, the camera goes back and records-over the oldest 3-minute segment stored on the memory card, moving forward and recording over newer and newer 3-minute segments continuously.
Is my camera functioning "correctly" in a way that I don't understand, or is it not functioning correctly?
What I'd like is for my camera to record everything while I'm driving, then go back and re-record over the oldest footage once it runs out of space. Is this possible?
I'm not sure what firmware I was running, but when I discovered the issue I updated to the May 12, 2015 update.