Re: Proxies not working properly with CUDA

When you are coding effects at the level that Premiere does, you can't compare to the prosumer stuff. Even though a couple of them now have a few pretty spiffy/splashy things they do, everything that Premiere does would have to be set for the odd processing involved in VFR.

And VFR is a capture thing ... it cuts down on the frames needed to be encoded to the file, just like the long-GOP process cuts down on the pixel data being encoded to file. And in both cases, the playback device then does a ton more work to make it not obvious.

So ... can it be done? I would expect it could. But the next question ... given everything else that people want Premiere to start doing, and the constant upgrading to work with newer hardware, dump code for older not-used hardware, all that constant never ending process ... priorities are needed.

And would handling VFR better take precedence over 55 or 60 other things? For some users, yes, of course. For the majority of the user base ... maybe not so much. 

It's rather like a lot of the upper-end colorist stuff I would like to get in Premiere. Yes, the devs know that for a few of their users like me, it would be an awesome addition. But the vast majority of their users, they'd never use it ... so ... I've been told it wouldn't be wise to hold my breath even for something really awesome for some higher-end workflows.

As a long-time self-employed business person, I had to make a lot of decisions I did not like making at all. But the data were clear, and I needed to make changes at times dropping a photo style I loved doing. For instance. But things change all the time.

So ... maybe at some point, VFR would be a natural fit and welcomed by enough users to be worth the major effort it would take to fully support it 'natively'.