New NUC (NUC7i3BNH), followed the guide, tested with two different version of ffmpeg (git and release), copied over (data/Codecs), rebooted the NUC, same message. ffmpeg works on the extracted linux client so I know theres nothing wrong with the file.
I also reinstalled (clicked the button on the page), so I have the latest ROCK version (Version 1.0 (build 159) stable).
Everything else works, restored from backup etc. Just the missing codec.
Since I cant ssh in, I can’t debug this any further on my own.
Can you please let me know where you’re seeing this error and how exactly you uploaded the ffmpeg file? Have you tried rebooting the ROCK yet and verify that it is still showing this error after a reboot? Please let me know when possible.
I’m seeing that error on the ROCKS webpage (ip of the NUC).
I mounted the share in Nautilus, copied the ffmpeg binary to /data/Codecs on the share, and rebooted.
After reboot, same error about the missing codecs. So I thought there was something wrong the ffmpeg file and downloaded the other archive, extracted that and copied that ffmpeg binary over.
Rebooted, still the same error message.
I can execute the ffmpeg binary directly from the share, and it works fine.
I have gone ahead and enabled diagnostics mode for your account and what this action will do is next time your Core is active, a set of logs will automatically be generated and uploaded to our servers for analysis.
If there’s any other details you can tell us about how you’re copying the binary over, that might help us understand why you’re getting a different result than everyone else who’s set up ROCK. Are you using a Windows/Mac or Linux machine to copy this file over?
Please let me know if you can think of anything else that you’re doing different when possible.
The NUC is on right now, but I will not be home until after midnight (6h from now).
I guess you want me to reboot it so it will provide som logs on boot, so i’ll do that when I get home.
On the computer I uploaded the binary from, I use Linux (I thought that was clear when I mentioned Nautilus). More specifically Qubes OS, with Arch Linux as template. Nautilus is the filemanager in Gnome3, which I mounted the share from, and copied the binary over with. And then rebooted the NUC by clicking the button on the ROCK webpage.
What else… I use a 2.5" SSD-disk (on the NUC with ROCK), and not a NVME-disk if that matters (it should’nt).
Thanks for letting me know the additional information. I’ll let you know when we have some feedback for you based on the diagnostics but in the meantime, if you have another machine around running Windows or Mac, it might be interesting to know whether you have the same experience moving the binary into place from one of those machines.
I checked the file permission (as written in the first post), and it was/is 700. I read the other threads with people having the same problem and they didnt change the permission?
I just downloaded ffmpeg on my MacBook, copied the file to the desktop and checked permissions:
8625650151 -rwxr-xr-x@ 1 martin staff 65440616 1 Nov 05:33 ffmpeg*
So, I suggest you make sure permissions are 755 which is the default for executable files. Essentially, your file is only executed by the owner, i.e. uid 1000.
I’ve tried these steps on a setup DietPi-ROCK. And in my case file is being copied over with execution rights. Maybe this has something to do with the samba implementation on the machine you are copying from ?