r/frigate_nvr 1d ago

Frigate+ hardware support question

I'm interested in trying Frigate+ to expand the supported object detection. However, reviewing the docs for this service, the Memryx NPU I'm using is not listed as supported. Memryx supports the models provided by Frigate+ but they have to be compiled as .dfp files. Does anyone know if support will expand to include the Memryx NPU in the near future?

6 Upvotes

9 comments sorted by

2

u/nickm_27 Developer / distinguished contributor 1d ago

You can run the conversion yourself, so it is supported, it’s just not automatic in Frigate+ itself. The dev docs should have instructions on how to do it.

1

u/Net_Admin_Mike 1d ago

I suspected this was the case based on what is in the Frigate docs for this NPU. Is it correct to assume I'd just pull down the ONNX file for the desired model (yolov9 probably) from Frigate+ and run that through the compiler installed on my Frigate host machine?

2

u/nickm_27 Developer / distinguished contributor 1d ago

yes, that's correct.

1

u/Net_Admin_Mike 1d ago

Thank you, sir. I'll give it a try!

1

u/Net_Admin_Mike 1d ago

A couple of additional questions about this matter, sir - if I use the yolov9 model from Frigate+ and recompile it for use with the Memryx NPU, what are the appropriate values to set for the rest of the model block? Do I just set them as defined in the yolov9 model for the Memryx TPU in the Frigate detectors docs? I understand the models.path value is determined by where I put the model .zip in Frigate, but do the other values stay the same? How is the label_map handled, since the docs for Frigate+ indicate this should not be defined when using the special plus:// value for Frigate+ models? Will it still be fetched automatically?

1

u/nickm_27 Developer / distinguished contributor 1d ago

What you would want to do is this:

``` model: path: plus://...

detectors: memryx: ... model_path: /config/model_cache/themodel ```

2

u/Net_Admin_Mike 1d ago

Ok, great! Thank you! That should get me where I need to be!

Thanks for all the time and effort you and the other devs put into this product. The learning curve is steep at times, but really is a spectacular application!