Add DirectML Onnx EP as alternative GPU setup

[ev-dev]

Hey great project, I've been tweaking it to use DirectML as the onnx execution provider because I'm one of the poor suckers who doesn't have a Nvidia GPU and it works very well as an abstraction on most GPUs.

If you're interested, I'd be happy to submit my patch thru a PR, although I couldn't seem to come up with a reasonable way to avoid breaking changes to the main Yolo constructor's call signature since it's currently designed for simple disabling of GPU use but let me know if you have any suggestions/preferences in that regard.

Cheers

[uno-studio]

i am also interested in this issue. deploying cuda, cudnn to each client is difficult, so i am aiming for a simpler solution. can you give me suggestions on modifications?

[ev-dev]

@unofficialdev it's not too much effort, you can pull in the DirectML Onnx provider into the YoloCore class constructor and initialize it properly (see Onnx docs) and finally propagate any signature changes up to any of the inherited classes or invocations in the rest of the library here.

For reference, you can take a look at the open PR #38 which essentially does what I mentioned but for other Onnx execution providers.

[ev-dev]

Would be nice to hear from @NickSwardh seeing as now there are a few more people interested in using other Onnx providers like this. Merging #38 would be a good first effort if the maintainer is willing. From there I could more easily integrate DirectML as another EP option and push to new PR

[NickSwardh]

I modularized YoloDotNet in v4 in order to provide different execution providers for different environments. I'll look into DirectML and hopefully add it to the mix.

[ev-dev]

That's awesome wow I have to check out v4 ASAP! Could we possibly keep this issue open in the meantime?
Or maybe a separate issue that checklists any other potential future EPs if there are any on the roadmap