Vueroid S1-4K Improvement Wishlist

@meyelow_Vue said:
Without an overall understanding of image processing concepts and the technical limitations of video tuning,

@Chuck McCoy said:
Correct, I don’t understand how any of this works.
I have below average IQ.
Barely graduated high school.
Did not attend college / university.
No education, training, or experience with computers & electronics.
My low intelligence represents the mass majority of your customers.
This is why dash cam needs to be as simple as possible (idiot proof) with only one video setting.
Ha, gotcha! 🤣
 
Last edited:
@Karagandinez said:
Regarding video loss when the timer triggers:
Manufacturers need to explicitly mention this in the manual.
This ensures the user is aware of what to expect and can then decide—based on that information—whether or not to use the timer.

@Chuck McCoy said:
I wonder why no one else posted S1-4K HDR Timer 4 Second Recording Lapse, and it took a dumb guy like me to do it. 🤣
 
Last edited:
@Karagandinez said:
Regarding video loss when the timer triggers:
Manufacturers need to explicitly mention this in the manual.
This ensures the user is aware of what to expect and can then decide—based on that information—whether or not to use the timer.

@Chuck McCoy said:
I wonder why no one else tested HDR Timer 4 Second Recording Lapse, and it took a dumb guy like me to do it. 🤣

Actually...that lapse was already known to testers and manufacturers. It is an acceptable loss in imaging when the switch happens. As Karagandinez mentioned elsewhere, it would be best if manufacturers who employ this feature let users know about it.
 
It's been there ever since we started seeing timed HDR in Starvis 1 dashcams, perhaps 5 years ago
I meant S1-4K HDR Timer 4 Second Recording Lapse.
 
I wonder why no one else posted S1-4K HDR Timer 4 Second Recording Lapse, and it took a dumb guy like me to do it. 🤣
Not everyone likes recording a video for every little thing...
Information regarding the video pause caused by the timer has been available in my thread since October 2025.
At that time, the duration was 5 seconds.

 
Isnt Viofo taking 20 seconds changing over with no recording?
Each model has its own specific duration of lost time in video files when the HDR timer triggers.
For example, on the A229 Pro model, this pause amounts to 14 seconds per day. I haven't measured it on other models...
 
Feature Request: QR activated Garage Mode -

Why? If I park inside my garage no parking mode needed, but if I park outside in my driveway, parking mode would run as normal. The problem is that GPS lockout radius can't detect the 10-20ft different to know if I'm in the garage or in the driveway.

Possible solution
Idea #1: If a preconfigured QR code is detected on the inside of the garage, that can trigger the parking mode you want to be in (enabled/disabled/etc). This QR code would obviously need to be unique for each dash camera system. I could see a "training" menu on the app where you print out your qr code and it would scan it. That QR code would only work to specific GPS location and it would have a delay to disable the parking mode. The delay would prevent someone from flashing it in the camera and then immediately doing what they want to your car. Maybe a customizable 5min delay or something.

Idea #2: I know some security camera will take a snapshot of an environment to better help with detecting motion. Kind of like fingerprinting the surrounding and looking for the changes. Possible this is something we can do here, you park in the garage go into the app and the dash camera stores a image of your garage via the front and rear camera. So when the parking more is triggered in the future it checks for any similarities with the stored images after a set delay and then maybe once per hour. I think we still need for it to do a recurring check for situation like leaving your garage door open, so you still want the parking more to activate. The front and rear camera would kind of act like two factor authentication where the current environment for both camera needs to match the previously stored snap shots. And again this would only function as preconfigured GPS location. I would imagine this is more of a software and hardware resource intensive process compared to the QR code idea. That said this would be way ahead of the game compared to other products out there.
 
Feature Request: QR activated Garage Mode -

I think that is a very good idea.
Perhaps because you already have a technical background, you also mentioned in advance both the necessary aspects and the potentially burdensome parts.

Some high-end SoCs used in dashcams already include an NPU, which is not as big as the general-purpose SoCs. If resources are allocated properly, simple recognition processing is certainly possible.
However, since dashcams already use almost all of the SoC’s available resources to perform their primary recording functions, features like this would likely need to be discussed and designed from the very beginning of the product planning stage in order to be realistically implemented.

The custom QR training itself does not seem particularly difficult. Since it is pattern recognition and QR codes only contain a limited number of recognizable features, reading and memorizing them would probably not be very challenging.
However, while it may be possible to include a QR recognition algorithm inside the dashcam, automatically detecting and reading QR codes would require continuously scanning every frame to determine whether a QR code is present or not. Just thinking about it, that would likely require an enormous amount of processing resources.
Otherwise, the user would have to manually activate a QR recognition mode when arriving home to avoid scanning every frame(or maybe one of a few frames) and instruct the dashcam to scan the QR code. But in that case, it would effectively become no different from manually pressing a button to enable or disable parking mode, which would somewhat defeat the purpose.

As for recognizing and comparing the surrounding environment, I believe that would require significantly more system resources.
The system would need to recognize multiple environmental feature points, store them, and continuously compare those stored reference frames against newly captured real-time frames. It may not be impossible technically, but achieving high accuracy would probably make it a very resource-intensive approach and not necessarily the most practical one.
That was also the concern you mentioned yourself.

Still, the idea itself is excellent, so I will continue thinking more deeply about how it could potentially be implemented.
Honestly, ideas this valuable probably should have been sent to me privately instead. lol

Thank you very much. Have a great day~
 
Back
Top