Question / Help Obs not installing files?

[naseem002]

I don't know much but all I know is when I try and run obs it gives me msg's such as MSVCR120.dll is missing from your computer try reinstalling the program to fix this problem it also happens for these as well:

avcodec-57.dll

avutil-55.dll

MSVCR120.dll

avformat-57.dll
(I'm running windows 10)
Thanks for the help

 

[Harold]

Reinstall the visual studio 2013 runtimes
http://www.microsoft.com/en-us/download/details.aspx?id=40784

 

[naseem002]

Thanks, I've installed it and tried to run it although this doesn't seem to work with windows ten

 

[Harold]

The installers (X86 and X64) work fine with windows 10.

 

[naseem002]

Oh thanks I installed the wrong thing Works thank you a lot!!!

 

[naseem002]

avcodec-57.dll

avutil-55.dll

avformat-57.dll
Are still not working although my other problem was solved anyway to fix this?

 

[Pinky]

This is the exact same problem I am having, the same 3 files also.

 

[RytoEX]

@naseem002
Does OBS still start after those warnings? Are you, or were you, running the AMD AMF encoder? Are there any log files produced by OBS during this error (check "%AppData%\obs-studio\logs" manually, if OBS is not starting)?

 

[Pinky]

@naseem002
Does OBS still start after those warnings? Are you, or were you, running the AMD AMF encoder? Are there any log files produced by OBS during this error (check "%AppData%\obs-studio\logs" manually, if OBS is not starting)?

I'm having the same issue, same error about the same 3 files. I checked and the files are installed in the obs dir correctly.

I've attached some logs and this entry jumps out at me:

14:06:26.338: [ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for packet data failed

For info, obs has been working fine but I recently upgraded obs and amf plugin to latest version.

 

[RytoEX]

@Pinky
Have you tried temporarily disabling your security software (antivirus)?

Beyond that, the only suggestion I have at this point is to uninstall OBS, and then restart. After restart, make sure the install directory is completely empty (or non-existent), and then run the 0.16.4 full installer, and try again after that.

I don't think it's related to the AMD AMF plugin, but I've asked the author anyway.

 

[Pinky]

@Pinky
Have you tried temporarily disabling your security software (antivirus)?

Beyond that, the only suggestion I have at this point is to uninstall OBS, and then restart. After restart, make sure the install directory is completely empty (or non-existent), and then run the 0.16.4 full installer, and try again after that.

I don't think it's related to the AMD AMF plugin, but I've asked the author anyway.

Disabled windows defender, same issue.

Uninstall, restart, check folders, reinstall.

Initially the recorder worked on the AMF presets until I enabled opencl then the error started happening again.

Now the error keeps happening even though opencl is disabled, and even on presets that were working just a moment ago :/

Still seeing this in the logs:

15:24:42.996: [ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for info structure failed

I have attached the full log which shows recording working for the first 3 or so attempts, with slight changes to settings and then it stops working. Maybe someone can see which setting I changed that is causing the issue?

 

[Pinky]

I see this too in the log:

15:23:01.270: [AMFDeviceDX11Impl] Debug: InitDX11() created HW DX11.1 device
15:23:01.270: [AMFDeviceDX11Impl] Debug: InitDX11() created HW DX11 device
15:23:01.270: [CLWrapper] Trace: Release:: FreeLibrary opencl.dll successed
15:23:01.270: [CLWrapper] Trace: Init:: LoadLibrary opencl.dll successed
15:23:01.270: [CLWrapper] Trace: Load function clSetPrintfCallback failed
15:23:01.270: [CLWrapper] Trace: Load function clSetImageFormatAMD failed
15:23:01.270: [CLWrapper] Trace: Load function clCreateImageTiledAMD failed
15:23:01.270: [CLWrapper] Trace: Load function clSetThreadTraceBuffersAMD failed

 

[Xaymar]

I suggest a clean reinstall of your AMD driver, as the issue is still not with the encoder. You're looking at debug output that isn't even related.

 

[RytoEX]

I've seen those errors, and I've brought them up to the AMD AMF encoder author. The whole thing doesn't make sense to either of us.

Does it still warn you about those three files originally mentioned?

Does the breakage persist across OBS sessions (shut down OBS, reopen OBS)? What about system restarts? Can you reproduce the breakage every time by toggling just the OpenCL setting?


Edit:
Cross-posted with @Xaymar, the author in question. Try his advice.

 

[Pinky]

Thing is, yesterday I had 16.11.1 driver installed and today I installed 16.11.2 so have already covered that step. I always use DDU during my driver upgrades.

And no, it has actually stopped warning me about the 3 files, though the rest of the symptoms have remained.

I will check if the issues persist across sessions and system restarts and report back.

 

[RytoEX]

I recall reading once that DDU with AMD drivers can sometimes produce unexpected results. @Xaymar would know more on that.

 

[Xaymar]

DDU had a few versions where it wouldn't remove all files and leave "leftovers" around that Windows would use. Also there's Windows Update that immediately downloads the "latest" driver if it wasn't disabled.

 

[Pinky]

I'm on the latest DDU and I have the windows update disabled so that it doesn't do that.

So had another look, set to 'Recording' preset with all default settings and recording was working, so I changed the following settings one at a time and tested:

Memory Type changed from Host to DX11 - Recording still worked
Device change from Default to be my Fury GPU - Recording still worked
OpenCL changed from disabled to enabled - Recording failed, 3 error pop ups for those files appear.

So I changed OpenCL back to disabled but recording still failed.

Restarted Obs without changing any settings (OpenCL disabled) - recording was successful (nice!!)

OpenCL enabled again, recording fails repeatedly.

Disabled OpenCL - Recording fails

Restarted Obs - Recording successful

I feel like we are getting somewhere now, just not sure where :)

 

[Xaymar]

Well the obvious solution is "don't use OpenCL" for you. The reason why is probably that your system is somehow broken enough that using the opencl runtime somehow makes other dlls fail - for whatever reason that happens.

 

[Pinky]

Well the obvious solution is "don't use OpenCL" for you. The reason why is probably that your system is somehow broken enough that using the opencl runtime somehow makes other dlls fail - for whatever reason that happens.

Not ideal though really.

I noticed in the logs from earlier that opencl is enabled by default in some of them and recording seemed to work? Seems to cause problems when I manually fiddle with it.

In fact I put the preset back to 'default', and recording worked. Looked in the log and opencl is enabled.