Reviewing and Testing the Vantrue Nexus 5S

Could you please let us know the firmware version of your N5S?
IMG_5809.webp
 
Yep, just updated both front and rear firmware. Should be good now. I'll need a few days to retest my previous scenario - I don't drive my car every day.
 
Last edited:
I was in normal drive mode. I was using the menu to switch between HDR on/off for the rear camera. It looks like with the original firmware, it was cropping from the sensor using different techniques/algorithms.
 
@Jeff_Vantrue
I have a request that would be REALLY helpful, but I'm not sure if it is possible. When I look at the list of video files that come out of any of the Vantrue cameras on the SD card, the file timestamps in Windows Explorer show the actual times that the files were made. But, when I copy those files from the SD card to the hard drive on my computer, all of the file time/date stamps are updated to the UTC time that is embedded in the meta data of the MP4 file. For me, this adjustment is UCT-5. Thus, all of the files on my computer are now "off" by -5 hours, which is really a pain when I try to correlate my recollection of specific segments of videos that I am looking for.

Would it be possible to embed my actual local time (UTC + timezone adjustment) in the MP4 metadata so the times remain accurate/constant as I move them from the SD card to my computer? Presently, it seems that only the "UTC" time (which is not my local time) is embedded in the MP4 metadata. It's a small detail, but would be really awesome!
 
@Jeff_Vantrue
I have a request that would be REALLY helpful, but I'm not sure if it is possible. When I look at the list of video files that come out of any of the Vantrue cameras on the SD card, the file timestamps in Windows Explorer show the actual times that the files were made. But, when I copy those files from the SD card to the hard drive on my computer, all of the file time/date stamps are updated to the UTC time that is embedded in the meta data of the MP4 file. For me, this adjustment is UCT-5. Thus, all of the files on my computer are now "off" by -5 hours, which is really a pain when I try to correlate my recollection of specific segments of videos that I am looking for.

Would it be possible to embed my actual local time (UTC + timezone adjustment) in the MP4 metadata so the times remain accurate/constant as I move them from the SD card to my computer? Presently, it seems that only the "UTC" time (which is not my local time) is embedded in the MP4 metadata. It's a small detail, but would be really awesome!

You're copying the files from one location to another so the modified date is going to change. That's how windows handles its file structure. Created Date and Modified date aren't the same.
 
It's not a Date Modified attribute. The time shift displayed in windows is a function of the Time Zone differential (-4 hrs, not the -5 that I said above) because the date is encoded as UTC, not local time where I am located. Though, perhaps this is a function of the GPS unit. I have two screen captures below.

This first screen cap is with the file still on the SD card. I have overlaid the file attributes displayed by the MediaInfo app with the Windows File Explorer display. All of the red arrows indicate the same time code, but at the very top, the time code is encoded as UTC, not UTC plus my time zone offset.
Time Stamps on SD Card.webp


In this image, I have copied the file highlighted above from the SD card to the hard drive on my computer. Inspecting the file time stamps now shows a time offset because Windows applied the time zone adjustment (show with blue arrow) - this is not the time stamp of when I copied the file (which shown with the green arrow). It is my guess (I could be wrong) that the time shift that appears when copying the file is because the original file is not encoded with UTC + time zone offset as stored in the camera, it is stored only as UTC time. Is this more clear?
Same File Copied to HD.webp
 
Last edited:
@Jeff_Vantrue
I have a request that would be REALLY helpful, but I'm not sure if it is possible. When I look at the list of video files that come out of any of the Vantrue cameras on the SD card, the file timestamps in Windows Explorer show the actual times that the files were made. But, when I copy those files from the SD card to the hard drive on my computer, all of the file time/date stamps are updated to the UTC time that is embedded in the meta data of the MP4 file. For me, this adjustment is UCT-5. Thus, all of the files on my computer are now "off" by -5 hours, which is really a pain when I try to correlate my recollection of specific segments of videos that I am looking for.

Would it be possible to embed my actual local time (UTC + timezone adjustment) in the MP4 metadata so the times remain accurate/constant as I move them from the SD card to my computer? Presently, it seems that only the "UTC" time (which is not my local time) is embedded in the MP4 metadata. It's a small detail, but would be really awesome!
Thank you very much for your suggestion. Just to clarify, the issue is not with UTC itself. The video files are saved in a fixed 24-hour format, and the camera only allows switching between 12-hour and 24-hour display on the screen — not in the file naming or metadata.
We recommend setting your computer to 24-hour time format and checking again. This should make the file timestamps easier to match with your recordings.
 
the camera only allows switching between 12-hour and 24-hour display on the screen — not in the file naming or metadata.

I was wondering if this particular metadata was controlled by the GPS unit and not editable (which makes sense, because then GPS timestamp data would lose its accuracy/relevance). This is what I was looking for, thank you!

@jsmith - not yet, likely this weekend.
 
Ha, when I originally updated the N5S firmware, I screwed up and only updated the front camera firmware. I used the link provided by @Karagandinez in his thread. This linked to the following page that only has front camera firmware:


Then, @jsmith posted a link to another page that showed firmware updates for both the front and rear cameras


@Jeff_Vantrue - is it possible to have a single location on the Vantrue website for firmware updates so people don't inadvertently miss an update in the future? This would simplify the user experience.
 
Ha, when I originally updated the N5S firmware, I screwed up and only updated the front camera firmware. I used the link provided by @Karagandinez in his thread. This linked to the following page that only has front camera firmware:


Then, @jsmith posted a link to another page that showed firmware updates for both the front and rear cameras


@Jeff_Vantrue - is it possible to have a single location on the Vantrue website for firmware updates so people don't inadvertently miss an update in the future? This would simplify the user experience.

@EricSan I already raised that issue and that's why BOTH front and rear Firmware are now listed together on same page! Way ahead of you!
 
Ha, when I originally updated the N5S firmware, I screwed up and only updated the front camera firmware. I used the link provided by @Karagandinez in his thread. This linked to the following page that only has front camera firmware:
There are also firmwares for rear cameras:
@Jeff_Vantrue - is it possible to have a single location on the Vantrue website for firmware updates so people don't inadvertently miss an update in the future? This would simplify the user experience.
Don't new firmware, if available, arrive when connecting the application to the DVR?
 
Vantrue has 2 pages with updates.
On one page, the firmware for the front and rear cameras are located separately:
On the other page, the firmware for the front and rear cameras are located together:
 
Don't new firmware, if available, arrive when connecting the application to the DVR?

I've not noted that behavior, but my own behavior is perhaps an anomaly. I don't use a cell phone (gasp...). I have the app on my ipad (wifi), so I'm either connected to the home router OR the camera, never both at the same time.
 
I already raised that issue and that's why BOTH front and rear Firmware are now listed together on same page!
This is super useful, for sure. I was looking for the next step of removing the duplicate pages because they don't contain the same software updates. This is the classic "concurrency control" issue when things live in more than one location.
 
This is super useful, for sure. I was looking for the next step of removing the duplicate pages because they don't contain the same software updates. This is the classic "concurrency control" issue when things live in more than one location.

The old link might work, but google vantrue firmware and it no longer takes you to updates WITHOUT both cameras listed.
 
Ha, when I originally updated the N5S firmware, I screwed up and only updated the front camera firmware. I used the link provided by @Karagandinez in his thread. This linked to the following page that only has front camera firmware:


Then, @jsmith posted a link to another page that showed firmware updates for both the front and rear cameras


@Jeff_Vantrue - is it possible to have a single location on the Vantrue website for firmware updates so people don't inadvertently miss an update in the future? This would simplify the user experience.
Thanks for the suggestion! At the moment, we’re focusing on Vantrue.com as the main site for firmware updates. The Vantrue.net site will be phased out in the near future.
 
EDIT: looks like this was my official 1,000th post here. How about that... 😎

Work has gotten very busy lately, but I did find some time to drive around in circles in traffic waiting for just the right opportunity to make some video captures using the new N5S camera. I have the N5S mounted side by side with the N4S which is fun because they both have 2.5k front facing cameras that use the very same sensor. Just for fun, I compared both of these to my Viofo A139 Pro camera, which is not entirely a fair comparison because it features a 4k front camera, but the results were a little surprising.

Here is the overall scene: I'm sitting in a turn lane with a red light and traffic is moving past in the lanes to my right at about 35-40mph. First up are images from each camera just to show overall renderings - these images are just screen captures from VLC player.

From the N5S: WDR mode is enabled, no adjustment to exposure. Circular polarizer is installed:
N5S Ambulance Entire Frame.webp


The same scene from the N4S is below. I need to re-adjust the exposure level to +0.6. When HDR and PlatePix are both enabled, the overall scene is a bit darker. It would be really great if these settings were stored in non-volatile memory in the camera so firmware updates don't blow away all of the setting changes that I make...
N4S Ambulance Entire Frame.webp


And finally, here is the same scene from my A139P (4k front camera) with HDR enabled:
A139P Ambulance Entire Frame.webp


The three images above are not precisely time-aligned because VLC doesn't allow the level of granular frame-by-frame advance that CapCut allows. So, using CapCut, I advanced the video from each camera, frame by frame, until the rear left wheel of the ambulance was aligned with the second white stripe from the crosswalk as shown below:
N5S Ambulance Wheel Alignment.webp



Then I zoomed in 250% and focused on just the license plate. Here are the results of a 250% zoom/crop on just the ambulance rear plate from each camera:

N5S:
N5S Ambulance Plate 250p.webp


N4S:
N4S Ambulance Plate 250p.webp


A139P:
A139P Ambulance Place 250p.webp


As with the overall scene that I posted above, the N4S image is a bit darker, but both the N5S and the N4S render the plate in a manner that is completely readable. If I use photo software to adjust the brightness and contrast of the plate from the N4S, it very closely matches the image from the N5S. The surprise to me was the A139P that had the blurriest rendering of the three despite (or perhaps because of) its higher resolution.

Then, I advanced the video from each camera by 5 more frames (ambulance is now further away) to have another look.
N5S zoom/crop is still very readable
N5S Ambulance Plate 250p 5frames.webp


N4S zoom/crop starts to become more more difficult to read. In this case, merely increasing image brightness and contrast does not produce an image that equals that of the N5S. I've read a little about how Wide Dynamic Range is achieved through hardware and often produces a softer image than High Dynamic Range processing which is performed by software, but I have found exactly the opposite here. WDR from the N5S wins over the HDR + PlatePix from the N4S. I thought the lack of PlatePix in the N5S would be a detriment. This is not the case.
N4S Ambulance Plate 250p 5frames.webp


A139P: The rendering from the A139P is still readable and very similar to the lower resolution N5S camera and a pinch ahead of the N4S rendering. Again, this is a surprise given the higher resolution of the A139P.
A139P Ambulance Place 250p 5 frames later.webp


I should probably repeat this set of images and zooms with HDR/WDR turned off and see how that impacts the clarity of the resulting images. That would be an interesting comparison and provide some additional insights about using HDR (or not) during the day with moving targets.
 
Last edited:
Back
Top