Errno::ENOENT, No such file or directory - ffmpeg -i path_public/uploads/tmp/1414501164-5614-4315/video1.mp4 , Error while uploading File.

[kranthi1027]

Hi,
Before I ask anythink I just want to say I'm very new to rails.
I'm building an application where users can upload a video. Using carrierwave i could upload the video successfully but html5 video tag doeant work for all video formats. On looking around I found this gem. I followed the instructions but I'm getting the following error.

Errno::ENOENT in VideosController#create
No such file or directory - ffmpeg -i path_public/uploads/tmp/1414501164-5614-4315/video1.mp4

I don't know what is going wrong.

My storage path is the default path given by carrierwave which is
"uploads/#{model.class.to_s.underscore}/#{mounted_as}/#{model.id}"

but I don't know why it is looking for a path_public/uploads/tmp/1414501164-5614-4315/video1.mp4.

Can someone please help me?

[swaathi]

I'm facing the same issue. Did you resolve this?

[rheaton]

I have not tested this library out with Rails 4, so that could be the issue. :-/

[kranthi1027]

No I haven't solved it. I'm restricted users to upload only mp4 format for now.

[komochi]

I'v the same problem in my test environment.
In my case this problem occurs on my tablet Windows8.1 PC, but it's working well on my Windows7 PC for the same Rails program although the screenshot is black.
I don't understand about the difference between these.
On Windows8.1 tablet, I found some temporary video files and screenshots (jpg) that were created on public\uploads\tmp folder by my some trials.
The access securities of such folders seem to same as Windows7 PC.
It seems to not depend on the file types MP4 or wmv.

[debborafernandess]

Did you tried add a ''/" in the begin of the url on store_dir?
Like that: "/uploads/#{model.class.to_s.underscore}/#{mounted_as}/#{model.id}"

I think that could be the reason, works to me..

[d4rky-pl]

This sounds more like an issue with ffmpeg path rather than anything with the uploader. If it is - make sure you have ffmpeg installed on your machine. Check where it is (which ffmpeg in terminal). Create an initializer (config/initializers/ffmpeg.rb) and set FFMPEG.ffmpeg_binary to right path.

[ahmed-sharief5]

Hi. Can someone help me to resolve this issue https://stackoverflow.com/questions/51946375/ffmpeg-for-aws-s3-bucket-signed-url-not-working-in-node-js

[d4rky-pl]

@ahmed-sharief5 this is a Ruby library

[jimmy-owoa]

This sounds more like an issue with ffmpeg path rather than anything with the uploader. If it is - make sure you have ffmpeg installed on your machine. Check where it is (which ffmpeg in terminal). Create an initializer (config/initializers/ffmpeg.rb) and set FFMPEG.ffmpeg_binary to right path.

This solved my problem!