question about VTdecoderservice, FCPX and eGPU

Hi all,

Apologies if this is in the wrong place.
I am running Final cut on a 2016 MacBook Pro ( Mac OS 15.5.5) alongside with an eGPU (razer Core xx with an AMD 5700xt)

When I updated to 15.5.5 the eGPU setup worked perfectly, cutting through H.265 like butter and transcoding using the eGPU rather than the cpu, this could be seen not only the MacBook's fans not kicking off but in activity monitor the eGPU would be using VTdecocderservice.

Then I took a lunch break, came back and this was no longer the case, the VTdecoderservice was being done by the cpu instead and the footage was unplayable (no T2 in MacBook Pro) The eGPU still worked for rendering but was obviously not as fully as before (the eGPU was recognised by Mac OS and Final Cut)

I then updated to the 15.5.5 patch and again It worked flawlessly as expected but stopped for the night and next day the same again.

Was it a glitch in the first place that VTDecoderservice was offloaded to the eGPU and it corrected itself?
or (I'm hoping) theres a way to kickstart final cut to exploit the eGPU (or vice versa) again and save me from having to buy a T2 Mac just to work with H.265.

Yes, I can transcode to Prores 422 (and I am, well to proxy) but I have my reasons to want to H.265 to work, for time efficiency, drive space, especially when juggling multiple projects.

Thanks

Hey man! I have an almost exactly identical system, and wondering the same thing. Have you made any progress on this problem? Very curious.