- Apr 5, 2016
- Reaction score
- United Kingdom
- Dash Cam
- A129 Pro Duo 4K Viofo 119 Pro Viofo 119 V3 NB 522GW & 612GW
Because not a single video posted from a 129 Duo is free of duplicates. So chances are that video source is from a time when this issue hadn't occured. But if @TonyM wants to locate other samples, it'd help conclusively prove this theory.So when did a sample size of 1 become statistically valid? I clearly remember being taught otherwise in every class I ever took on statistics.
1. Do you have the A129 Duo (and not the 4K)?
HonestReview-Bill from Viofo was contacted about the double frame issue and said techs were going to work on a solution. Seems that promise hasn't come to fruition. While I realize the new 4K A129 is Viofo's latest and greatest product, the A129 4K is pre-order only. Meaning those with the A129 Duo still have Viofo's latest technology. And I believe we're owed a resolution to the problem.
I can't be the only one that feels this way?
Bill Zhou asked me for a clip and explanation of the dupe frame problem. I provided him with a very detailed explanation of how to replicate the problem, along with two clips for comparison. V1.11 that doesn't suffer the issue and a clip from a later firmware that has dupe frames.HonestReview-
I agree with you that Viofo is not giving A129 Duo users the courtesy of "timely customer service". - - Viovo/Bill Zhou said they would correct the sensitivity problem with the g-sensor in parking mode a month ago... - just another broken promise! - - Meanwhile the regular Viofo Fanboys come up with all kinds of excuses as to why Viofo cannot deliver on their promises.
I disagree. While the 4K A129 doesn't suffer from this issue, according to Beta testers, it might be that all prior generation cameras are affected. And while these cameras will be phased out as newer models released, it'd be good idea to address the issue. As there's always potential that the same dupe frame bug is introduced into a later firmware of the 4K A129 if the root cause isn't located and identified.If one frame duplicate of 90 frames in the rear camera is really important for someone, we recommend using V1.1 firmware.
Such issue normally related vendor SDK, not so fast to solve. Even I don't think Novatek have much interesting to check this. But they have solved some duplicated frame issue on other models before if they confirmed the issue.
Nope- different processor and a different SDK which means a different set of possible 'bugs', each of vwhich will need to be handled differently to make things right.As there's always potential that the same dupe frame bug is introduced into a later firmware of the 4K A129 if the root cause isn't located and identified.
I'm not harping on Viofo. Matter of fact, I gave him specific details on how to replicate the problem vs. 1.11 Firmware. So that this information can be passed along. It isn't Bill Zhou's fault. He is relegated to handing this information over to those responsible for releasing an SDK with a fix.Nope- different processor and a different SDK which means a different set of possible 'bugs', each of vwhich will need to be handled differently to make things right.
As Nigel said, Viofo can't do any more till they update the SDK so how about harping to them on their site instead and see whether that does you any good either. Nobody like waiting but when there is nothing else you can do that's what you do. And you've been given a stop-gap fix to address this issue until that new SDK comes out which is better service than 90%+ of the cam manufacturers would do for you.
Because I've tested itWhile the 4k A129 uses different hardware and a different SDK, we don't know what caused the issue on the A129 Duo, so how can you confidently say it won't reappear?
Correct and that's exactly what I said. The 4K doesn't have the problem but it could reappear in an update since the cause of the duplicate frames is yet unkonwn.Because I've tested it
Although it could of course re-appear at any firmware or SDK update, so it is good to get the issue understood and the old SDK fixed.
Correct. But again, the V1.11 of the A129 Duo didn't have the bug. Later firmware versions do. The 4K A129 doesnt have the bug. But later firmware versions might reintroduce the problem if the root cause is left unidentified.The new 4K processor in the A129 Pro is an evolution of the previous ones, and the SDK is also an evolution, so bugs in the older ones can certainly be passed into newer ones, but from testing I know that this particular bug hasn't currently been passed on, unless it is currently hiding.
@viofo @BillZhou-We are one of the manufacturers that want to update to the latest SDK. We also plan to upgrade SDK for A129 PRO in the near future.
But the new SDK may delivery some unknown bugs like this we talked about.
Even some time Novatek change some rules, like they didn't allow MOD firmware to change the bitrate to very high, give most of the chipset resource for IQ.
So some MOD firmware develop will complain this why they can improve the bitrate.
We have established that this requires an SDK update, and that Novatek are in control of when the SDK updates arrive, not Viofo, and we know from experience that these arrive when every fix/addition/improvement within the update is ready, not to meet a specific timescale. After the SDK arrives, it will then take some time for Viofo to get it working correctly with each camera.Can you tell everyone on this forum once and for all WHEN Viofo plans on fixing the g-sensor sensitivity problem so that it can be used in Parking Mode?