OBS v29 suddenly not hooking process for recording?

ClutchDCS

New Member
Log file (hella long): https://obsproject.com/logs/8nsmhtznNkAxSBnq

After switching to mkv format I went at least a year without running into that "stopping recording" issue, but ran into it today. Looking through the log file I see a lot of instances where it appears to be unable to hook the process I'm trying to record (DCS.exe), but I don't know what is really going on. In the log file you can see that from noon to 14:20 I was able to record things fine. I did some editing, took a break from the computer for a bit, came back at 19:50 to do some more recording, where you see the "attempting to hook process" entries. The red recording badge was on OBS and it was stuck on "stopping recording" yet it recorded no files at all. What would cause the software to stop working a few hours after working normally?
 

PaiSand

Active Member
All the recording attemps stop due to 14:09:17.148: Stopping recording due to hotkey
Check if the hotkey is set correctly or change it to something else and apply it again to the one your using now.

You may want to check the analyzer:

It's adviced to use CQP instead of CBR for recording.
Do not set so many different capture methods on one single scene. Monitor capture must be on it's own scene. In this case it's adviced to create one scene for each game you want to play, so the capture of this game don't mess with the other game captures.
 

rockbottom

Active Member
Base Resolution (1440p) is wrong, should be 2160p or 1080p

No wonder it won't hook, your Scene is a mess, needs to be fixed & there's a sample rate mis-match too.
- scene 'Scene':
12:51:48.019: - source: 'OpenVR Capture' (openvr_capture)
12:51:48.019: - source: 'Display Capture' (monitor_capture)
12:51:48.019: - source: 'SteamVR' (game_capture)
12:51:48.019: - source: 'Window Capture' (window_capture)
12:51:48.019: - source: 'DCS 2D' (game_capture)
12:51:48.019: - source: 'FS2020' (game_capture)
12:51:48.019: - source: 'DCS VR Wide' (game_capture)
12:51:48.019: - source: 'LifeCam' (dshow_input)
12:51:48.019: - source: 'VB Cable' (wasapi_input_capture)
12:51:48.019: ------------------------------------------------
12:51:48.022: WASAPI: Device 'CABLE Output (VB-Audio Virtual Cable)' [44100 Hz] initialized
12:51:48.604: WASAPI: Device 'Headset Microphone (Oculus Virtual Audio Device)' [48000 Hz] initialized
12:51:48.635: adding 21 milliseconds of audio buffering, total audio buffering is now 21 milliseconds (source: Mic/Aux)
 

ClutchDCS

New Member
Strange that it suddenly has problems after a year of working fine.
All the recording attemps stop due to 14:09:17.148: Stopping recording due to hotkey
That was when recording worked fine. The issues started at timestamp 19:50:22.102.
In this case it's adviced to create one scene for each game you want to play, so the capture of this game don't mess with the other game captures.
I only enable one source at a time. Do the other sources in the scene interfere even when off?
Base Resolution (1440p) is wrong, should be 2160p or 1080p
For VR capture, 2160p gives too wide FOV where nothing can be clearly seen, and 1080p gives too narrow FOV where you're looking through a soda straw. 1440p gives best FOV for VR capture in my games.
No wonder it won't hook
It hooked fine between 12:51 and 14:12, and a gazillion times before that for the past year *shrugs*
 

PaiSand

Active Member
I only enable one source at a time. Do the other sources in the scene interfere even when off?
Yes, that's why in the analyzer says so.
If you need to change the output resolution for different games, like you mention on the VR, make a separate profile for it. You can use the same scene collection on different profiles.
 
Top