- Device model: MacBook Pro 15" 2017
- Version of operating system: macOS 13.7.6
- Version of djay: 5.3.2
Your question:
I have a question, is the Djay pro application able to work on a dedicated graphics card? At the moment, even with the setting: prefer external eGPU, the application loads the integrated graphics card. If there was a possibility to work using a dedicated graphics card, it would significantly reduce the CPU usage.
Could you include this fix in the new update? Is it not possible for the application to work on a dedicated graphics card?
Thank you in advance for your answer
1 Like
Hi @mystamef, welcome to the Community! I checked with our engineering team and we do not have support for selecting the graphics card for rendering.
Okay, but I didn’t mean exactly only rendering and choosing a graphics card in the application settings.
The djay pro application processes the display of the interface on the integrated processor. So the graphics card integrated with the processor is responsible for the appearance of the interface and displaying it on the screen.
Most applications on mac OS have the option of forcing the launch on an external eGPU. Many graphic applications, but also Final Cut Pro, or even applications such as a web browser. For them, there is the option of forcing work on the eGPU.
Maybe it would be possible to do something along these lines towards the possibility of working on the eGPU. I will add that this would be a developmental convenience, on the one hand for users of older laptop models, but also for professionals who use external graphics processors for vjaying.
I guess it’s a rather complicated process of adapting to using egpu, but maybe you’ll find that you can handle it very quickly 
I’ll add that the application itself running on my device already generates a large load on the CPU, and when playing music, the integrated processor is loaded 100%.
An external GPU could also speed up the operation of AI algorithms.
This is the CPU usage the app generates when I’m not playing.
Thanks for the additional clarification and info @mystamef. I will pass this onto our engineering and development team for consideration.
