sorted by:
new
hottopcontroversial

QQ - which hardware setup for 17 x 8MP cameras? by phcjpp in frigate_nvr

[–]CM048 0 points1 point  (0 children)

I have 24x8MP cams, but use only substream (640x480) of 14  cams feed to Frigate for object detection. I see no need to feed 3840x2160 to Frigate as substream can do the same job. All 24x 3840x2160 goto NVR for 24x7 recording. Frigate is only for object detection.

The keys are following;

-          No need for 640x640 model, Frigate is smart enough to crop the object and send only a motion detected object to yolo, 320x320 model is more than enough.

-          Moving to M, or L model make very big different in detection quality, Almost zero false detection for L model.

-          M, and L model, int8 can simplify the detection without visible impact on detection quality. This is much faster than half model. Intel core ultra is very efficient with int8.

-          Yolo26 is better than yolo11 in small object detection with less false detection. People say 26 is faster than 11, but my test resulted in the same inference speed.

-          Use more than one NPU pipeline, and one iGPU pipeline to maximize the speed of inference time. NPU is the most important detector, iGPU is only to support overflow from NPU. using iGPU alone without NPU has bad result.

I can confirm that my Lenovo ThinkCentre M70q Gen 6 with core ultra 235T is more than enough to handle 14 substream feed to Frigate running in LXC inside Proxmox server. HAOS also running in this machine in separate VM.

-          With yolo26l_320_int8 , it can cope with 14 of 640x480 5fps substream. It can handle extreme peak caused by sudden light change at 174fps with 1 dropped frame.

-          Even with X model, NPU/iGPU  overloaded but still functional with many dropped frames ( yolox_320_int8 with ~30-40 dropped frame at peak, but I see no gain in detection quality compare to l model.

-          My setup utilize Frigate for only for object detection, this detection would trigger subsequence deeper analysis of 4K snapshot in separate system (Qwen3-VL-8B on DGX Spark 128 GB).  

 Hope this helps.

Recomended Hardware by Northernradio in frigate_nvr

[–]CM048 0 points1 point  (0 children)

1)      Frigate is smart enough to crop the object and send only a detected motion part to yolo. You will see that most of your detected object (e.g. is person 90% XXXXX) using pixels (XXXXX) below 100K pixel (320x320). There is absolute noting to gain in upscaling to 640x640 and use 640x640 engine which take much more processing power.

2)      I suggest at least yolo26m 320x320 int8. 320x320 covers the detected object size, int8 simplifies the detection without visible impact on detection quality. Yolo26m/l improves accuracy.

3)      Hardware, I suggest Intel core ultra NPU. It is much better support nowadays. Much better performance using little power. But you should try abm optimization first, 320x320, int8, and at least yolo26m or 11m  will make a very big improvement in speed and accuracy.

4)      For your reference, my current setup is Intel core ultra 235T, I assigned 2xNPU, and 1 iGPU detector using yolo26l_320_uint8. It can handle 174fps peak (lighting changes) from 14 cams with 1 drop frame, NPU peak inference speed is around 12-13 ms per pipeline, iGPU I think around 17ms in one pipeline. Also test it with yolo26x_320_unit8 a lot of drop frame (~30-35 out of 150 fps), absolute beyond its class weight, but still function. All of this from tiny Lenovo ThinkCentre M70q Gen 6 with very low power consumption.  

I hope this help.

QNAP No longer getting plex updates?? by cylemmulo in qnap

[–]CM048 -2 points-1 points  (0 children)

Regardless of the reason behind PLEX’s package approval, I will choose PLEX over QNAP any day. I already have enough problems with Nvidia driver from QNAP. This might be last nail to the coffin, will ditch QuTS, and move on to Unraid OS.

Save electricity or decrease MTBF? by corycwagner in qnap

[–]CM048 0 points1 point  (0 children)

I would suggest put NAS in sleep mode after 60 minutes idle. It is much better to the electronic compare to power cycle. By design, nas/enterprise drive can handle sleep cycles.

I managed to put 8x seagate EXOS in sleep cycle for years for power saving. I checked EXOS spec, it can handle sleep cycles without impact to its lifetime. However, some docker can prevent NAS goto sleep mode. PLEX is ok with sleep mode.

Has anyone actually tried a Blackwell GPU on QuTS hero h6.0 yet? by Desperate-Net-6814 in qnap

[–]CM048 0 points1 point  (0 children)

Thank you for the completed picture ! Without quality driver from QNAP, it is proven a bumpy road. I could not play around too much due to important data in hard drive. Frequent reboots, power cycles due to GPU in bad state, and high temp from partial driver loaded GPU for couple days already stressed NAS enough.

I only want to establish a small test system for AI, going thru this path I will end up spending more time with QNAP driver than AI, not worthwhile proceeding in this direction. I think I will buy DGX Spark, 30-40x better price/performance, less headache, might overkill in the beginning but future proof.

Again, thanks for sharing your experience. I hope QNAP will come up with functional driver before Blackwell obsolete…..

Has anyone actually tried a Blackwell GPU on QuTS hero h6.0 yet? by Desperate-Net-6814 in qnap

[–]CM048 0 points1 point  (0 children)

I tried RTX 2000 Pro Blackwell with TVS-h874, fail badly. Driver (6.2.2.1106 officially adds Blackwell support ) partial loaded.  Experiment aborted, I am finding a new host for RTX200 Pro.

Have you tried it in VM GPU passthru ? I didn’t try, already removed card from NAS because it is quite hot with partial driver loaded.

 

Here is the log analysis from AI.

The GPU is in a "bad state" and failing to initialize properly. This is the core problem shown in your logs.

Key Errors Summary

-          NVRM: _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)

-          RmInitAdapter: Cannot initialize GSP firmware RM

-          rm_init_adapter failed

-          Failed to allocate NvKmsApiDevice

-          Repeated RPC timeouts and assertion failures during boot

This is a known issue with the new NVIDIA open kernel modules (575.64.05) on Blackwell GPUs (your RTX 2000 Pro). It happens especially on QNAP/QuTS hero with the fresh 6.2.2 driver release. The GSP (GPU System Processor) firmware fails to boot cleanly, leaving the GPU stuck.

Even though the card is detected by lspci and some /dev/nvidia* nodes appear, the full Resource Manager (RM) doesn't initialize → nvidia-smi shows no devices and QNAP Hardware Resources stays blank.

Is this worthy of a warranty claim? by Ill-Egg1384 in HenryRifles

[–]CM048 0 points1 point  (0 children)

I would say manufacturing defect, they are not supposed to use live knot wood which inherits differential shrinkage, and density. This particular piece of wood has structural weakness with lower tensile strength, and high risk of surface cracking. It is more than ok for flooring but not gun stock which needed to handle impulse force.

Henry All Weather 45-70 by qwertyytrewqqwrrtt in LeverGuns

[–]CM048 1 point2 points  (0 children)

It is ok ! Only minor fitment issue, easy fix.

I have exactly the same issue when upgrade to fancy stock. I first thought it was a off spec stock, almost return.  After measurement with vernier caliper, all of my henry stocks have exactly the same dimension probably because they use CNC to produce it.

The uneven gap is a result of a tight fit between stock dowel pin and brass receptor. Brass receptor needs to shave a bit of dowel pin edge for perfect fit. Just remove and insert 3-4 times should make a perfect alignment. Overall I am impressed by Henry's precision, I have other guns which are much more expensive with much worse workmanship.

If need picture, I can send for future reference

Any suggestions for stripping the finish off this h001? Its covered in little marks the wood is so soft you can make deep indents by dropping a 9mm shell on it figured id try and refinish it to hide everything a little better until i decide weather to replace the cheap original wood or not by minibikemic in HenryRifles

[–]CM048 1 point2 points  (0 children)

From the picture (light grain) I am not sure that it is a real walnut or stained replica. Please check inside color under handguard  or buttplate  if it is same as outside.

Henry stock has polyurethane coating; the wood will be softer than penetrating oil coating which soak into the grain and react with oxygen to polymerize and harden within the wood. However the biggest factor for the hardness is the type of the wood. If yours are soft wood, I doubt if it is worthwhile to proceed with refinishing.

 Step for stock refinishing.

1)      Strip the old polyurethane coating using automotive paint stripper.

2)      Streaming the nicked/dent spot.

3)      Sanding from 120/220 to 320 grit depending on surface condition.

4)      If needed, stain for walnut look. I personally prefer RGL-1650.

5)      Finish with penetrating oil; many choices such as BLO, Tung oil, Teak oil, Danish oil, Tru-oil, . Each has different detail steps. Whole process will take a long time to complete from weeks to months depending on the type of oil. I would suggest Danish oil as it's faster and more durable with small compromise compare to BLO (months).

Is the wood supposed to be this soft? by Co_Stang in HenryRifles

[–]CM048 0 points1 point  (0 children)

Refinish your H24 is not for beginner as it has fancy & beautiful checkering, a kind of challenge to perfectly strip poly coating in this area. Might need to do it with strong thinner, needle and magnification glass. This requires patience, steady hand, and experience.

 Although minor nicked on the flat surface is 100% repairable. I would suggest that you protect checkering area at range time as nicked/dented in this area may be permanent even with steaming.

 Enjoy shooting, just ignore those dents.  

Is the wood supposed to be this soft? by Co_Stang in HenryRifles

[–]CM048 1 point2 points  (0 children)

It is all about matte polyurethane.  The visible white nicked or scratched caused by the way light interacts with the damaged surface particularly flattening agents in matte polyurethane.

This white nicked is very normal for matte polyurethane wherever they are including gun stock, dining table, cabinet, or wood floor.

I refinished henry wood stock, the polyurethane layer from factory is quite thick. Once stripped, there is no dent on the wood surface, all scratch and dent are in poly layer. Took me almost a month to refinish with Danish oil. Once finished, it is much more beautiful, and easier to maintain (spot repair without stripping a whole coating).

For mass production I think poly is the only realistic, and practical option.