Downloading videos files directly from camera via web interface (using other than IE) seems to be capped at *TEN* Mbps

Again, it may be 2025, but the firmware is code written decades ago. Between that and under powered processors, this is what we get.

Sadly nobody else on the market competes in low light at this price point, so we either deal with the occasional frustration when needing to get into the GUI or spend 5 times the amount for Axis with modern GUIs.

Choice is your lol
 
@alekk

I tried everything. Different browser, pc, wifi, lan, plugin, better sdcard

On 54pro it takes around 20-30min ! to download a 500mb dav file.
On all other 5442 in the same network, no matter if wifi, lan, plugin, vpn it takes only 3-5min to download the same 500mb dav.

Bit strange that you can download fast from 54pro.
 
Yes
its even slow when powering with 12v and direct to pc

According to the switch/pc the cam sync with 100mbit.

So most people dont use sdcard, bit wondering why alekk can download fast. Thought its another bug
 
I cannot use the same cable when its mounted somewhere :D. Also i can see errors in the switch/pc.

I swap the cables from the 5442s next to the 54pro, also sdcards. On the desk its another cable lol. Still 5442 is fast, 54pro not.

I dont need theoretical stuff. Its the cam itself. So who else tried it on 54pro ? With recording still running etc
 
I cannot use the same cable when its mounted somewhere :D. Also i can see errors in the switch/pc.

I swap the cables from the 5442s next to the 54pro, also sdcards. On the desk its another cable lol. Still 5442 is fast, 54pro not.

I dont need theoretical stuff. Its the cam itself. So who else tried it on 54pro ? With recording still running etc

Ok.. I only try to help..

This is just another yours sarcastic answer to me, so I'll let it go..
 
  • Like
Reactions: looney2ns and TonyR
I have it mounted without an SD card, so no..

And thats the problem what you still not understand.
We are trying to merge out bugs from the firmware. Some might be a bug, some might be broken hardware/user error.
Maybe CPU power is limited, cannot do everything at the same time, limit sdcard speed... ?? who knows.
Sure one already swaped the network cable/sdcard/pc/browser/connect directly.
Theoretical / marketing stuff do not help. Real reports does.

Slower speed from sdcard compared to 5442 is on the buglist, so i am wondering why @alekk can even download faster than 5442.
 
  • Like
Reactions: alekk
And thats the problem what you still not understand.
We are trying to merge out bugs from the firmware. Some might be a bug, some might be broken hardware/user error.
Maybe CPU power is limited, cannot do everything at the same time, limit sdcard speed... ?? who knows.
Sure one already swaped the network cable/sdcard/pc/browser/connect directly.
Theoretical / marketing stuff do not help. Real reports does.

Slower speed from sdcard compared to 5442 is on the buglist, so i am wondering why @alekk can even download faster than 5442.

I understands this very well.. repeated many times on this thread - report problems to Andy.. And wait for next firmware with fix (or not).

I understands one more thing - Dahua to fit release dead line, released this camera with very alpha quality firmware. Which never should be published to end-users..

The same story was with TIOC-PRO one year ago (where I bought 8 cams very early and almost immediately installed to end-users).

But this is cost of having access (Andy channel) to product 2-3 months before everyone else (classic Dahua channels)..

That's why I don't get so excited about every problem reported here at this alpha firmware phase..

Please simply reports problems to Andy. Dahua have own test labs / test utilities where they retest / reconfirm (or not) each reported problem.

And we must wait for next more stable (I hope) firmware versions...

Question to Andy (@EMPIRETECANDY):
Could You ask Dahua, does they have never firmware release candidate (official ones)?
firmware .2 was released in August almost 2 months ago... There should be .3 or even .4 official firmwares in pipe line now.

Usually there is one month gap between firmware release candidate published on internal Dahua server and official release on Dahua webpage we see.
 
Last edited:
  • Like
Reactions: alekk and duplo
. Also i can see errors in the switch/pc.
What is the nature and number of the errors? This might be significant and relevant to the problem you are exploring.

Suggestion :
Reset the error count on the switch port, do a test data transfer, check the errors.
A normal connection should give zero errors even after months of use.
 
@alekk

I tried everything. Different browser, pc, wifi, lan, plugin, better sdcard

On 54pro it takes around 20-30min ! to download a 500mb dav file.
On all other 5442 in the same network, no matter if wifi, lan, plugin, vpn it takes only 3-5min to download the same 500mb dav.

Bit strange that you can download fast from 54pro.

As others have commented, it sounds like you have a network issue with your 54PRO.

You could further troubleshoot this by trying to download a snapshot - the 10 MBYTE PNG is basically right away for me (both the 5442 and 54PRO) so I presume it's downloaded in a second. Ditto if you want to repush a .bin firmware file. For both of those, I see ~10 MBYTES/second ... which is basically 100 Mbit/sec ... note I'm intentionally capitalizing BYTES versus bits to make the distinction clear.


Your 5442-S3 times are in the ballpark to what I see - albeit a bit faster ... since 500 MBYTES in 5 minutes would be 1.67 MBYTES/sec. Which I do find a bit perplexing (can you remeasure?) because all my testing is on my internal LAN which seems is fast. I get full Gbit speeds between devices capable of it ... and as noted above, I see the full 100Mbit/sec to the cameras for PNG downloads and firmware uploads.

Recall I see 1.3 MBYTES/sec from a T54PRO-ZE and I just tested my 2nd copy which was about the same. And I just did a morning download from the 5442-S3 and saw the same 0.9MBYTES/sec.

Those are WAAYYY slower than what you would expect from a 100Mbit line!

And yes, all of those are in "production" recording to the card, having ffmpeg pull a stream, and some (very simple) AI rules applies.
Side note: Is there any way to tell how "busy" the camera is - i.e. a "load factor". I haven't tried an ssh connection.
 
Slower speed from sdcard compared to 5442 is on the buglist, so i am wondering why @alekk can even download faster than 5442.

First time I heard this ... so yea, it's possible that if the SD interface is really (REALLY!) screwed up, that would throttle the speeds. Since the PNG download and firmware upload probably don't involve the SD card.

Is this an "official" Dahua published buglist?
It would be great to put this issue on it ... since it is easily replicated and if someone knowledgeable on the network/browser code (easy to look internally and check if the SD card throughput is (bizarrely) the issue) looked at, I bet they'd figure it out pretty quick.

The 512 GByte Samsung EVO Select SD card I have in my cameras (plural) is rated at 160 MBYTES/sec and were "fresh" & formatted. Realistically, I doubt you would ever see those speeds ... but clearly the card itself can provide data WAAYYY faster than 1.3 MBYTES/second.

@EMPIRETECANDY : Ditto @steve1225's question about firmware in the pipeline - I know you said something elsewhere about working on the next release - any more specific news?
 
I can confirm:

video footage download from camera web interface using clean browser (no plugins, Mac, safari) is capped at 1.2-1.3 MB/s per ONE download using much much faster Samsung PRO Endurance 256GB sd-card...

I can start 6 parallel processes of downloading the same big chunk of video footage - speed going down to 300 KB/s per each download...

this don't look like SD interface problem (I downloaded at the same time the same video footage file which is cached in camera memory)... more like bandwidth limit somewhere in camera web server configuration or script..
 
The 512 GByte Samsung EVO Select SD card I have in my cameras (plural) is rated at 160 MBYTES/sec and were "fresh" & formatted. Realistically, I doubt you would ever see those speeds ... but clearly the card itself can provide data WAAYYY faster than 1.3 MBYTES/second.

Side comment:
EVO cards are not dedicated for CCTV usage.
they will die after a few months in 24/7 writing scenarios..

only "Endurance" sd-card models (Samsung, SanDisk etc) with high TBW values are dedicated for usage like this.. they use older flash memory technology which are capable of much more writing cycles..
 
  • Like
Reactions: alekk
Thanks @steve1225 for confirming the issue - means a lot coming from someone as knowledgeable as you.
To be clear to everyone, this is not a "show-stopper" ... but it's an annoying bug ... and ideally should not be hard to fix - LOL if someone looks at the code and there's something that says "throttle video download speed to about 10Mbit/sec so camera CPU and network are not overloaded" ... with the last code update in 2005 ... ;-)


WRT SD Cards: Yea, I know that the "Endurance" is recommended for continuous writing ... but I've been using the EVO Select for several years and (famous last words!) never had a failure. In fact, the Hikvision that I just replaced/retired was recording 7x24 since 2018 with a 64 GByte EVO Select.

Remember I'm a hobbyist with a just a few cams ... so when/if it fails, I'm OK with that and don't mind the downtime and replacing it.
Whereas if I was a professional installer like you, spending the extra $$$ to use the best SD cards totally makes sense.
 
Last edited:
BTW @steve1225 , if you want to see some bugs that got FIXED, try using the "clean browser" and hit the snapshot button on your 5442-S3 ... mine is running Andy's 12/21/2024 firmware.

As an aside, I bet you see the same I do that the (excessively large) PNG file (for my scene it is about 10 MBYTES) is downloaded in about a second ... so there is no throttle there!

NOW ... hit the snapshot button a SECOND time ... I get "Download Blocked" (using Edge ... but NOT Chrome!) ... and I have to close that tab (but not the browser) and reopen to download another snapshot.

NOW ... do the same with the T54PRO-ZE (I'm running the Dahua 8/27/2025 firmware) and you will NOT see this problem - i.e. you can keep downloading snapshots ... as it should be.

There's a similar issue with downloading multiple .dav files where the 5442-S3 fails, but the T54PRO-ZE works ... so SOMETHING got fixed ... maybe part of that code last changed in 2005! ;-)
 
Last edited:
BTW @steve1225 , if you want to see some bugs that got FIXED, try using the "clean browser" and hit the snapshot button on your 5442-S3 ... mine is running Andy's 12/21/2024 firmware.

As an aside, I bet you see the same I do that the (excessively large) PNG file (for my scene it is about 10 MBYTES) is downloaded in about a second ... so there is no throttle there!

NOW ... hit the snapshot button a SECOND time ... I get "Download Blocked" (using Edge ... but NOT Chrome!) ... and I have to close that tab (but not the browser) and reopen to download another snapshot.

NOW ... do the same with the T54PRO-ZE (I'm running the Dahua 8/27/2025 firmware) and you will NOT see this problem - i.e. you can keep downloading snapshots ... as it should be.

There's a similar issue with downloading multiple .dav files where the 5442-S3 fails, but the T54PRO-ZE works ... so SOMETHING got fixed ... maybe part of that code last changed in 2005! ;-)

this only confirms how bad Dahua / HIK is on software / firmware side.

All modern companies / solutions moved to rolling releases in one main line.
So all your supported hardware (from specific company) is receiving the same firmware / software (done from the same base code) with only small changes / limits applied per specific hardware model (you receive what you paid for and what you HW supports).

And company have only one firmware / software line to maintain.

Dahua / HIK duplicates at beginning codebase for each hardware line / model and then develops them (hmm, strong semantic overuse :) independent of other camera lines.
Sometimes some critical changes (bugs) are rebased over all firmware lines - but that's all.
 
  • Like
Reactions: alekk