Grampa Wild Willy
New Member
I've just gotten an update to OBS. I hadn't used it in a couple of months so I'm not sure how old this update is. But I just discovered it yesterday. According to the About box, I am now on version 27.2.1 64-bit. I suppose more details are in the log files I'm going to try to attach to this post. These 2 log files are both attempts to record in a Window something from the XM Radio web site. Obviously, I am not concerned with the video component of what OBS captured. In both cases, I set the recording timer to record 4 hours. In the first log file, it looks like the recording stopped abruptly for no apparent reason after about 45 minutes. In the second, it looks like it stopped for no apparent reason after about an hour & a half. I did use timed recording with whatever release of OBS I had before this one & it worked fine. Actually, I don't think there is evidence in the log files of these problems. The log files look like, to my uneducated eye, that OBS thought it was still recording. But my files containing the recordings were both too short.
In the first case, I set it to record & went out to get groceries. I was not even home. When I came home, it appeared to still be recording but when I checked the XM web site, my program had ended. The point is, the XM web site was still streaming its content properly. So I manually stopped the OBS recording before the 4 hours were up, only to discover I had only the first 45 minutes of what I wanted. What it recorded was fine, it was just not all of what I wanted.
In the second case, I was experimenting to see whether it would work. I once again set OBS to record 4 hours of XM & went to sleep. When I got up 8 or so hours later, the OBS timer said it had 0:00:00 left to record, which is what I expected, and XM was still merrily streaming. But I noticed that the main OBS window showed that the recording was "opping." The "St" was truncated from the label inside the button in the GUI. I clicked the button & OBS appeared to stop recording then. It looked like it had tried to stop on its own but got stuck. This is also what happened in the first case. It was only at that point that I discovered my recording had actually stopped well before the 4 hours were up. Again, what was there was a good recording but it was not the entire recording I had asked for.
The .mkv file that OBS is writing into says it is of size 0 throughout the recording process. I have no good clue that it isn't recording until it's too late. I believe I am going to have to avoid the timer & just use the start & stop recording button manually to get things to work. That, of course, is subject to experimentation. I'm not sure when I'll be trying that, but if I do, I'll post about it.
Before posting this, I did search the forum for other instances of this issue & didn't find anything relevant. So maybe I'm seeing something unique to my system. Or maybe it's something others are seeing but I really am the first to report this. I don't know. I'm hoping the attached log files contain all the information necessary to diagnose this.
In the first case, I set it to record & went out to get groceries. I was not even home. When I came home, it appeared to still be recording but when I checked the XM web site, my program had ended. The point is, the XM web site was still streaming its content properly. So I manually stopped the OBS recording before the 4 hours were up, only to discover I had only the first 45 minutes of what I wanted. What it recorded was fine, it was just not all of what I wanted.
In the second case, I was experimenting to see whether it would work. I once again set OBS to record 4 hours of XM & went to sleep. When I got up 8 or so hours later, the OBS timer said it had 0:00:00 left to record, which is what I expected, and XM was still merrily streaming. But I noticed that the main OBS window showed that the recording was "opping." The "St" was truncated from the label inside the button in the GUI. I clicked the button & OBS appeared to stop recording then. It looked like it had tried to stop on its own but got stuck. This is also what happened in the first case. It was only at that point that I discovered my recording had actually stopped well before the 4 hours were up. Again, what was there was a good recording but it was not the entire recording I had asked for.
The .mkv file that OBS is writing into says it is of size 0 throughout the recording process. I have no good clue that it isn't recording until it's too late. I believe I am going to have to avoid the timer & just use the start & stop recording button manually to get things to work. That, of course, is subject to experimentation. I'm not sure when I'll be trying that, but if I do, I'll post about it.
Before posting this, I did search the forum for other instances of this issue & didn't find anything relevant. So maybe I'm seeing something unique to my system. Or maybe it's something others are seeing but I really am the first to report this. I don't know. I'm hoping the attached log files contain all the information necessary to diagnose this.