Viofo A329T (unboxing & first impressions) (Sony Starvis 2 IMX678, Wi-Fi 6/GPS, HDR, Novatek NT98530, 4K front + 2.5K telephoto + 2.5K rear, HDR all)

From where do you know that a rain or thunderstorm will create parking files in low energy parking mode? And even they will trigger the G-Sensor, I consider is not a tragedy to have some parking videos on the card in a day when it is raining.
.
.


.
.
For me the best news regarding the parking mode is because of a much more sensitive G-Sensor setting in parking mode. If I am knocking with my finger on the front side window, the dashcam will start recording in parking mode because it will detect such shock. Until now I was not satisfied about the Viofo G-Sensor sensitivity in Parking Mode so I preferred ...

From your post. If you are knocking with fingers on the front side window, then it would seem a heavy rain storm would be detected by the new sensor sensitivity. Now, taking into account that English is not your native tongue, you may be speaking of somewhere else when stating the front side window. Or, I could just be misunderstanding your explanation or needs. I am good either way, I am reading with interest what you are reporting.
 
Looks like a lot of info is being leaked on here. The amount of detail from people who are supposed to be trusted with information that are leaking info is quite interesting..

There are features that Bill and Leo showed me that nobody knows on here. Will be a great surprise for many. If that somehow gets leaked I will be very surprised @viofo specifically told me noone else knows.

Not going to comment until I have one in my hands in a few weeks.

Those few weeks, would that be when you receive one for testing or when the A329S is released to the market for purchase?
 
Those few weeks, would that be when you receive one for testing or when the A329S is released to the market for purchase?
Testing
Not release for a few months yet
 
English is not your native tongue
You are right, English is not my native language, but seems that also it is not yours native... tongue, too. 😎 Lets hope Trump is not reading this forum. 😵
I know I can not make people always understand what I want to say, but I am doing my best without using Google translate.

Regarding the G-Sensor, that test was made with a special extreme sensitivity of the G-Sensor, but, who knows, this setting can be removed in future firmware the same way it was removed few years ago from the A129 Pro beta firmware. In all Viofo firmwares you have 3 levels of sensitivity for the G-Sensor. The Viofo strategy regarding the G-Sensor is to detect only accidents and not minor scratches. In my finger knocking test the firmware has a new level, the fourth.

If you are afraid of storms and heavy rains you can set the G-Sensor with a lower sensitivity. But again, don't be afraid if during a rare and heavy storm your card will contain many parking mode videos.
I will make a test with a water hose for watering the garden to see if it will trigger the parking mode. Instead of heavy wind I will try to shake the car
 
As space used and because of the SNV feature the time-lapse 1FPS is a great feature. If an F35 will hit your car it is possible to miss something at 1FPS but in normal parking and traffic conditions you will miss nothing. You are just assuming that you can miss something at 1FPS and not speaking from reality.

In my opinion is ideal only because it contains audio. If somebody consider that the audio is not important can chose time-lapse.

With all functions of Viofo parking mode you should be afraid only if somebody will come exactly from the side of the car, hit or scratch the car and leaving exactly from the side of the car. In that situation even you have front and rear cameras and the best parking mode, nothing of them will help. But it can help the interior camera of A329S which is wide angle and it can capture some details. Not perfect, but will be something.

@safedrivesolutions created a great video showing the difference in parking mode. Under ideal lighting, you may capture the event needed, but at 1FPS time lapse, you're losing 29 frames a second over low bitrate (29.97 FPS). So there are far fewer frames to analyze if you don't capture that moment perfectly.

I'm not assuming here. That's just a fact.

With low bitrate, if someone walks to the side of your car, and you've got an interior camera, you may capture that action. On time lapse, you may not.

@Mtz what is SNV?

 
I much prefer low bitrate when parked at the supermarket, however I don't need low bitrate when parked at home, so I am happy if it switches into impact detection, which uses so little power that I don't need a dashcam battery, it can simply run of the car battery all night, while parked in a pitch black garage, and it doesn't matter how many channels it has!

Low bitrate with 3 channels, even with a dedicated dashcam parking battery, will not run all weekend while the car is not in use. Using most of the dashcam battery for low bitrate, and then switching to impact detection before the battery is empty will allow it to give excellent protection for part of the weekend and good protection all weekend, and all week too if needed.

If parked at a store or in public, I agree that low bitrate is best.

No buffering on the impact detection, it is sleeping, with all the image sensors turned off, that is how it uses so little power.

Until now, most dashcams have taken many seconds to wake up and start recording from sleep, which has not been much use, but with sub 1 second impact to recording, it is a good option for some people, as safedrivesolutions suggests, but you don't have to use it if it is not what you want. The A329S should start recording fast enough that safedrivesolutions with his basketball can't escape from the frame before he has been recorded! Not as good as low bitrate with a big enough battery, but it will work for much longer between charges, and doesn't actually require a dashcam battery.

If the wake up from sleep is almost instantaneous and it's reliable, then impact detection could be useful for long term parking. However, there are downsides, too.

1. Someone keys your car. There obviously won't be an impact to register or wake up camera
2. Car is vandalized

However, I do agree that most other circumstances would be covered if the impact detection is sensitive enough
 
@safedrivesolutions created a great video showing the difference in parking mode. Under ideal lighting, you may capture the event needed, but at 1FPS time lapse, you're losing 29 frames a second over low bitrate (29.97 FPS). So there are far fewer frames to analyze if you don't capture that moment perfectly.

I'm not assuming here. That's just a fact.

With low bitrate, if someone walks to the side of your car, and you've got an interior camera, you may capture that action. On time lapse, you may not.

@Mtz what is SNV?

SNV is Viofo's super night vision.
 
  • Like
Reactions: Mtz
You are right, English is not my native language, but seems that also it is not yours native... tongue, too. 😎 Lets hope Trump is not reading this forum. 😵
Trump's family is Scottish, not English, being from the Hebridean Islands, their native language is Gaelic, not English. Trump's mother's native language was Gaelic, your native language is much closer to English!

I'm guessing @lufa6977 's native language is Usanian?

If an F35 will hit your car it is possible to miss something at 1FPS but in normal parking and traffic conditions you will miss nothing.
The F35 that hit my car with enough noise to trigger any impact sensor a few weeks ago would not have been captured by 60fps, unless I had a camera mounted on top of the roof, facing upwards, then I could have had video of the afterburners disappearing vertically up through the clouds! F35s are hard to see anyway, better to look for their shadows, stealth technology doesn't seem to work for shadows:

1743542412119.webp

I hope those two people had ear protection!
 
  • Like
Reactions: Mtz
There will definitely be users who do not like the new parking mode or think it will not be functional. No need to worry. Users who are suitable for their own use will use this mode when the necessary conditions are met and will be satisfied. Other users can continue with the current parking modes.

Just like I suggested adding the voice notification sound to the menu in the past. Some, namely the user who works loudly or uses it on noisy roads, will choose the high notification sound, while others, namely the user who is quiet or uses it in an electric vehicle, will choose the low notification sound.

This is the summary of the situation.
 
@safedrivesolutions created a great video showing the difference in parking mode. Under ideal lighting, you may capture the event needed, but at 1FPS time lapse, you're losing 29 frames a second over low bitrate (29.97 FPS). So there are far fewer frames to analyze if you don't capture that moment perfectly.

I'm not assuming here. That's just a fact.
As you can see in the above post, SafeDriveSolutions made a very good video about the 1FPS time-lapse. I don't think Ben can go out from the video frame in less than one second. If you have a dashcam with 1FPS time-lapse parking mode just park it on some supermaket parking or on some road and then study the videos to see if you can miss at least one car or one person.
More, than that, compared to other dashcam manufacturers, Viofo is offering more FPS options for the time-lapse parking mode, so if you will be afraid that Speedy Gonzales will be not captured after scratching your car you can chose the highest FPS from time-laps mode and check again. The biggest advantage of 1FPS is not more space on card for parking mode, but the SNV. Normally I would chose 3FPS or 5FPS, but because of he SNV, the 1FPS is the only attractive option for me if I want to chose the time-lapse mode.
And even more than more than that, Viofo also have a time-lapse mode for the normal driving mode. Compared to the parking mode, the speed on the normal driving mode is double, because it is summing the speed of dashcam car and the speed of the opposite car or pedestrian. In your opinion the 1FPS time-lapse option in driving mode is a disaster because nothing is captured.

I know also the people who are desperate to have 60FPS or even more FPS for driving mode just because they think they will capture more details, but in reality is no experiment proving that 60FPS is a clearly winner over 30FPS. In some video Vortex Radar made a short comparison of 60FPS vs 30FPS and in some moment the 60FPS won. But in others, dont. More than that, 30FPS is always better in low light than 60FPS or equal, but never 60FPS is better than 30FPS in low light. People are paying more money for 60FPS just because they are fooled by the marketing numbers and they like to be fooled because they don't know the facts, they are just assuming.
Never, never, a 60FPS night video will be better than a 30FPS HDR video from the same dashcam.
There will definitely be users who do not like the new parking mode or think it will not be functional. No need to worry. Users who are suitable for their own use will use this mode when the necessary conditions are met and will be satisfied. Other users can continue with the current parking modes.
The continuous parking mode is killing the car battery. Going with the car battery at 12V or 11.8V day by day will make your car battery life even shorter. More than that, actual products are designed to last at least the warranty duration which in Europe is 2 years. Years ago the car batteries were lasting longer.
I am using standard parking mode even it is time-lapse or low-bitrate because I like the car to be monitored all the time, but the Duration is set at 1 hour. Many places where I go I park the car about 1 hour so it is enough for me, but if life will change, I can increase this 1 hour duration. At home I have CCTV cameras and in my opinion these are the best for protecting your car when it is parked. Except when you want to see car license numbers, for this purpose, the dashcam is better but only during day. In low light is not useful even with HDR enabled in parking mode. Of course, at home I can have a CCTV camera with optical zoom so I can point it just around my car and with its IR LEDs to hope I can capture also the license plates. But I need to park the car exactly at the same spot.

Of course you can tell me that you can put the voltage cut at 12.4V. But how many hours will record your dashcam with this voltage cut? If you will want one night recording I guess it will not cover all night even the car battery is new. For example when the car battery is new, the Low bitrate parking mode maybe can last 6 hours until it reach 12.4V. But after 6 months it will last only 4 hours and so on.

So, what will you do at that moment? Lower the voltage cut? Accept less and less hours for parking mode?
But after 2 years when you will observe that even you put the voltage cut at 11.8V the parking mode can not last more than 1 hour? Your car engine is starting OK, battery is enough for this and if not using dashcam in parking mode you can still use that tired battery for more than 6 months.
So, you will look for a solution.

At that moment you can have some solutions:
1. buy a dedicated battery pack, maybe about $400. Even with that, you need to drive at least 45 minutes daily. For shorter driving periods you need another solution and this can be the low energy parking mode
2. accept that the car battery must be replaced each 2 years and replace it. A normal car battery is not expensive these days but other types are expensive. But you will always have your parked car protected by the dashcam.
3. when you start to feel that the car battery is not so good as before and you will want to save some money, you will chose the low energy parking mode even you like more the low bitrate parking mode.

As a summary, a new option for parking mode as was described by me can save some money. And it can be even better by an improved firmware.
 
If you have a dashcam with 1FPS time-lapse parking mode just park it on some supermaket parking or on some road and then study the videos to see if you can miss at least one car or one person.
You will record all the cars and all the shopping trolleys, but you will probably miss the license plates. You will also miss the tap from your neighbour reversing out of her parking bay, and the movement of your car’s suspension as a result of the tap, which would prove that it happened even if it can’t be clearly seen. And of course you will miss the audio of the tap and your car getting dented and scratched, more proof.

Low bitrate is much better for supermarkets.
 
Exciting news! Do you have the parameters for these models?
 
As you can see in the above post, SafeDriveSolutions made a very good video about the 1FPS time-lapse. I don't think Ben can go out from the video frame in less than one second. If you have a dashcam with 1FPS time-lapse parking mode just park it on some supermaket parking or on some road and then study the videos to see if you can miss at least one car or one person.
More, than that, compared to other dashcam manufacturers, Viofo is offering more FPS options for the time-lapse parking mode, so if you will be afraid that Speedy Gonzales will be not captured after scratching your car you can chose the highest FPS from time-laps mode and check again. The biggest advantage of 1FPS is not more space on card for parking mode, but the SNV. Normally I would chose 3FPS or 5FPS, but because of he SNV, the 1FPS is the only attractive option for me if I want to chose the time-lapse mode.
And even more than more than that, Viofo also have a time-lapse mode for the normal driving mode. Compared to the parking mode, the speed on the normal driving mode is double, because it is summing the speed of dashcam car and the speed of the opposite car or pedestrian. In your opinion the 1FPS time-lapse option in driving mode is a disaster because nothing is captured.


@Nigel beat me to the punch.

One point to add, and you didn't address, is that 1 FPS is still 29 less frames per second than low bitrate Viofo. Or 14 FPS less than Vantrue low bitrate.

One problem is that if lighting isn't good, you have less frames to analyze in order to get a clear image of @safedrivesolutions (or whomever).

I had similar situation with Viofo camera, where I had to frame by frame very poor quality lighting, to get a good image of person. Even then image wasn't super clear but "passable".

The rest of the issues @Nigel covered.

I know also the people who are desperate to have 60FPS or even more FPS for driving mode just because they think they will capture more details, but in reality is no experiment proving that 60FPS is a clearly winner over 30FPS. In some video Vortex Radar made a short comparison of 60FPS vs 30FPS and in some moment the 60FPS won. But in others, dont. More than that, 30FPS is always better in low light than 60FPS or equal, but never 60FPS is better than 30FPS in low light. People are paying more money for 60FPS just because they are fooled by the marketing numbers and they like to be fooled because they don't know the facts, they are just assuming.
Never, never, a 60FPS night video will be better than a 30FPS HDR video from the same dashcam.

I agree that 30 FPS and 60 FPS have their benefits. Just like 1080P (larger pixel size) will do better in low light than 2160 or 4K. Smaller the pixels, the less light.

I run two cameras for a reason. One 60 FPS and One 30 FPS.
 
One point to add, and you didn't address, is that 1 FPS is still 29 less frames per second than low bitrate Viofo. Or 14 FPS less than Vantrue low bitrate.
And how much bitrate does silent 1 FPS save over 30 FPS low bitrate with audio?
Google's AI says no saving, which is what I was guessing, but I don't see any figures published... Anyone got some figures?

So why use the 1FPS?
1. It uses 29% less power, but only if you use SNV mode.
2. You can use SNV mode.
 
It's a choice between SNV for bright images in near darkness, compared to darker pictures that are clearer.

It's the same quandary currently haunting CCTV cameras.

Higher pixel cameras but dark night vision unless floodlit Vs low light sensors that need longer exposure rates (lower FPS to allow more light per frame).

It's a new feature and will be improved over time - either by firmware updates, or on newer models as the technology improves.
 
It's a choice between SNV for bright images in near darkness, compared to darker pictures that are clearer.

It's the same quandary currently haunting CCTV cameras.

Higher pixel cameras but dark night vision unless floodlit Vs low light sensors that need longer exposure rates (lower FPS to allow more light per frame).

It's a new feature and will be improved over time - either by firmware updates, or on newer models as the technology improves.
100% this. Would rather have brighter images to get an idea of what's going on in the scene around my vehicle etc
 
And how much bitrate does silent 1 FPS save over 30 FPS low bitrate with audio?
Google's AI says no saving
This is garbage info.
 
Of course the biggest advantage of 1FPS is the SNV option and I dont know if you can find a better dashcam regarding quality of the video in parking mode. Again, regarding the video of Ben, do you think that he can run so fast from the video image and you can not capture at least one frame where you can see is face?
And how much bitrate does silent 1 FPS save over 30 FPS low bitrate with audio?
Google AI is wrong, it needs more tariffs.
1 hour of 1 FPS 4K recorded at 65mbps is 960 MB. The video is just 2 minutes long, easy to search. And if SNV enabled, a bright video at night recorded at maximum bitrate.
1 hour of low bitrate should be something like 1980 MB for one hour of video in parking mode.
This means the size used by the low bitrate is double.
 
Back
Top