Question / Help [SOLVED] Recording - Unspecified Error - os_process_pipe_write for info structure failed

[Doynik]

I've been having an issue with recording on OBS for a few months now. I can stream perfectly fine using the H264/ACV Encoder (AMD), no issues there.

However, when I attempt to record the session I get the fantastically unhelpful "Unspecified Error."
The log file states: "[ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for info structure failed" and then promptly stops the recording.

I've searched and searched and tried all the suggested fixes:
- Record to a different drive or folder, making sure it's a folder at the root of the drive (tried several different folders and drives, no changes)
- Run as Admin
- Ensure I've got an updated ffmpeg installed (someone fixed their error with this)
- Changing the encoder used (none of the available encoders work)

The only thing that didn't throw this error up was when changing the Video Output -> Type from Standard to Custom Output (ffmpeg). However the quality when using this setting left a lot to be desired, so I'd like to be able to used the other standard encoders.

Does anyone have any ideas? Much appreciated for any help.

Log File: https://obsproject.com/logs/FZyjHHA5W3LM0zl4

 

[Doynik]

Is there any fix for this? The ffmpeg output has started crashing OBS after a few minutes recording, so that doesn't seem to work either now.

 

[Suslik V]

Make sure that the OBS Studio is whitelisted in your security software.

 

[Suslik V]

About crashes - please, upload your crash reports here.

 

[Doynik]

Make sure that the OBS Studio is whitelisted in your security software.

I forgot to mention but I have explicitly whitelisted obs64.exe in my AV, that didn't seem to change anything either. All the folders i'm trying to record to have full permissions/aren't hidden or anything like that, just as an aside.

This is the last crash log I have, when I was recording using the Custom ffmpeg output: https://obsproject.com/logs/vU2xaSwhaaDEtqzH

 

[Doynik]

Fixed the issue! I found a fix that seems to work perfectly from this thread, with the solution posted by @fostejo.

For the lazy, I've pasted the relevant section below:

The process I followed is below and is 32-bit specific (but may work with the 64-bit version with appropriate path changes):

First... Confirm you're seeing the same issue. If not, then this may not be the solution you're looking for...

1. Fire up an administrative cmd prompt
2. CD to C:\Program Files (x86)\obs-studio\data\obs-plugins\obs-ffmpeg
3. Run ffmpeg-mux32
4. If it shows an error message about not being able to find (in my case) avcodec-57.dll then it's likely the same issue.

Update your machine's PATH variable so the OBS DLLs get found first...;

1. Right-mouse your 'My Computer' icon > Properties > Advanced System Settings > Advanced (tab) > Environment Variables... (button)
2. Select the 'Path' variable from the 'System variables' section and click the 'Edit...' button
3. (Copy and paste the current path variable detail somewhere safe just in case you need to return back to its original value)
4. In the 'Variable value' text field, jump to the beginning of the text and enter (note the semi-colon): C:\Program Files (x86)\obs-studio\bin\32bit;
5. Click ok, then ok and ok one last time to close the dialog down.

Check if that's helped ffmpeg-mux32 function correctly (or better at least);

1. Fire up a NEW administrative cmd prompt (to ensure you're using the updated path variable)
2. CD to C:\Program Files (x86)\obs-studio\data\obs-plugins\obs-ffmpeg
3. Run ffmpeg-mux32
4. Hopefully, this time, all - or most - of the required DLLs will be found by ffmpeg-mux32 and it'll just complain that there's an 'expected option missing' - If so... it should be working ok when called via OBS

Note: In my instance, it helped but wasn't 100% perfect - it then complained about the procedure entry point for deflateBound not being located in zlib.dll (presumably because if was finding a different version elsewhere). To correct that particular problem I found I had to copy OBS's specific version of zlib.dll into the obs-ffmpeg directory - even though it should've been picked up via the path variable. To do this just run copy "C:\Program Files (x86)\obs-studio\bin\32bit\zlib.dll" "C:\Program Files (x86)\obs-studio\\data\obs-plugins\obs-ffmpeg"

Everything seems to be working now, so shout out to @fostejo and @Sai_ for the hard work!

 

[Suslik V]

This rather points to the problem that you have similar dlls in the System dir or somewhere else (maybe some game/software installed them).

 

[ShanetheAmber]

Confirmed that Doynik's post works on my RX580(4GB-2048sp Ver (^ ^). Adding that path to System Environemtal variables did help ff-mpeg find avcodec-57.dll.
FYI, RX580 2048sp is a Shrinked version sold by Chinese Retailers.

Fixed the issue! I found a fix that seems to work perfectly from this thread, with the solution posted by @fostejo.

For the lazy, I've pasted the relevant section below:



Everything seems to be working now, so shout out to @fostejo and @Sai_ for the hard work!