-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Av::CommandError for 0.6.4 #16
Comments
see this. it says it was fixed in |
I'm having the same problem [AV] Running command: if command -v avprobe 2>/dev/null; then echo "true"; else echo "false"; fi-v was unexpected at this time. Av::CommandError (error while running command if command -v avprobe 2>/dev/null; then echo "true"; else echo "false"; fi: Command 'if command -v avprobe 2>/dev/null; then echo "true"; else cho "false"; fi' returned 1. Expected 0 ): model.rb |
If i remove :processors => [:transcoder] the video uploads and a screenshot is shown but the video doesn't play. |
Are you running paperclip 4.2+? There seems to be an issue with |
I was using av-transcoder 0.6.3 and paperclip 4.2.1, but even after updating to av-transcoder 0.6.4 and trying paperclip 4.2.2 and going as far back as 4.0.0, I got the same thing here and here. From the paperclip NEWS file, it says they updated the custom processors in lib/paperclip, but using processors: [:transcoder] doesn't work for me. I replaced :transcoder with :ffmpeg and got this error using paperclip 4.2.2 and this error with paperclip 4.1.1 |
+1 got the same error when using transcoder as paperclip processor. Hope you could help me, thanks :) |
I am getting this same error. Has anyone come up with a fix for this? |
+1 Same. I'm receiving the error when I upload videos. Neither Paperclip nor Carrier Wave Video are allowing me to upload and show video files. |
For those who tried a lot of times but in vain. After hours of trying, It strikes me that maybe the error lies in choosing
If you use Ubuntu like me, you might at first install Finally I decide to remove
These steps work for me. Hope it works for you too. |
Im still having this issue although it was fixed with this release.
The text was updated successfully, but these errors were encountered: