Source Record stops creating files when switching to the hardware encoder

Just_Cyril

New Member
Hello!

I use OBS 30.1.2 with Source Record 0.3.4 to record videos from multiple USB cameras. I need to have the original video files, that's why I use Source Record.
If I use the software encoder, everything works fine: all the files are created, but the CPU load is crazy if I want to use all the cameras. When I select the hardware encoder for some cameras (in the attached example it was Cam1), OBS stops creating video files for them.

I tried to google the solution and had a quick look through the forum, but did not find what I was missing. Pretty sure everything is fine with the folder and other typical mistakes as the videos appear on the software encoder without any troubles.

I have attached a few files if they help to spot the problem:
- log file (at 18:21:34.601 I started the recording when the hardware encoder was selected for Cam 1; at 18:22:00.622 I started the recording when the software encoder was selected for Cam 1).
- Folder.png (the files in the folder for both recordings)
- Source_Record_settings.png (all parameres I set in the source record settings)
- Encoder_choice.png (the list of possible encoders to choose. I tried the software, hardware, AMD HW H.264 and x264. Not sure what SVT and AOM mean. The software one worked, other options I tried did not work)
- Hardware_encoder_parameters.png (parameters suggested by OBS in case I should choose something there that I did not choose before).

Thank you in advance for any advice!
 

Attachments

  • OBS_log.txt
    23.8 KB · Views: 7
  • Encoder_choice.png
    Encoder_choice.png
    9.5 KB · Views: 8
  • Folder.png
    Folder.png
    86.1 KB · Views: 8
  • Hardware_encoder_parameters.png
    Hardware_encoder_parameters.png
    16.3 KB · Views: 8
  • Source_Record_settings.png
    Source_Record_settings.png
    44 KB · Views: 7

rockbottom

Active Member
Your GPU is overloaded, lots of rendering lag to overcome. Anyway, here's your AMF encoding error.

18:21:34.749: [ffmpeg muxer: 'Source Record'] Writing file 'C:\Users\miski01p\Videos/2024-05-13 18-21-34 Cam3.mkv'...
18:21:34.775: [texture-amf-h264: 'Source Record'] amf_encode_tex: SubmitInput failed: AMF_INVALID_RESOLUTION
18:21:34.775: Error encoding with encoder 'Source Record'
 

rockbottom

Active Member
GPU is long in the tooth (2012) & the installed driver is close to 4 years old. I'm not sure how much traction you're going to get using the latest version of OBS as it works best with new(er) hardware. Thinking the last version of OBS v27 might be a better option.

Some food for thought. k variant CPU but the iGPU is not enabled. It will more than likely encode better than the GPU & since it's Gen 8, it's still supported by the current version of OBS. Depending on mobo, you may be able to enable it in BIOS. Should be good for at least (2) encodes, maybe 3 if the settings are done correctly.
 
Last edited:

Just_Cyril

New Member
Your GPU is overloaded, lots of rendering lag to overcome. Anyway, here's your AMF encoding error.

18:21:34.749: [ffmpeg muxer: 'Source Record'] Writing file 'C:\Users\miski01p\Videos/2024-05-13 18-21-34 Cam3.mkv'...
18:21:34.775: [texture-amf-h264: 'Source Record'] amf_encode_tex: SubmitInput failed: AMF_INVALID_RESOLUTION
18:21:34.775: Error encoding with encoder 'Source Record'

Thank you for spotting it! Now I know where I should look at.
I guess I will play with the resolution settings and it should fix the issue (at least I will be checking the response in the log file)

GPU is long in the tooth (2012) & the installed driver is close to 4 years old. I'm not sure how much traction you're going to get using the latest version of OBS as it works best with new(er) hardware. Thinking the last version of OBS v27 might be a better option.

Some food for thought. k variant CPU but the iGPU is not enabled. It will more than likely encode better than the GPU & since it's Gen 8, it's still supported by the current version of OBS. Depending on mobo, you may be able to enable it in BIOS. Should be good for at least (2) encodes, maybe 3 if the settings are done correctly.
Thank you, I may try v27. Just started with whatever was the latest ¯\_(ツ)_/¯

Could you give me a little bit more guidance re. the second part of this message you wrote? So, I should be able to turn on... iGPU (I suspect, the GPU core in the CPU I have). Could the AMD graphic card be the reason iGPU is off now? And, once it's on I should be able to see it in the list of encoders, correct? Thank you in advance! I will check, what I can do with it.
 

rockbottom

Active Member
2592x1944 was in play on the camera sources. See how it goes with them @ 1920x1080.
Might need to step down to 30fps or 720/60 if there still rendering lag.

Maybe, if your mobo supports it. The owners manual or BIOS manual should be available on the manufacturers support page. If you're able to enable it, update the driver (2/1/24) & the QSV encoder(s) will be available.

 

Just_Cyril

New Member
2592x1944 was in play on the camera sources. See how it goes with them @ 1920x1080.
Might need to step down to 30fps or 720/60 if there still rendering lag.

Maybe, if your mobo supports it. The owners manual or BIOS manual should be available on the manufacturers support page. If you're able to enable it, update the driver (2/1/24) & the QSV encoder(s) will be available.


Thank you very much!

Firstly, I fixed the resolution problem by setting the source resolution (I thought it would pick it up from the camera as was set by the settings, but no...). Then I turned on the iGPU and managed to run almost all the cameras I wanted (now I need more USBs haha!). Though I had to drop down the quality to 720p and 30 FPS (which is more than enough for me right now). As you noted, QSV appeared in the list of encoders and it is, indeed, much more powerful than the AMD one (why this computer has an AMD card in this case?.. rhetorical question, it is a work computer).

Thank you again for your help and advice!
 
Top