By Kirill Pilipenko on Saturday, 03 March 2018
Posted in Technical Issues
Likes 0
Views 715
Votes 0
Hello guys, so there is a feature to download your own video into the EasySocial. It's always been processed with FFmpeg library.
It's been processing forever and never ends.
I tried to solve it on my own. After some research, I find out that you need FFmpeg support on your hosting. So I reached them out and they change subscriber plan for me to one that supports this. Also, they gave me a correct path to FFmpeg.
But unfortunately, it's still not working. At this point, I need your help.
Hi there,

Seems like one of our issues hit same issues like yours facing right now as you can see here https://stackideas.com/forums/video-upload-isn-t-working#reply-398635 . On that post, there are also steps on how to solve this issues on your server end. Please give it a try and see how it goes.

We suspected that your ffmpeg didn't install/compile this libx264 library yet and that why you hitting this error on your end. It is required for you to install/compile libx264 library because Easysocial required video encoding in order to encode/convert your uploaded videos into more high-quality video

By the way, this actually beyond of our support scope, by right your web hosting service provider should assist you regarding this issues.

If your web hosting service provider still unable to solve this based on the steps prompted here https://trac.ffmpeg.org/wiki/CompilationGuide/Centos , perhaps you can pass us your SSH access so we can better have a look on this issues and please remember to do full backup on your site first.

Please advice.

EDITED
·
Tuesday, 06 March 2018 16:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Logs from one of the video, hope it will help

ffmpeg version 3.4.2 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-18)
configuration:
libavutil 55. 78.100 / 55. 78.100
libavcodec 57.107.100 / 57.107.100
libavformat 57. 83.100 / 57. 83.100
libavdevice 57. 10.100 / 57. 10.100
libavfilter 6.107.100 / 6.107.100
libswscale 4. 8.100 / 4. 8.100
libswresample 2. 9.100 / 2. 9.100
Unrecognized option 'crf'.
Error splitting the argument list: Option not found
·
Saturday, 03 March 2018 04:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Kirill,

It looks like the version that you are using is unsupported. Could you get your host to install the 2.8.x version of ffmpeg?
·
Saturday, 03 March 2018 15:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark. It was hard to get them to do it. But finally, they helped me... And it's not working again =_=

Hosting answer :We have downgraded ffmpeg to version 2.8.14:

$ ffmpeg -version
ffmpeg version 2.8.14 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-18)
configuration:
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101


New Error log


:ffmpeg version 2.8.14 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-18)
configuration:
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
Unrecognized option 'crf'.
Error splitting the argument list: Option not found
·
Sunday, 04 March 2018 12:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Kirill,

I am really sorry for the delay of this reply as it is a weekend for us here. Is it possible for you to provide us with the back end and FTP access to your site to check on this issue? You may store your site access at http://stackideas.com/dashboard/site so you don't have to provide these information all the time
·
Sunday, 04 March 2018 17:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark, Done, you have access to FTP and admin panel. (http://stackideas.com/dashboard/site)
·
Monday, 05 March 2018 00:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

It seems that it already stated that you hit "Unrecognized option 'crf'." error on your logs. It is required for you to consult with them regarding this. I have done some searching on the internet and found out that, it required for you to recompile ffmpeg as listed below.

you need to recompile ffmpeg with options like this (debian version):

--enable-gpl --enable-libass --enable-libfaac --enable-libfdk-aac
--enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis
--enable-libvpx --enable-libx264 --enable-nonfree

crf is x264 option and you don't have it enabled


https://mail-archives.apache.org/mod_mbox/openmeetings-user/201404.mbox/%3CDUB126-DS18E6745B74FA857F6AA0DAC9680@phx.gbl%3E
·
Monday, 05 March 2018 11:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear abdul. Bellow is answer from the hosting. Please fix this problem!!. If you need access to server - I'll give to you.


Please reach your developer and further let him know that your server is built on top of the CentOS core, not Debian, thereby the installation is a bit different from the ordinary one. These options can't be enabled due to a discrepancy between the Kernel of the server and the libraries like libass or libfaaac.

I have tried to install some of these dependencies manually, however, some of them are already deprecated thereby we can't install them. Since you have root access to the server, the best option for you is to provide it further to your developer so he could work around the errors and possibly to configure ffmpeg with the desired extensions or to find up to date ones, that could be used for replacement of the legacy ones.
·
Monday, 05 March 2018 23:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Abdul, Thank you so much for the link ( https://trac.ffmpeg.org/wiki/CompilationGuide/Centos)
As soon as I gave it to them - they fixed everything.
My task solved.

·
Wednesday, 07 March 2018 00:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Kirill, glad that your issue is resolved now
·
Wednesday, 07 March 2018 00:48
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post