Every once in a while when I try to capture the window of an app I end up getting a blank window. I don't realize it until it is too late and I missed the capture.
The reason for this is either two problems:
1. I use virtual desktops. It seems that maybe if OBS is started on one virtual desktop and the process on another it can't find the process. I can demonstrate this is the issue by running the app on VD2 and obs on VD1 then I get a blank capture. The problem is that I automate running these processes and use a utility to move the process to VD2. Usually, I guess, obs ends up starting on VD2 also 99% of the time.
2. the "window" setting doesn't do a good job understanding title differences or how ever it detects the window as compared to last time. I think it does it by process name and not title but I think I've had issues in the past with it losing track of the process and/or title. It would be much more beneficial if we could have more control(e.g., regex with variables title, process name, etc) over exactly the process information it uses to detect even so much as using a script to get that information.
For now I'm going to modify my script to try and make sure obs starts on VD2. The problem is that it starts minimized in the tray for all VD's and I'm not sure if the utility I use to move windows to different VD's will work when it is in the tray nor will OBS detect that it has changed VD's and recalculate windows pointers and such.
--
Ok, after some tests, if I move without switching to the VD, obs will not recalculate. If I move, then switch to the VD, it recalculates. All this is pointless though since the utility does not work unless obs is not in the tray.
The reason for this is either two problems:
1. I use virtual desktops. It seems that maybe if OBS is started on one virtual desktop and the process on another it can't find the process. I can demonstrate this is the issue by running the app on VD2 and obs on VD1 then I get a blank capture. The problem is that I automate running these processes and use a utility to move the process to VD2. Usually, I guess, obs ends up starting on VD2 also 99% of the time.
2. the "window" setting doesn't do a good job understanding title differences or how ever it detects the window as compared to last time. I think it does it by process name and not title but I think I've had issues in the past with it losing track of the process and/or title. It would be much more beneficial if we could have more control(e.g., regex with variables title, process name, etc) over exactly the process information it uses to detect even so much as using a script to get that information.
For now I'm going to modify my script to try and make sure obs starts on VD2. The problem is that it starts minimized in the tray for all VD's and I'm not sure if the utility I use to move windows to different VD's will work when it is in the tray nor will OBS detect that it has changed VD's and recalculate windows pointers and such.
--
Ok, after some tests, if I move without switching to the VD, obs will not recalculate. If I move, then switch to the VD, it recalculates. All this is pointless though since the utility does not work unless obs is not in the tray.