I have tested many thousands of hours using loop recording with 64GB cards formatted to FAT32. ZERO problems with FW v2.18. I do not have a Samsung 64GB to test but have tested Kingston, Sandisk, PQI and PNY cards.had to reset my Mobius just now, is this normal?? had it only a few days, bench testing it and it locked up, satt here with just a green light on solid, computer wouldn't recognize it either. not sure if it was because the card was full or what is going on but I deleted a few files off of the card and set it going again.
I have a Samsung evo 64GB card in it, the file system for the card is set to FAT32, loop recording ON, anyone know whats going on?? have I missed something??
Tested 32GB card and that worked for over 24 hours non stop.I have tested many thousands of hours using loop recording with 64GB cards formatted to FAT32. ZERO problems with FW v2.18. I do not have a Samsung 64GB to test but have tested Kingston, Sandisk, PQI and PNY cards.
Are you sure your card is genuine? Format your card and then use c't Magazin's h2testw.exe program to test the entire card. This will take a good while.
I was testing FW2.18 for few days and today I tried to edit some files in AVS Video Editor which I successfully used until now to edit Mobius MOV files, as well as other formats. However, this time I got an unpleasant surprise:
View attachment 8773
At first I blamed Registrator Viewer which I updated recently (the files were fragments generated with RV), but then I tried with the original MOV files and got the same error message.
Just for testing I switched to AVI (non-standard format and cannot be edited without re-packaging or re-encoding), generated 2 clips and imported them into AVS. There were no errors, but AVS can't handle them correctly, there are problems with playing the imported clips and the produced file didn't have all transition/effects that I applied.
So... back to FW1.13 for me.
I have not heard of anybody else who has problems editing files created with FW v2.18. I do know that v2.18 uses the latest codes from the chip manufacturer which are different than the codes used in previous FW versions, so that could be the reason your AVS product doesn't like the updated format. Other editors apparently work fine.
Weird really when you think about it. For years SanDisk and SD were synonymous.Since I've now had 4 Sandisk cards fail I don't think this is coincidence and suspect Sandisk use low quality or badly designed controllers in their cards. No other cards have failed so far.
Tested 32GB card and that worked for over 24 hours non stop.
I woke up in the middle of the night last night and all of a sudden it came to me that 64GB cards come factory formatted with exFat, then I remembered reading on here that to format it to FAT32 else may have issues.
got up this morning, sure enough, the card was exFat, this may be the issues I am having. I have formatted it to FAT32 and will update in 24 hours if its still working good.
the card is genuine, got it from jokiins recommended supplier.
thanks.
Tested 32GB card and that worked for over 24 hours non stop.
I woke up in the middle of the night last night and all of a sudden it came to me that 64GB cards come factory formatted with exFat, then I remembered reading on here that to format it to FAT32 else may have issues.
got up this morning, sure enough, the card was exFat, this may be the issues I am having. I have formatted it to FAT32 and will update in 24 hours if its still working good.
the card is genuine, got it from jokiins recommended supplier.
thanks.
I didn't even know I can use a format other than .mov. The manual says nothing about it. Where do I change it? Besides, why should I change it? And I'm already using a second Class 4 card. Still the same. Plays back only the first video after formatting. The rest are corrupted. And yes, I'm of course checking it with multiple players and Gspot, not just VLC.which format are you using, MOV, MP4 or AVI?
have you tried any of the alternate formats?
tried another memory card?
The format has nothing to do with the card. It's Microsoft who imposed an upper limit of 32GB for FAT32. However, there's nothing stopping you format 64 and 128GB cards with FAT32. In fact, this is the ONLY format that will work correctly with 64GB cards.. With FW v2.18 you can set the file format you want to use. In-camera formatting will then use this format. If you use mSetup the program will show if the card is formatted with exFAT. The Tooltip will also tell you that only cards greater than 32GB will be affected by the File system (format) parameter.You cannot format 64gb into fat32 cuz doesnt support it, gotta be exfat
You should check your card with h2testw.exe. Your card could be fake. Format your card before running h2testw.I didn't even know I can use a format other than .mov. The manual says nothing about it. Where do I change it? Besides, why should I change it? And I'm already using a second Class 4 card. Still the same. Plays back only the first video after formatting. The rest are corrupted. And yes, I'm of course checking it with multiple players and Gspot, not just VLC.
Sounds like a fake SD card to meI didn't even know I can use a format other than .mov. The manual says nothing about it. Where do I change it? Besides, why should I change it? And I'm already using a second Class 4 card. Still the same. Plays back only the first video after formatting. The rest are corrupted. And yes, I'm of course checking it with multiple players and Gspot, not just VLC.
However, there's nothing stopping you format 64 and 128GB cards with FAT32.
I use bothActually it's Windows that stops most people, it won't format anything larger than 32GB FAT32, this is what catches most people out, anything larger needs to be formatted with a 3rd party app
as a dash cam, who has the motion detection setting turned on? if so is it on high?? if not why not??
My experience with my A lens is as Dashmellow said, a lot of false triggers on High and Medium. Low worked best for me in a daytime parking lot and would only start recording when something or someone got close to the car. The second thing I learned is the need for 30 second or higher timeout or sometimes things would be missed.as a dash cam, who has the motion detection setting turned on? if so is it on high?? if not why not??
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
H | Mobius C2 failure (for no apparent reason) | Mobius | 0 | |
E | Looking for original Mobius1 | Mobius | 3 | |
V | Mobius 1 vs maxi 4k ...FOV | Mobius | 0 | |
T | Mobius suddenly acting screwy - solid blue light on startup | Mobius | 9 | |
J | Mobius dash cam problem | Mobius | 55 |