BlackVue Elite 9 - Testing/Review - RCG

I posted three plate capture examples in my Elite 10 review thread.

 
I updated the Elite 9 and Elite 10 to firmware version 1.005. I have more parking lot comparison footage in my Elite 10 thread.

 
I updated the Elite 9 and Elite 10 to firmware version 1.005. I have more parking lot comparison footage in my Elite 10 thread.

Earlier you mentioned you were using the older coax cable (from 970x plus) for the rear camera of your latest elite 9.
Did you encounter any issues ?
 
Earlier you mentioned you were using the older coax cable (from 970x plus) for the rear camera of your latest elite 9.
Did you encounter any issues ?
I have not found any problems using the older coax cable with the Elite 9 [so far]. For the Elite 10, I'm using the "new" cable for the connection to the 4K rear camera.
 
I have not found any problems using the older coax cable with the Elite 9 [so far]. For the Elite 10, I'm using the "new" cable for the connection to the 4K rear camera.
Thanks for the update. Hopefully you can keep testing with the older coax cables and let us know if you run into any issues. A lot of us are keen to upgrade the cameras, but would really prefer not to replace the existing cables, at least for the Elite 9 system with the 2K rear camera.
 
Thanks for the update. Hopefully you can keep testing with the older coax cables and let us know if you run into any issues. A lot of us are keen to upgrade the cameras, but would really prefer not to replace the existing cables, at least for the Elite 9 system with the 2K rear camera.
I've been using both the Elite 8 and Elite 9 since release with no issues using older original coax.

The existing cables are compatible.
The newer cables just have improved shielding and higher bandwidth for futureproofing for future models.
 
I've been using both the Elite 8 and Elite 9 since release with no issues using older original coax.

The existing cables are compatible.
The newer cables just have improved shielding and higher bandwidth for futureproofing for future models.
Thanks you..! the more testing data the better.
 
I believe I found the "white noise" issue reported on this site in the Elite 9 / Elite 10 parking mode impact files.

What surprised me more were the two video issues I found in the impact video files. During the 10-second buffered period, the video is very choppy. It looks like 15 fps recorded content being played back at 30 fps. At the 10-to-11 second mark when it transitions from buffered content to “live” content, there’s a very noticeable white flash that occurs. The remaining 50-seconds of the video has smooth video, but that low volume “white noise” appears to be present. The rear camera’s 10-second buffered content looks a bit choppy as well and it also smooths out for the remaining 50-seconds of the video. Both the Elite 9 and Elite 10 have the "color flash" issue present in the 1.005 firmware. I found the color flash issue in Elite 9 footage back to firmware version 1.003. I've reported the issue to Pittasoft.

I provided sample footage to Pittasoft for these issues: https://drive.google.com/drive/folders/1a3SiqH7eJCGxbewzh29PJlL6pxc-vVFi?usp=sharing
 
I believe I found the "white noise" issue reported on this site in the Elite 9 / Elite 10 parking mode impact files.

What surprised me more were the two video issues I found in the impact video files. During the 10-second buffered period, the video is very choppy. It looks like 15 fps recorded content being played back at 30 fps. At the 10-to-11 second mark when it transitions from buffered content to “live” content, there’s a very noticeable white flash that occurs. The remaining 50-seconds of the video has smooth video, but that low volume “white noise” appears to be present. The rear camera’s 10-second buffered content looks a bit choppy as well and it also smooths out for the remaining 50-seconds of the video. Both the Elite 9 and Elite 10 have the "color flash" issue present in the 1.005 firmware. I found the color flash issue in Elite 9 footage back to firmware version 1.003. I've reported the issue to Pittasoft.

I provided sample footage to Pittasoft for these issues: https://drive.google.com/drive/folders/1a3SiqH7eJCGxbewzh29PJlL6pxc-vVFi?usp=sharing
I don't think I have the flash issues that your videos have, but I have to check again, focusing on the transition from parking to live video and vice versa. IIRC, my Thinkware would always cut the video clip once the ACC was turned on, so when I noticed that the Blackvues continued recording in the same clip, it was interesting. I do have the white noise, though. Glad I'm not the only one with that problem.

When I'm back at the car I can download some more clips.

Edit: @rcg530, it doesn't look like my clip has the flash issue during this simulated impact with me shutting the door, assuming I reproduced the issue correctly.

 
Last edited:
I don't think I have the flash issues that your videos have, but I have to check again, focusing on the transition from parking to live video and vice versa. IIRC, my Thinkware would always cut the video clip once the ACC was turned on, so when I noticed that the Blackvues continued recording in the same clip, it was interesting. I do have the white noise, though. Glad I'm not the only one with that problem.

When I'm back at the car I can download some more clips.

Edit: @rcg530, it doesn't look like my clip has the flash issue during this simulated impact with me shutting the door, assuming I reproduced the issue correctly.

Your sample video seems to be with the dash camera transitioning from normal recording mode [30 FPS] to parking recording mode when the impact occurred. My example was with the dash camera already fully in time-lapse parking mode when the impact event occurs.

I received an explanation of why the "flash" event is occurring from Pittasoft. While in time-lapse parking mode [in my case], the video/audio buffer is being filled at a rate of 15 FPS. Pittasoft reduced the buffer fill rate from 30 FPS to 15 FPS to reduce the amount of power the parking mode requires. When the impact event takes place, the buffered impact video is first created with 10 seconds of content from the buffer [15 FPS] and the remaining 50 seconds are captured at 30 FPS. The transition from the 15 FPS content in the buffer to the 30 FPS content being captured "live" is when the "flash" takes place. Pittasoft is looking into whether the "flash" can be reduced in a future firmware release.
 
Your sample video seems to be with the dash camera transitioning from normal recording mode [30 FPS] to parking recording mode when the impact occurred. My example was with the dash camera already fully in time-lapse parking mode when the impact event occurs.

I received an explanation of why the "flash" event is occurring from Pittasoft. While in time-lapse parking mode [in my case], the video/audio buffer is being filled at a rate of 15 FPS. Pittasoft reduced the buffer fill rate from 30 FPS to 15 FPS to reduce the amount of power the parking mode requires. When the impact event takes place, the buffered impact video is first created with 10 seconds of content from the buffer [15 FPS] and the remaining 50 seconds are captured at 30 FPS. The transition from the 15 FPS content in the buffer to the 30 FPS content being captured "live" is when the "flash" takes place. Pittasoft is looking into whether the "flash" can be reduced in a future firmware release.


Thank you for bringing this issue to our attention. We have identified the cause and prepared a solution. It is currently undergoing internal validation and will be addressed in the next firmware version.
 
I captured some frame grabs from three 4K rear cameras and four 2K rear cameras.

4K Rear Cameras - BlackVue Elite 10 No HDR, VIOFO A229 Ultra HDR, 70mai T800 HDR

2K Rear Cameras - BlackVue Elite 9 HDR, Thinkware U3000 Pro 2K Rear HDR, VUEROID S1-4K 2K Rear HDR, VIOFO A329S 2K Rear HDR

 
This video contains day and night driving video samples from the BlackVue Elite 9 4K UHD front / 2K QHD rear dash camera and the BlackVue 10 4K UHD front / 4K UHD rear dash camera.

 
Elite 8/9/10 - EV Power Accessory [G-Sensor Parking Mode]

An over-the-air firmware update version 1.006 for the Elite 9 and Elite 10 adds support for G-Sensor parking mode operations when powered by a vehicle USB-C port capable of providing 12V or the included cigarette lighter USB-C power adapter in an "Electric Vehicle". I don't have an Elite 8 dash camera, so cannot confirm the version of the updated firmware for that dash camera. These firmware updates are not yet available via the BlackVue website. You must have the latest version of the iOS [4.17] / Android [4.21] BlackVue app to take advantage of this new feature/setting.

1772055013867.webp


In the "Parking Mode Recording" settings, a new "EV Accessory Power" link/section has been added. This allows the Elite dash camera to operate in parking mode using USB-C provided power and the vehicle remains stationary for 5-minutes. This appears to implement a "vehicle motion based" [enter into and exit from] parking mode feature similar to the older BlackVue dash cameras in the Elite series of dash cameras.

1772055157936.webp
1772055250655.webp
 
Last edited:
Yeah, I noticed this on my Elite 10. Even with it set to 11.8V, after I got the notification that the cam was shutting down the next time I started the car my B130A reported it still had 27% battery.

I just received my TWO Elite 10 DUAL cams (to create a 360° view), and I was not aware of this limitation.

At the moment, I have TWO Thinkware U1000 dual cams installed, and each one runs on a large external battery pack (each camera has a main unit plus two extension packs: https://www.power-core.co.uk/products.html).
On those cams you can set the cut-off to “off”.

On the Elite, the 48-hour timer is too short, and 11.8V is too low; i will never the get maximum running time out of my batteries this way

I truly start regretting my purchase now.

We should be able to decide for ourselves whether we want this feature enabled or not.

Really hope this will be addressed by BV!
 
I just received my TWO Elite 10 DUAL cams (to create a 360° view), and I was not aware of this limitation.

At the moment, I have TWO Thinkware U1000 dual cams installed, and each one runs on a large external battery pack (each camera has a main unit plus two extension packs: https://www.power-core.co.uk/products.html).
On those cams you can set the cut-off to “off”.

On the Elite, the 48-hour timer is too short, and 11.8V is too low; i will never the get maximum running time out of my batteries this way

I truly start regretting my purchase now.

We should be able to decide for ourselves whether we want this feature enabled or not.

Really hope this will be addressed by BV!
Agree, I had brought this up to support as I also upgraded from the U1000 and said in my post that it's not something they support at the moment and they recommended I use the low power mode to get longer time. Bummer

I have it set to 48 hours and it fits my needs but for people with extended batteries this poses an issue.


Also unrelated, does the Blackvue iOS app constantly log anyone out? Almost every time I need to use it, the app has me logged out.
 
Without wanting to sound dramatic, i seriously regret going back to BV .

For years i was with Thinkware, without this hassle and on top their cloud is FREE

I might just return them and keep my U1000's for now

What i also don't understand is why you get a free cloud subscription with every BV camera, yet you have to pay if you register more than one.
So the more cameras you buy from BV, the more you get punished. funny way of doing business.

I should have done more research i guess. My bad.
 
Last edited:
...

Also unrelated, does the Blackvue iOS app constantly log anyone out? Almost every time I need to use it, the app has me logged out.
I had that with my Elite 9, In the end, it was the least of my concerns. Strangely, it logged in OK for the first few days.
 
Back
Top