Question / Help Recording shutoff questions

[BiometalOmega]

Alright, I recently updated OBS from 16.6, which I've been using ever since, for some reason, OpenGL didn't didn't appear in the renderer options of 18.9, but in doing so I've had a bit of a recurring issue with it. For some time now, on the older version, for no reason OBS would stop recording altogether, while displaying that it indeed is still successfully writing data. Does the newer version have the same issue? I'm not sure if the fact that the file reached 5gb is in any way related to this problem, but if it is then any ways of retaining a high resolution video while minimizing the file size would be very welcome.

 

[koala]

OpenGL as renderer is gone, because its performance is bad in comparison to directx. Just use directx. If you want to record a OpenGL app, you don't need OBS using OpenGL as renderer. These are 2 different things. Just use directx as renderer for OBS and run your OpenGL game and be fine.

 

[BiometalOmega]

OpenGL as renderer is gone, because its performance is bad in comparison to directx. Just use directx. If you want to record a OpenGL app, you don't need OBS using OpenGL as renderer. These are 2 different things. Just use directx as renderer for OBS and run your OpenGL game and be fine.

I do apologize, but that didn't really answer my question. I was wondering if I would have the same recording cut off issues with the newer addition of OBS. If using DirectX will fix it, then I suppose I'll grit my teeth, but in all honestly, its been lacking in the efficiency area for a long time, in my opinion. OpenGL actually was available when I installed ver21 of OBS anyway, probably thanks to the previous installation of 16.6, so for now I'll keep using it as long as it isn't the root of my issue.



Back to the question at hand. Will the newer version most likely rectify the recording cutoff issue I've bee having or not, because if it won't, then there is little point in trying to continue using OBS

 

[koala]

I'm sorry, I only answered your first question. For the second one I have no answer. I can only say that my game recordings are hour-long with 30+ GB, so no, OBS does not generally have a cutoff issue. Disk full, fat32 filesystem on destination drive, activated Tools->Output timer, virus scanner interfering?

 

[RytoEX]

If using DirectX will fix it, then I suppose I'll grit my teeth, but in all honestly, its been lacking in the efficiency area for a long time, in my opinion.

On Windows, the OpenGL renderer does not perform nearly as well as the Direct3D 11 renderer. It was removed as an available option quite some time ago because we received too many reports from Windows users with complaints about poor performance. The OpenGL renderer may still be visible as an option on installations where you had it enabled before upgrading, but it definitely does not perform better than the Direct3D 11 renderer.

As to your 5GB video file and it being cut off, please answer @koala's questions above. If those do not lead to an answer, please post a log file.

 

[BiometalOmega]

I'm sorry, I only answered your first question. For the second one I have no answer. I can only say that my game recordings are hour-long with 30+ GB, so no, OBS does not generally have a cutoff issue. Disk full, fat32 filesystem on destination drive, activated Tools->Output timer, virus scanner interfering?

My disk has over 2tb in open space, NTFS file system (W7), no output timer or hotkeys set, and no antivirus currently installed. That's why I'm so confused, honestly.


And as to the OpenGL renderer issue, I find that odd. On my previous pc, a gateway with 8gb of RAM and a Core2 Duo E5800 processor, I couldn't actually record using DirectX11, but OpenGL worked smooth. It's just kind of confusing.

 

[RytoEX]

If your system lacked proper DirectX 11 (or DirectX 10.1) support, then OpenGL may have performed better on that system. If you have a modern system with proper DX10.1/DX11 support running Windows, that will always perform better than OpenGL.

You still need to post a log file.

 

[BiometalOmega]

If your system lacked proper DirectX 11 (or DirectX 10.1) support, then OpenGL may have performed better on that system. If you have a modern system with proper DX10.1/DX11 support running Windows, that will always perform better than OpenGL.

You still need to post a log file.

Here's the log file. The only entry that worries me is one involving "capture window no longer exists. Terminating capture", so I'm assuming that's the issue, or something around it. Honestly, that makes sense in some ways, but not others, considering the target window was open for more than an hour after the capture failed, and the UI was still showing recording status. Hopefully this has been fixed by the fresh install of 21.1.2. Any other insight would be wonderful.

 

[RytoEX]

That log is from OBS Studio 0.16.6. I'd need to see a log from a current release of OBS. It's unlikely that anyone here is going to troubleshoot issues happening in any version of OBS that old, and I don't recall hearing of this particular issue. I didn't realize that you had only reproduced this issue on older versions and not the current version until I re-read this thread.

Using the OpenGL renderer on Windows also isn't really supported, as I've already sort of alluded to.

You should also be using the 64-bit OBS Studio on 64-bit Windows, unless you have a device that only works with 32-bit applications. I'm told that 32-bit OBS should be able to produce files larger 4GB (and it seemed to do so, in your case), though perhaps that is something to look into further.

22:20:06.428: [game-capture: 'Game Capture'] capture window no longer exists, terminating capture

This just means that you closed GTA5 after playing for 3 hours.

23:56:50.343: [game-capture: 'Game Capture'] capture window no longer exists, terminating capture

This just means that you closed StickFight after playing for 1.5 hours.

How are you verifying that your recordings are cut-off? Are you using a reliable media player? Are you using a 32-bit or 64-bit media player on files over 4GB?

If you ever reproduce this issue with a current release of OBS, then we can dig into it further.

 

[BiometalOmega]

That log is from OBS Studio 0.16.6. I'd need to see a log from a current release of OBS. It's unlikely that anyone here is going to troubleshoot issues happening in any version of OBS that old, and I don't recall hearing of this particular issue. I didn't realize that you had only reproduced this issue on older versions and not the current version until I re-read this thread.

Using the OpenGL renderer on Windows also isn't really supported, as I've already sort of alluded to.

You should also be using the 64-bit OBS Studio on 64-bit Windows, unless you have a device that only works with 32-bit applications. I'm told that 32-bit OBS should be able to produce files larger 4GB (and it seemed to do so, in your case), though perhaps that is something to look into further.


This just means that you closed GTA5 after playing for 3 hours.


This just means that you closed StickFight after playing for 1.5 hours.

How are you verifying that your recordings are cut-off? Are you using a reliable media player? Are you using a 32-bit or 64-bit media player on files over 4GB?

If you ever reproduce this issue with a current release of OBS, then we can dig into it further.

So far I've been using my editing software in conjunction with VLC to verify my videos' integrity, and both crash once they reach the same point during video playback, becoming unresponsive until they are terminated and restarted.

The error log I sent is from the filming session where this issue occurred last. I had 16.6 installed due to the quirks of my previous PC, even if I understand why OpenGL has been removed since that version. I did not install anything more recent (the latest release) until afterward, realizing there had been an issue in recording. I honestly have no more information in that regard, other than the fact that OBS was still trying to render to a file that had been cut off, or perhaps the UI had glitched out slightly. The fact that OBS realized what was opened and closed when it truly was makes me think perhaps this is merely a compatibility issue with Windows and the older version of OBS, and that brings me back to the question I was origanlly here to get answered, whether or not OBS 21.1.2 will possibly perform the same. So far, after testing DirectX11 is running fine, and files up to 2gb have not been an issue, but it won't be for, most likely, another week and change before anything lasts long enough to reach 5gb.



(update)


Attached is a log file from the current version of OBS, where the same issue has occurred. The Application shows that encoding is proceeding fine, yet the file has been cut off before I stopped recording. This was during Bioshock 2 gameplay, so in the end I doubt it has anything to do with a lack of rescources.
Sorry if this counts as rambling.

Also, everything is 64bit except my editor (VSDC), which I believe is 32bit.




(Second update)

I've done a full reinstall of OBS and it seems that has done the trick. Maybe it was the extra preference files from the version 16.6 I had installed previously? I'm not totally sure. Either way, everything seems to be in order now. Thanks so much for you time and patience.

 

[RytoEX]

So far I've been using my editing software in conjunction with VLC to verify my videos' integrity, and both crash once they reach the same point during video playback, becoming unresponsive until they are terminated and restarted.

Was it a 32-bit or 64-bit VLC? I know you said "everything is 64bit except my editor (VSDC), which I believe is 32bit.", but I figured I'd ask specifically to confirm this point anyway.

The fact that OBS realized what was opened and closed when it truly was makes me think perhaps this is merely a compatibility issue with Windows and the older version of OBS, and that brings me back to the question I was origanlly here to get answered, whether or not OBS 21.1.2 will possibly perform the same.

I can't really answer that question, since I don't believe I've ever heard of this specific issue occurring.

So far, after testing DirectX11 is running fine, and files up to 2gb have not been an issue, but it won't be for, most likely, another week and change before anything lasts long enough to reach 5gb.

You could probably quickly generate a large video file by recording white noise or static (or anything with constant movement in frame) with NVENC at a super high bitrate or super low CQP or with x264 at ultrafast.

Attached is a log file from the current version of OBS, where the same issue has occurred.

There's actually no successful game capture or recording session in that log. But...

I've done a full reinstall of OBS and it seems that has done the trick. Maybe it was the extra preference files from the version 16.6 I had installed previously? I'm not totally sure. Either way, everything seems to be in order now. Thanks so much for you time and patience.

Since you say that everything is working fine now, it seems to be a moot point. Glad it's working for you now!

 

[BiometalOmega]

Yeahp, 64bit VLC, don't worry.

I did like you said and recorded some mucis playing in the background on WMP with that shifting pattern deal people seem to like so much. Everything turned out fine.

And that is why I'm confused. Everything seemed like it went successfully, up until I verified the video. Doesn't make a single lick of sense, even though its passed now.

Thanks again, and sorry for the amateurish bumbling.

 

[koala]

Fine that everything works now. As a result, please take this with you:

- always use the newest software version you get. Application (OBS) and OS (Windows 10 is the current version, which you still not upgraded to; highly recommended; it's still free of charge)
- always upgrade to the newest patches in every software. Don't skip patches, never stick to older versions.
- always adapt current "best practice" at configuring software. At major software upgrades, start fresh from the default configuration to avoid keeping errors from previous configs and to avoid keeping workarounds that are not necessary any more with the new version.

Generally, newer software versions work better than older. Trust me. No need to ever keep old versions around. 10 years ago that was not always the case, but today this is the case.

Of course, you will spend more of your time to adapt to new versions, but you will not spend time any more searching for problem solutions in older versions that are fixed in new versions. What you gain is access to new features of the new version with no additional time investment.

 

[BiometalOmega]

Fine that everything works now. As a result, please take this with you:

- always use the newest software version you get. Application (OBS) and OS (Windows 10 is the current version, which you still not upgraded to; highly recommended; it's still free of charge)
- always upgrade to the newest patches in every software. Don't skip patches, never stick to older versions.
- always adapt current "best practice" at configuring software. At major software upgrades, start fresh from the default configuration to avoid keeping errors from previous configs and to avoid keeping workarounds that are not necessary any more with the new version.

Generally, newer software versions work better than older. Trust me. No need to ever keep old versions around. 10 years ago that was not always the case, but today this is the case.

Of course, you will spend more of your time to adapt to new versions, but you will not spend time any more searching for problem solutions in older versions that are fixed in new versions. What you gain is access to new features of the new version with no additional time investment.

While I agree in some areas, and I do update most of my programs, until recently that wasn' an option for me, for my computer was far below the required specs for... pretty much everything I was doing, meaning I had to shoehorn everything together just for it to function.


However, there is one thing I will not do, and that is update Windows. I do apologize, but using Microsoft products for as long as I have has instilled a special kind of hatred for them. XD

And after using W10, that means its an extra nope.

I thank you for the advice, however.