OBS Studio package broken - unable to record

Hi, it appears that 1:17.0.2dmo1 of obs-studio is unable to perform
ffmpeg recordings. The problem is that the helper ffmpeg program has
been moved from it's usual location to another "lib plugins" location.
This causes the recording task to fail with an "unknown error".

From an strace:

[pid 26237] access("/usr/share/obs/obs-plugins/obs-ffmpeg/ffmpeg-mux",
F_OK) = -1 ENOENT (No such file or directory)

It looks like it defaults to "sh" if the command isn't found?!

[pid 29936] execve("/bin/sh", ["sh", "-c", "\"\"
\"/media/space/rawvids/2017-02"...], [/* 56 vars */] <unfinished ...>

This of course just errors badly, and you get some fun mystery console
output:

info: ==== Recording Start ===============================================
info: [ffmpeg muxer: 'adv_file_output'] Writing file
'/media/space/rawvids/2017-02-24T14-41-10.mp4'...
sh: 1: : Permission denied
warning: [ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for
packet data failed
info: [ffmpeg muxer: 'adv_file_output'] Output of file
'/media/space/rawvids/2017-02-24T14-41-10.mp4' stopped
info: Output 'adv_file_output': stopping
info: Output 'adv_file_output': Total encoded frames: 28
info: Output 'adv_file_output': Total drawn frames: 28
info: ==== Recording Stop ================================================

The file it's looking for is located at
/usr/lib/x86_64-linux-gnu/obs-plugins/obs-ffmpeg/ffmpeg-mux, where it
seems to have been moved by debian/rules, and is the reason I'm mailing
this list. If I link back to the original location (see above) I can now
make recordings successfully. I suspect this is a slight bug in
upstream, since that is a binary helper, and it should be in the
binaries area, but for some reason is actually shipped in the shared
(data) area and only searched for there. It's probably also a bug that
it doesn't properly sanitize this particular input.

Thanks!

Christian