Tux Prowess
New Member
The NVidia made profile can mess with game hooks, the browser's functionality, and any source that practically uses hardware acceleration. It either doesn't work or crawls on its feet when it does.
Anything I attempt to do to change the encoder to either Intel QuickSync or AMD's encoder is saved in the profile, but OBS is so stubborn on detecting NVENC, even when it is not the selected encoder, that I have to create a fresh profile to get it to encode properly at all. Even when switching to the AMD profile from the NVidia profile, OBS will not correct itself to the proper GPU acceleration until it is closed and restarted.
It is one of those sandy edge cases. I did not consider the program to be this level of dependent on a specific driver. I just copied the information I needed to transfer my streaming profile and scenes into a new computer. Everything on my technical side has already been resolved, but the bugs and "clingy driver dependency per profile" itself are not.
Anything I attempt to do to change the encoder to either Intel QuickSync or AMD's encoder is saved in the profile, but OBS is so stubborn on detecting NVENC, even when it is not the selected encoder, that I have to create a fresh profile to get it to encode properly at all. Even when switching to the AMD profile from the NVidia profile, OBS will not correct itself to the proper GPU acceleration until it is closed and restarted.
It is one of those sandy edge cases. I did not consider the program to be this level of dependent on a specific driver. I just copied the information I needed to transfer my streaming profile and scenes into a new computer. Everything on my technical side has already been resolved, but the bugs and "clingy driver dependency per profile" itself are not.