Re: Proxies not working properly with CUDA

@R Neil Haugen

I don’t disagree (read that as mostly agree also).  I'm not suggesting anything fancy for VFR support - but rather something as simple as a way to detect VFR and alert the user to go and deal with it.... and a little better, right click, and render replace without VFR.  I don’t think I would want VFR support to be built in past the 'render and replace' (on import) approach.

The costs of developing it are likely lower than the costs of addressing the problems with support - or the 'negative' aspects that people walk away with without even knowing what the core issue is with VFR.  

With that said, there are so many people using it for game recording, and OBS etc - this is a new workflow that is big enough that I think adobe needs to address with at least an alert in import - and better yet a way to convert to VFR on import.

Feels like we are at the point where we can’t hide from VFR issues as there seems to be so many valid ways to create it.  Now, I don’t use, and have never used VFR or OBS, and maybe there are ways to turn it off in OBS and force CFR - but again, if at the very least on import an alert that VFR was detected - would cause people to think about how they record next time.

Also feels like the fact that VFR has the potential to cause all sorts of other issues - Adobe would save on support costs, users would likely have less surprises too....

Feels like we are at the point we cant hide from VFR issues as there seems to be so many valid ways to create it.  Now, I dont use, and have never used VFR or OBS, and maybe there are ways to turn it off in OBS and force CFR - but again, if at the very least on import an alert that VFR was detected - would cause people to think abotu how they record next time.

Also feels like the fact that VFR has the potential to cause all sorts of other issues - Adobe would save on support costs, users would likly have less surpirses too....