Mapleshade20
commented
1 year ago Open Mapleshade20 opened 1 year ago
Mapleshade20
commented
1 year ago Mapleshade20
commented
1 year ago 
nschurmann
commented
1 year ago I can confirm that the same happens with a MacBook 14 inch m1 max. Logs here: https://obsproject.com/logs/ob9nWeDtkL7xzwrG
willymena
commented
1 year ago Same with Windows. OBS will not close if you have an active "Source Record" filter with "replay buffer" in the filter checkmarked.
KeiBoogie
commented
4 months ago Same problem, decided to uninstall the plugin.
k0ntroversial
commented
3 months ago Having the same issue. OBS Devs say this is related to the Source Record plugin.
exeldro
commented
3 months ago Can you try if this test build fixes it for you? https://github.com/exeldro/obs-source-record/actions/runs/8489942713
k0ntroversial
commented
3 months ago Can you try if this test build fixes it for you? https://github.com/exeldro/obs-source-record/actions/runs/8489942713
Just tried it out and it doesn't seem to make OBS crash on closing. When I reopen I'm not getting the "Run OBS in Safe Mode" dialogue box either. I will update you tomorrow night after I run my stream with it active.
willymena
commented
3 months ago 2024-04-01 09-45-48.txt My pleasure!!! I very much appreciate you looking into this, as this is my most used plugin for what I do.
Unfortunately new version is not working either.
I installed a brand new clean install of OBS then installed this 0.3.3 version of Source Record (verified in control panel). I used the windows installer. I create a new source, then attach this filter to the scene. I can close and open with no problems. But as soon as I turn on a 9 second "Replay Buffer" using NVENC/H.264 or x.264, same problem exists. OBS will not close and I have to force crash it, resulting in OBS didn't shut down properly message at restart.
If I go back in and uncheck the Source Record Replay Buffer, it closes fine.
Last log (with crash/lockup) attached.
Let me know if there is anything else I can supply you.
k0ntroversial
commented
3 months ago Just wanted to update you that I am not getting the errors/crash reports anymore but the media file that is generated using Source Record is not usable. When I try to open it has a Windows Media Player error code "0xc00d36c4"
exeldro
commented
3 months ago @k0ntroversial does it play in VLC media player or in an OBS Media source?
k0ntroversial
commented
3 months ago @exeldro I tried two short recording sessions with the test build plugin and both showed as "corrupt" files and not able to be played with VLC player. I closed out of OBS and still unable to play. I then went into Task Manager to fully close the program (not sure why it's staying open in there) and once I ended the task, one of the files was able to play using Windows Media Player.
It seems the issue may be that Source Record is not allowing OBS to "fully" close down??
k0ntroversial
commented
3 months ago Source record settings:
willymena
commented
3 months ago @exeldro - will the replay buffer issue be something you'll looking into?
exeldro
commented
3 months ago @willymena I will look into all issues, but I am only able to fix issues I can replicate on my system or have a crash report for that indicates the issue. You provided an OBS log file that does not indicate what the issue is, do you maybe have an OBS crash report of the issue?
willymena
commented
3 months ago @exeldro - I apologize for any confusion caused. It seems I haven't been as helpful as I had hoped.
The issue I'm experiencing is quite easy to replicate:
I start by installing a clean version of OBS. Opening and closing the application works fine. I then add a new source (Display Capture), which also presents no problems with opening and closing. Next, I install the source-record plugin and add the source-record filter to either the scene or display source, keeping all default values. In my case, the default encoder was NVENC, H.264. This step also does not cause any issues with opening and closing OBS. However, as soon as I checkmark "Replay Buffer," any attempt to close OBS will lock it up. I have attached a file that may be helpful, as well as information from the Windows Event Viewer. Let me know if there is ANYTHING else I can supply.
=========================================== Cab Id: 0
Problem signature: P1: obs64.exe P2: 30.1.1.0 P3: 4b210561 P4: a03c P5: 134217728 P6: P7: P8: P9: P10:
Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ba18a181-aac3-4495-8e3b-ddca7b2ca042.tmp.WERInternalMetadata.xml WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240401_1_EC_0_inject.etl \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4c8e1e62-300a-4d2f-b082-b5301fbf096d.tmp.etl WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6b89ccc7-2a4f-4d3e-89b8-2c86c0d912f1.tmp.etl \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1087aa31-0793-4b22-b8cb-77ca0e21de8e.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.276e868e-bd90-414e-9eec-d41758463f63.tmp.txt \?\C:\Users\wmena\AppData\Local\Temp\WER.c6da5c06-dae3-4122-80f3-a9e3cbfecf4b.tmp.appcompat.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9a7e00d8-7d52-494e-ae7b-25fedfbe05f7.tmp.xml
These files may be available here: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_obs64.exe_2f318f3f4659bae1fc602e499735ccf66cce1f_8cf4d198_5e651435-48eb-4992-98c1-13f10f5e461f
System
[ Name] Application Hang [ Guid] {c631c3dc-c676-59e4-2db3-5c0af00f9675}
EventID 1002
Version 0
Level 2
Task 101
Opcode 0
Keywords 0x8000000000000000
[ SystemTime] 2024-04-04T11:38:12.7065950Z
EventRecordID 55605
Correlation
[ ProcessID] 11728 [ ThreadID] 4032
Channel Application
Computer WILLY-GAMING
[ UserID] S-1-5-18
EventData
Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\obs-studio\bin\64bit\obs64.exe
Problem signature Problem Event Name: AppHangB1 Application Name: obs64.exe Application Version: 30.1.1.0 Application Timestamp: 4b210561 Hang Signature: a03c Hang Type: 134217728 OS Version: 10.0.22631.2.0.0.256.48 Locale ID: 1033 Additional Hang Signature 1: a03cecdb80e23238eca98fb58db87b23 Additional Hang Signature 2: 34c4 Additional Hang Signature 3: 34c45bfa6d207d7e73caa83bda1030c3 Additional Hang Signature 4: a03c Additional Hang Signature 5: a03cecdb80e23238eca98fb58db87b23 Additional Hang Signature 6: 34c4 Additional Hang Signature 7: 34c45bfa6d207d7e73caa83bda1030c3
Extra information about the problem Bucket ID: 57d3e1c487696b465bc84b5cb5680123 (2001932895918752035)
exeldro
commented
3 months ago I was able to replicate the issue once, made a fix for that: https://github.com/exeldro/obs-source-record/actions/runs/8554754393
willymena
commented
3 months ago @exeldro - I'll keep testing, but my initial test looks good! I can't thank you enough, as I've been dealing with this issue for quite some time. Best plugin ever just got better!!!
k0ntroversial
commented
2 months ago @exeldro - I'll keep testing, but my initial test looks good! I can't thank you enough, as I've been dealing with this issue for quite some time. Best plugin ever just got better!!!
Are you still running Reply Buffer with the Source Record plugin?
willymena
commented
2 months ago @k0ntroversial, if you are asking me, depends on what "replay buffer" you're speaking of. If you mean the one built into the Source Record plugin, then yes. If you mean the one built into OBS, then no.
k0ntroversial
commented
2 months ago @k0ntroversial, if you are asking me, depends on what "replay buffer" you're speaking of. If you mean the one built into the Source Record plugin, then yes. If you mean the one built into OBS, then no.
I didn't even think about the replay buffer built into the Source Record plugin. I thought maybe there was an issue with the OBS Replay Buffer because I tried recording 2 different games and didn't have issues when closing or opening OBS but the third time I still got the crash report. How is the new beta version that exeldro released holding up? Any crashes/issues??
willymena
commented
2 months ago @k0ntroversial, so far, it's been great!
k0ntroversial
commented
2 months ago Just tried the new Source Record with no replay buffer on at all and crashed after the stream. Log file attached.
https://obsproject.com/logs/WnIdiN09emUzVmRB
@willymena what version of OBS are you running?
k0ntroversial
commented
2 months ago Also running into encoding overload now on this beta version of Source Record. Once I click the "eye" to turn off source record, my stream goes back to not missing frames.
willymena
commented
2 months ago @k0ntroversial, sorry, just saw your question. I upgraded to the latest version of OBS and all is good. Might be good in previous version also, but I did not test.
As far as missing frames, I'm actually running on a gaming laptop with an RTX 3060, so no issues here.
k0ntroversial
commented
2 months ago @willymena I'll try updating to the current OBS version, I just hate doing that because it seems like something major is always broken.
k0ntroversial
commented
2 months ago Still running into crashes everytime I close OBS. And now I can't even use the source record program because I'm getting encoder overload.
I really want to use CQP like I did for the longest time but it's bugged right now: https://github.com/exeldro/obs-source-record/issues/103
willymena
commented
2 months ago @k0ntroversial, so have you narrowed it down to what switch exactly? Can you start with a clean copy of OBS (maybe on a different machine), add the plugin and test again? What kind of machine you using? I use CBR.. no problems.
k0ntroversial
commented
2 months ago @willymena I uninstalled the Source Record plugin altogether now to narrow down that as my issue with the OBS crashes and encoding overload issues.
I updated the link in the other post. But when I chose CQP and a CQ level value and close the window, when I open it up it is showing as kbps (which is the measurement for CBR).
I have an i5-12600K and a 4070 TI Super. I never had an issue before 2 weeks ago and even before that when I was only using a 3060 TI.
k0ntroversial
commented
2 months ago Just did a 2.5 hour stream without source record installed. Zero dropped frames across the board and OBS didn't crash when I closed out of it.
k0ntroversial
commented
2 months ago Streamed Monday and Tuesday without Source Record installed in OBS and had no issues with OBS. Installed it yesterday before playing. Just recorded gameplay and after I hit stop recording and waited 2 minutes before closing OBS, it crashed. My saved source record .mp4 file appeared "unfinished" so it's unusable.
Really wish I could get this plugin to work again 😔
willymena
commented
2 months ago Save as .mkv
Get BlueMail for Android
On Apr 18, 2024, 9:06 PM, at 9:06 PM, k0ntroversial @.***> wrote:
Streamed Monday and Tuesday without Source Record installed in OBS and had no issues with OBS. Installed it yesterday before playing. Just recorded gameplay and after I hit stop recording and waited 2 minutes before closing OBS, it crashed. My saved source record .mp4 file appeared "unfinished" so it's unusable.
Really wish I could get this plugin to work again 😔
-- Reply to this email directly or view it on GitHub: https://github.com/exeldro/obs-source-record/issues/73#issuecomment-2065565861 You are receiving this because you were mentioned.
Message ID: @.***>
exeldro
commented
2 months ago @k0ntroversial was your latest test with latest version of OBS and latest version of source record? Can you provide a crash report and log file from the session with the crash?
k0ntroversial
commented
2 months ago Latest test was with version 30.1.3 of OBS and still Source Record 0.3.2.
It hasn't worked at all with version 0.3.3 and I have a lot of dropped frames when running the beta build.
I'm running a different encoder on tonight's stream and will report back in the morning if it closes successfully and the file is rendered good.
exeldro
commented
2 months ago Version 0.3.4 of source record is out please try that and provide crash report and obs log in case it's not working for you.
k0ntroversial
commented
2 months ago Hit "Stop Streaming" and the "Start Recording" didn't stop. Hit the "X" to close and gave me the warning and I hit "Close Anyway". OBS froze and had to go into task manager to close out OBS.
Crash Report: https://obsproject.com/logs/62OlOTdbti1byS09
I removed all the old 0.3.2 .dll files and installed 0.3.4.
When choosing an encoder, should you use "NVIDIA NVENC H.264" or "Hardware (NVENC, H.264)"?
exeldro
commented
2 months ago @k0ntroversial can you also provide the obs log file for the session with that crash?
"NVIDIA NVENC H.264" and "Hardware (NVENC, H.264)" should be the same.
k0ntroversial
commented
2 months ago k0ntroversial
commented
2 months ago I didn't get a crash when shutting down OBS tonight, but I did get the notification that OBS did not shut down correctly when I opened it back up.
Crash Report: https://obsproject.com/logs/CeKBJ9jKudah5kUG
k0ntroversial
commented
1 month ago I'm still having issues with a usable Source Record file after my stream is over. I assume it's because I have it set as a filter for my gameplay but start my stream on my "Starting Now" screen and also use a "Be Right Back" screen without the gameplay in the background?
Even when switching to MKV the file isn't useable
jaminmc
commented
1 month ago I'm still having issues with a usable Source Record file after my stream is over. I assume it's because I have it set as a filter for my gameplay but start my stream on my "Starting Now" screen and also use a "Be Right Back" screen without the gameplay in the background? Even when switching to MKV the file isn't useable
That is because of some bad code in 30.1.x upto the next one that will be released. If you install OBS from a newer build, it works, and you don't meed to run older 30.0.x
This is the one I am currently running: https://github.com/obsproject/obs-studio/actions/runs/9071742074 Just download OBS from the build action. IT is basically a beta of the next revision of OBS. It shows up as 30.1.0-191-gce4c99be4 on the top when I run it.