Updated IQ

... Less sharp screenshots show the maximum level
details, and those that seemed sharp are hopelessly spoiled by a sharpe and lost in detail.
This is what producers & managers do in advertising. In YouTube reviews, the picture appears sharp and
detailed, but as soon as you start to watch the originals in full size,
then you involuntarily think: "Excuse me, but where is the quality???"...
Yes, and besides, the bit rate also affects the quality of the picture.
Currently, the B4K flow rate for UHD is only 27,1 Mbit/s (which is extremely low), and it is required to at least double this figure for 4K.
(This is an indicator of the total bitrate. For 2560x1440 it is 15.0 Mbit / s, and for 1920x1080 it is 8.66 Mbit / s).
 
Another small test - comparison of the Original v009 - 4K (3840x2160) and modified firmware - 4K (3840x2160) and 1440 (2560x1440)
v009 4K EV= 0.0
2_v009_jeely-2.jpg
Mod 4K EV= 0.0
2_4K_MOD_jeely-2.jpg
Mod 1440 EV= -1/3
2_1440_MOD_jeely-2.2.jpg
v009 4K raw video here (1 min / 193,6 MB) EV= 0.0
1_v009_jeely.jpg

MOD 4K raw video here (1 min / 301,4 MB) EV= 0.0
1_4K_MOD_jeely.jpg

MOD 1440 raw video here (1 min / 301,4 MB) EV= -1/3
1_1440_MOD_jeely.jpg
 
Last edited:
Blueskysea B4K v009 MOD - Bitrate, Contrast, Sharpness, Gamma, DE, Others...
Hi @Falsificator , I see there are newer versions of - Blueskysea B4K v015 MOD released Feb2023 - is there any newer changelog showing what these releases have?

I am using B4k_20220113_V015 firmware and timelapse in parked mode at 1FPS. I have had two incidents when the car is parked, both of which were captured by the front camera but the image is not sharp enough to capture the number plate. I have since noticed that there is 2/5/10 FPS timelapse mode and have moved to 10 FTP timelapse mode. edit: (parking mode timelapse seems to be fixed at 1FPS)

For example here is the attached image where the number plate is not clear (extracted frame using avidemux), and the info on the timelapse video produced by the b4k. Would your version of the MOD firmware improve the ability of timelapse parking mode to get sharper images especially with number plates ? any ideas of any image processing techniques to try and better identify the number plate from attached image? - it is very blurred (not sure if it is reflection and lack of CPL filter?) and I'm not very hopeful of being able to "decode" the number plate.

Code:
=====================================================
Video
=====================================================
Codec 4CC:                H265
Image Size:                1920 x 1080
Aspect Ratio:            1:1 (1:1)
Frame Rate:                30.000 fps
Average Bitrate:        8389 kbps
Total Duration:            00:02:59.933
Pixel format:            YUV 4:2:0, 8-bit
Color range:            Full (JPEG)
Color primaries:        BT.709
Transfer characteristics:    BT.709
Color space:            BT.709


Also in the settings menu on the camera itself there is a numberPlate option that can be turned on/off. It was set as off for my (I think by default). i have checked the manual pdf and also searched this forum, and I couldn't find what exactly this option is supposed to do. I didn't see this option in the ucam android app 1.9.4.02 (11th oct 2022). Anyone know what its supposed to do?
 

Attachments

  • reg_truck.png
    reg_truck.png
    2 MB · Views: 10
Last edited:
I can’t say anything about the time-lapse mode, since I’ve never had this recorder
and I can’t answer for all video modes. With one user from Russia who had this recorder,
we were able to create firmware that improves the quality of video in the main modes.
I don't have an answer to your question, sorry...
 
I can’t say anything about the time-lapse mode, since I’ve never had this recorder
and I can’t answer for all video modes. With one user from Russia who had this recorder,
we were able to create firmware that improves the quality of video in the main modes.
I don't have an answer to your question, sorry...

I had the firmware Blueskysea B4K V015 (20220113) - MOD-1.0.zip installed on my camera for the last two months and what I noticed was
* the bitrate of the files increases from: 8665 kb/s to bitrate: 41953 kb/s (5x) therefore a 3 minute FHD clip, that took 200mb now occupies 1gb each
* the increase in the bitrate/file size seemed to make the camera totally unreliable, there were loads of video files missing (neither in the default or RO folder). I use a sandisk high endurance 256Gb UHS-I Class 10 U3 V30 and didn't have this problem with the default firmware. So will be reverting back to the default firmware.
 
I had the firmware Blueskysea B4K V015 (20220113) - MOD-1.0.zip installed on my camera for the last two months and what I noticed was
* the bitrate of the files increases from: 8665 kb/s to bitrate: 41953 kb/s (5x) therefore a 3 minute FHD clip, that took 200mb now occupies 1gb each
* the increase in the bitrate/file size seemed to make the camera totally unreliable, there were loads of video files missing (neither in the default or RO folder). I use a sandisk high endurance 256Gb UHS-I Class 10 U3 V30 and didn't have this problem with the default firmware. So will be reverting back to the default firmware.
The bitrate is variable and directly depends on the amount
of lighting in the video frame and the dynamics in the video frame.
The card needs to be formatted in FAT32 in the SD Card Formatter.
https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/
After this, you need to format with the largest cluster size in the GUI format.
http://ridgecrop.co.uk/guiformat.exe
The problem should go away. Large cards are often unpredictable in write-read-overwrite mode.
 
Its already FAT32 and 64k cluster as formatted by the camera itself.

Code:
Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1  *     8192 499744767 499736576 238.3G  c W95 FAT32 (LBA)


Code:
sudo dosfsck -v -n /dev/sdb1

fsck.fat 4.2 (2021-01-31)
Checking we can access the last sector of the filesystem
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
  Not automatically fixing this.
Boot sector contents:
System ID "SYSTEMID"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
     65536 bytes per cluster
      4540 reserved sectors
First FAT starts at byte 2324480 (sector 4540)
         2 FATs, 32 bit entries
  15614976 bytes per FAT (= 30498 sectors)
Root directory start at cluster 2 (arbitrary size)
 
Its already FAT32 and 64k cluster as formatted by the camera itself.
Feedback from a couple of my testers on this firmware modification did not
reveal any problems with writing to the memory card. And since I have never
seen or held this DVR in my hands, I cannot give you more complete information...
 
Back
Top