You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Think I found a workaround if anyone else is stuck on this! By default, streamio-ffmpeg calls FFMPEG using the path /app/vendor/ffmpeg. For instance, a transcription request might result in the follow command:
The path /app/vendor/ffmpeg seems to be off-limits on Heroku so it throws a Permission Denied error. Instead, heroku-buildpack-ffmpeg-latest makes FFMPEG available using the plain old ffmpeg command. If streamio-ffmpeg issues the command using the ffmpeg name instead of the path, everything works. The above command would be changed to the following:
ffmpeg -y -i input.mp4 -r 60 output.mp4
Unfortunately, FFMPEG.ffmpeg_binary only allows you to specify a path to a valid binary, so FFMPEG.ffmpeg_binary = "ffmpeg" doesn't work by default. I had to create a fork that removes the valid path restriction so that you can set FFMPEG.ffmpeg_binary to ffmpeg.
I am trying to make
ffmpeg
work in heroku but without success.I think the problem is with the buildpack. I am using this one:
https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
I add it in the dashboard: https://dashboard.heroku.com/apps/name_ap/settings
Next to the heroku/ruby buildpack
When deploying, I see the builidpack used:
But I am not sure if the library
ffmpeg
is installed or if the path finds it.I checked the version of
ffprobe
and it appears to be installed:It's a Rails app (5.2.4.3), Ruby 2.5.3
The text was updated successfully, but these errors were encountered: