Vueroid S1 Dash Camera Review

Augustus said:
A329 had reliability issues both with and without enclosures. By the sounds of it, A329S isn't faring much better.

Until Viofo / Novatek / whoever's fault it is , sorts it out, I wouldn't touch any SSD implementation with a six foot pole.
Click to expand...

Yep, the same here. When folks began demanding SSD support, manufacturers tossed the feature at them. We have seen the results, and they are problematic.

It is good to see that VUEROID has identified the various issues with SSD implementation and is working cautiously and carefully toward a reliable solution for users. That is one of the reasons I support VUEROID. They do not jump in and add a feature because 3 people want it, or because it is on a vanity list of requests. VUEROID will apply critical thinking skills to determine whether the feature is valuable and can be implemented without detriment to the dashcam.

The safest path for any manufacturer is to offer guaranteed compatibility and a reliable solution by developing or using an existing enclosure and NVME memory, along with a cable, and selling it. The manufacturer can now work with known controllers and memory, and manage the interface—no more wild-west implementations of user-owned devices.
 
lufa6977 said:
Yep, the same here. When folks began demanding SSD support, manufacturers tossed the feature at them. We have seen the results, and they are problematic.

It is good to see that VUEROID has identified the various issues with SSD implementation and is working cautiously and carefully toward a reliable solution for users. That is one of the reasons I support VUEROID. They do not jump in and add a feature because 3 people want it, or because it is on a vanity list of requests. VUEROID will apply critical thinking skills to determine whether the feature is valuable and can be implemented without detriment to the dashcam.

The safest path for any manufacturer is to offer guaranteed compatibility and a reliable solution by developing or using an existing enclosure and NVME memory, along with a cable, and selling it. The manufacturer can now work with known controllers and memory, and manage the interface—no more wild-west implementations of user-owned devices.
Click to expand...
Nailed it. Great to see Vueroid take a cautious approach as you say, that's what is most beneficial for the end user
 
TonyM said:
In driving recording priority mode, the memory allocation on a 512GB card for normal driving files is 413 minutes of 3CH video at maximum bitrate. That's approximately equal to 60min a day for 7 days, or 80min a day for 5 days.
Click to expand...

What would it be in low bitrate parking mode? Generally, if something happened while driving, you're going to pull off the video immediately or relatively quickly thereafter. The issue is more parking mode than anything else.
 
Augustus said:
A329 had reliability issues both with and without enclosures. By the sounds of it, A329S isn't faring much better.

Until Viofo / Novatek / whoever's fault it is , sorts it out, I wouldn't touch any SSD implementation with a six foot pole.
Click to expand...

1. So are you part of the group testing the A329 series? If so which Model?

2. So is the SSD fault with Novatek? Viofo? Or it has yet to be determined?

3. Do you recommend the A329S / T series if using just MicroSD (quality much better than A139)? Or are you recommending avoiding the A329 til bugs sorted?

@TonyM

So does the Vueroid S1 Infinite 4K support SSD? Or is SSD a feature that is being developed for later models?

I agree, you shouldn't rush to add a feature, until you're certain it works. It ends up coming off as embarrassing if you sell consumers on a feature, and that feature proves unreliable and rushed.
 
jsmith said:
What would it be in low bitrate parking mode? Generally, if something happened while driving, you're going to pull off the video immediately or relatively quickly thereafter. The issue is more parking mode than anything else.
Click to expand...
The S1 4K does not have a low bitrate parking mode.

If you use motion+impact detection parking mode with driving priority mode, the memory allocation on a 512GB card is 137 minutes (274 instances, each 30s long)
If you use motion+impact detection parking mode with parking recording priority, the memory allocation on a 512GB card is approximately 2.5x that at 340 minutes, or about 6 hours (I've not tested it yet)

You can extend the duration of parking coverage by choosing timelapse+impact parking mode. EDIT: I believe timelapse will record 5x longer than motion detection, so that's approx 12 hours or 30 hours depending on the memory allocation option.

Choosing a bitrate lower than HIGH will extend these parking recording durations.
 
Last edited:
TonyM said:
The S1 4K does not have a low bitrate parking mode.

If you use motion+impact detection parking mode with driving priority mode, the memory allocation on a 512GB card is 137 minutes (274 instances, each 30s long)
If you use motion+impact detection parking mode with parking recording priority, the memory allocation on a 512GB card is approximately 2.5x that at 340 minutes, or about 6 hours (I've not tested it yet)

You can extend the duration of parking coverage by choosing timelapse+impact parking mode. I have not yet calculated the allocated recording duration for this mode.

Choosing a bitrate lower than HIGH will extend these parking recording durations.
Click to expand...

1. What is driving mode priority? (Parking Mode)
2. What is parking mode recording priority?

Can you explain difference between these two.

3. What Frame rate is time lapse + impact parking mode?
 
jsmith said:
1. What is driving mode priority? (Parking Mode)
2. What is parking mode recording priority?

Can you explain difference between these two.
Click to expand...
The microSD card is formatted with allocations for driving, driving event, parking and parking event video files. The proportions vary depending on which option you choose.

These screenshots are from the review by @Julian23

44-webp.86912
45-webp.86913

jsmith said:
3. What Frame rate is time lapse + impact parking mode?
Click to expand...
Timelapse is recorded at 1fps, and plays back at 5fps. Any impact recorded in this mode is recorded as normal 30fps video with audio.
 
jsmith said:
1. What is driving mode priority? (Parking Mode)
2. What is parking mode recording priority?
Click to expand...
The "Memory Allocation" setting selects with file allocation strategy [quota system] is to be used with the memory card. Each selection defines the percentage of the total memory card capacity that is to be allocated to that specific type of recording files.
  • For example, the "Driving Recording Priority" memory allocation strategy is setup as follows:
    • 60% driving recording files [INF directory]
    • 15% driving event files [EVENT directory]
    • 20% parking mode files [PARK directory]
    • 5% parking mode event files [PEVENT directory]
Here are the four "Memory Allocation" types you can select from in the firmware menus / VUEROID Hub app:
1761842969842.webp


The VUEROID TFF [Three Free File] system used by the S1-4K is based on a FAT32 file system. Based on the total number of cameras [1-channel, 2-channel, or 3-channel], if the interior camera is connected and enabled for parking mode use, the video bitrate selected, and the memory allocation strategy selected, the S1-4K will format the memory card and pre-allocate [hidden] files within each of the recording file storage directories. The number and size of pre-allocated files are based on the settings I just mentioned. During normal operations of the dash camera as recording files are created, the next unused pre-allocated [hidden] file's storage space is used to write the recording file(s) for that recording type/event. When there are no more unused pre-allocated files available in that directory, the oldest files in that directory are reused for the new recording files. This approach makes sure there's no fragmentation in the recording files and the quota system implemented by the memory allocation strategy makes sure that recording file type does not consume more than the memory allocation's percentage for that recording file type.

jsmith said:
3. What Frame rate is time lapse + impact parking mode?
Click to expand...
All impact/motion triggered parking recording files are recorded at 30fps with audio [if the microphone is enabled in the settings]. Time-lapse video records at 1fps for up to 100 seconds in each video file. The time-lapse playback speed is 5fps which results in a full-length time-lapse video file playing in 20 seconds.

Parking recording files created from "Impact & Motion" or "Impact & Time-Lapse" [impact] are buffered 30-second recording files. The parking mode buffered recording files have 10-seconds pulled from the S1-4K's internal memory buffer and 20-seconds after the triggering event for that recording file. Parking recording files created as a result of a detected impact event while the dash camera is in the Extreme Low Power Mode of parking mode are 30-second unbuffered recording files.
 
jsmith said:
1. So are you part of the group testing the A329 series? If so which Model?

2. So is the SSD fault with Novatek? Viofo? Or it has yet to be determined?

3. Do you recommend the A329S / T series if using just MicroSD (quality much better than A139)? Or are you recommending avoiding the A329 til bugs sorted?

@TonyM

So does the Vueroid S1 Infinite 4K support SSD? Or is SSD a feature that is being developed for later models?

I agree, you shouldn't rush to add a feature, until you're certain it works. It ends up coming off as embarrassing if you sell consumers on a feature, and that feature proves unreliable and rushed.
Click to expand...
I had the A329 and had so many issues with SSD support that were never sorted, that I ended up selling the SSD off. Made some posts here in my threads back in the day.

Other new users also reported their issues with the SSD. Then the A329S series came out and more users reported their issues with SSD not working properly. Granted there are users who have had little to no issues with what SSD brands or ways they use it, but still seems to be a crapshoot between what actually works and not.

Million dollar question as to whose fault it actually is. On the datasheets for the NT98530, SSD support is stated so it makes it seem that novatek is just as much in it as Viofo is. But Viofo never came out and addressed the issue properly either.

A329 and A329S otherwise worked ok for me apart from the SSD issues.
 
TonyM said:
The microSD card is formatted with allocations for driving, driving event, parking and parking event video files. The proportions vary depending on which option you choose.

These screenshots are from the review by @Julian23

44-webp.86912
45-webp.86913


Timelapse is recorded at 1fps, and plays back at 5fps. Any impact recorded in this mode is recorded as normal 30fps video with audio.
Click to expand...

Thank you for the explanation. This is the part I didn't understand in your explanation.
 
rcg530 said:
The "Memory Allocation" setting selects with file allocation strategy [quota system] is to be used with the memory card. Each selection defines the percentage of the total memory card capacity that is to be allocated to that specific type of recording files.
  • For example, the "Driving Recording Priority" memory allocation strategy is setup as follows:
    • 60% driving recording files [INF directory]
    • 15% driving event files [EVENT directory]
    • 20% parking mode files [PARK directory]
    • 5% parking mode event files [PEVENT directory]
Here are the four "Memory Allocation" types you can select from in the firmware menus / VUEROID Hub app:
View attachment 87156

The VUEROID TFF [Three Free File] system used by the S1-4K is based on a FAT32 file system. Based on the total number of cameras [1-channel, 2-channel, or 3-channel], if the interior camera is connected and enabled for parking mode use, the video bitrate selected, and the memory allocation strategy selected, the S1-4K will format the memory card and pre-allocate [hidden] files within each of the recording file storage directories. The number and size of pre-allocated files are based on the settings I just mentioned. During normal operations of the dash camera as recording files are created, the next unused pre-allocated [hidden] file's storage space is used to write the recording file(s) for that recording type/event. When there are no more unused pre-allocated files available in that directory, the oldest files in that directory are reused for the new recording files. This approach makes sure there's no fragmentation in the recording files and the quota system implemented by the memory allocation strategy makes sure that recording file type does not consume more than the memory allocation's percentage for that recording file type.


All impact/motion triggered parking recording files are recorded at 30fps with audio [if the microphone is enabled in the settings]. Time-lapse video records at 1fps for up to 100 seconds in each video file. The time-lapse playback speed is 5fps which results in a full-length time-lapse video file playing in 20 seconds.

Parking recording files created from "Impact & Motion" or "Impact & Time-Lapse" [impact] are buffered 30-second recording files. The parking mode buffered recording files have 10-seconds pulled from the S1-4K's internal memory buffer and 20-seconds after the triggering event for that recording file. Parking recording files created as a result of a detected impact event while the dash camera is in the Extreme Low Power Mode of parking mode are 30-second unbuffered recording files.
Click to expand...

Thank you for the explanation, as this was the part I didn't understand and, and you clarified everything.
 
jsmith said:
1. So are you part of the group testing the A329 series? If so which Model?

2. So is the SSD fault with Novatek? Viofo? Or it has yet to be determined?

3. Do you recommend the A329S / T series if using just MicroSD (quality much better than A139)? Or are you recommending avoiding the A329 til bugs sorted?

@TonyM

So does the Vueroid S1 Infinite 4K support SSD? Or is SSD a feature that is being developed for later models?

I agree, you shouldn't rush to add a feature, until you're certain it works. It ends up coming off as embarrassing if you sell consumers on a feature, and that feature proves unreliable and rushed.
Click to expand...
"So does the Vueroid S1 Infinite 4K support SSD? Or is SSD a feature that is being developed for later models?"
=> not supported.
=> after we finish development , SSD cab be supported as an accessory. that is our plan . but it will take sometime.
 
qusejr2 said:
"So does the Vueroid S1 Infinite 4K support SSD? Or is SSD a feature that is being developed for later models?"
=> not supported.
=> after we finish development , SSD cab be supported as an accessory. that is our plan . but it will take sometime.
Click to expand...
qusejr2 said:
... the most important point to support SSD(via usb) , first power supply and the management of filesystem , filemanage, and reliability. for example , sudden power off , sudden cable off etc. what I'm understanding the SSD is not suitable device for intensive write application , suitable for data retantion . so support SSD is very difficult and need long time.
Click to expand...

This is exactly why I suggested a remotely installed micro-SD card via a USB-C port/cable rather than an SSD.

I hope most, if not all, solutions for an internal micro-SD card will also work for a remotely installed card.
Vueroid already has its own high-quality micro-SD card.
That's half the battle.
And the power consumption of a remotely installed micro-SD card is considerably lower than that of an SSD.

Grilling the micro-SD card inside the dash cam in direct sunlight does not improve reliability.
Hiding the micro-SD card remotely in the shade, significantly reduces the temperature of the card and, to some extent, the dash cam itself, thereby increasing reliability and the safety of evidence.
 
GPak said:
This is exactly why I suggested a remotely installed micro-SD card via a USB-C port/cable rather than an SSD.

I hope most, if not all, solutions for an internal micro-SD card will also work for a remotely installed card.
Vueroid already has its own high-quality micro-SD card.
That's half the battle.
And the power consumption of a remotely installed micro-SD card is considerably lower than that of an SSD.

Grilling the micro-SD card inside the dash cam in direct sunlight does not improve reliability.
Hiding the micro-SD card remotely in the shade, significantly reduces the temperature of the card and, to some extent, the dash cam itself, thereby increasing reliability and the safety of evidence.
Click to expand...

Unfortunately, it's the camera that often shuts down from thermal max, long before the MicroSD. For instance, the Viofo A329 max operating temperature is 65C (149F). A MicroSD can go to 85C (185F), well above what the dashcam can tolerate.

Blackvue's idea of having the dash camerass mount to a central unit that is removed from the windshield would be the most proactive design to mitigate heat. However, Blackvue's trend has not gained traction with other manufacturers.
https://blackvue.com/product/dr770x-box-3ch-dms-pro/

1761877759826.webp
 
qusejr2 said:
"So does the Vueroid S1 Infinite 4K support SSD? Or is SSD a feature that is being developed for later models?"
=> not supported.
=> after we finish development , SSD cab be supported as an accessory. that is our plan . but it will take sometime.
Click to expand...

What might make sense is to have a MicroSD be the main storage, and the SSD serve as secondary storage, as to avoid constant writes and reads from the SSD itself. The trick would be that hardwiring is necessary and setting WHEN the camera could copy all files from MicroSD to SSD each day.
 
jsmith said:
Unfortunately, it's the camera that often shuts down from thermal max, long before the MicroSD. For instance, the Viofo A329 max operating temperature is 65C (149F). A MicroSD can go to 85C (185F), well above what the dashcam can tolerate.

Blackvue's idea of having the dash camerass mount to a central unit that is removed from the windshield would be the most proactive design to mitigate heat. However, Blackvue's trend has not gained traction with other manufacturers.
https://blackvue.com/product/dr770x-box-3ch-dms-pro/

View attachment 87160
Click to expand...
toooooo expensive
 
jsmith said:
Blackvue's idea of having the dash camerass mount to a central unit that is removed from the windshield would be the most proactive design to mitigate heat. However, Blackvue's trend has not gained traction with other manufacturers.
Click to expand...
Street Guardian tried the SG9663DR a few years ago but it was not very popular. I think most consumers do not want multiple black boxes/cameras to mount and wires all over the cabin.

However for some customers this is an ideal solution and the suggestion comes up frequently on these forums.
 
GPak said:
Grilling the micro-SD card inside the dash cam in direct sunlight does not improve reliability.
Click to expand...
I would add that using cheap memory cards, which heat up to high temperatures in the dash cam not from sunlight, but from recording data, increases the heating of the dash cam itself.
 
TonyM said:
Street Guardian tried the SG9663DR a few years ago but it was not very popular. I think most consumers do not want multiple black boxes/cameras to mount and wires all over the cabin.

However for some customers this is an ideal solution and the suggestion comes up frequently on these forums.
Click to expand...

Agreed. The idea hasn't caught on, as I previously mentioned, because I think the separate camera / recording unit configuration creates a cable management headache. People want simplicity, but then moan about reliability. Personally, I would rather a unit be rock solid reliable, than aesthetically pleasing, because a dashcam is your insurance policy. Therefore, the separate configuration wouldn't bother me. To each their own.
 
You must log in or register to reply here.
Back
Top