Which version of FFmpeg.AutoGen should I use? - ffmpeg

I'm trying to use FFMediaToolkit library which uses FFmpeg.AutoGen.
And I encountered an error Invalid data found when processing input when calling ffmpeg.avformat_open_input this line. I tried run in windows & ubuntu using the latest version ffmpeg, it works fine.
But when I run in Nvidia Jetson, it throws error. I tried to figure out the issue and MABYE it is because of the mismatch version of installed ffmpeg and FFmpeg.AutoGen. But somehow, I can't update the ffmpeg in jetson.
Here the libraries inside '/usr/lib/aarch64-linux-gnu`:
libavcodec.so.57
libavcodec.so.57.107.100
libavdevice.so.57
libavdevice.so.57.10.100
libavfilter.so.6
libavfilter.so.6.107.100
libavformat.so.57
libavformat.so.57.83.100
libavresample.so.3
libavresample.so.3.7.0
libavutil.so.55
libavutil.so.55.78.10
Anyone know which version of FFmpeg.AutoGen should I use?
Or as alternative, how to get the latest version of ffmpeg for Nvidia Jetson Nano?
Thanks,

Why can't you update FFmpeg in Jetson? That's the proper solution. FFmpeg.AutoGen has so far done a good job at keeping up to date with the FFmpeg releases. So just get the newest release of FFmpeg and the latest code from FFmpeg.AutoGen.
libavcodec.so.57.107.100 corresponds with FFmpeg 3.4.8 (as shown by FFmpeg Download) which is from 2017-10. If you can't update your FFmpeg then use FFmpeg.AutoGen from commit f1fa4ed: Update to 3.4. Unfortunately, you'll be missing out on 3.5 years of FFmpeg development.

Related

Installation of gstreamer bad plugins and opencv3.3 on Ubuntu 16.04 arm64

I have been working on some video playing/streaming pipelines for Computer Vision work on Nvidia Jetson TX2. It had Ubuntu 16.04 with latest Jetpack.
I have already installed opencv 3.3 and to test some of the pipelines, with .MP$ video files, I need h264parse plugin which is a part of gst-bad-plugins. However, when I try to install it using apt-get, it shows that following packages will be installed:
freepats gstreamer1.0-plugins-bad-faad gstreamer1.0-plugins-bad-videoparsers
libbs2b0 libde265-0 libflite1 libfluidsynth1 libgstreamer-plugins-bad1.0-0
libmimic0 libmjpegutils-2.1-0 libmms0 libmpeg2encpp-2.1-0 libmplex2-2.1-0
libofa0 libopenal-data libopenal1 libopencv-calib3d2.4v5
libopencv-contrib2.4v5 libopencv-core2.4v5 libopencv-features2d2.4v5
libopencv-flann2.4v5 libopencv-highgui2.4v5 libopencv-imgproc2.4v5
libopencv-legacy2.4v5 libopencv-ml2.4v5 libopencv-objdetect2.4v5
libopencv-video2.4v5 libsoundtouch1 libspandsp2 libsrtp0 libvo-aacenc0
libvo-amrwbenc0 libwildmidi-config libwildmidi1 libzbar0
Here it tries to install an older version of opencv and this really messes up with my current opencv (v3.3) install.
Does anyone have any idea on how should I overcome this problem. I would not want the option to just ignore all the dependencies. But somehow, if it detects the installed opencv version, that would be awesome.
Any help is appreciated.
Thanks!
I am working on Jetson Tx1 , and have problem installing opencv 3.3 in virtual environment onto it due to space issues. I tried to compile the build file from external sd card and make from there. Then Sym-link (cv2.so) file to appropriate path. Can you tell me how you were able to install opencv3.3 ??

pebble-clay says my project is outdated, but it's not

I just updated the sdk to 4.1.4 and trying to install clay from command line I get the following message:
This projected is outdated (try 'pebble convert-project' or'pebble sdk install 2.9')
Now, I am not going to install the 2.9 sdk, of course, and I know that convert is just going to change appinfo.json into pakage.json, which I don't need to do because I am already on sdk 4.1.4.
Has anybody here had the same issue, how did you solve it?
Pebble-Clay is a JS package that can also be installed by running
npm install pebble-clay
This fixes the issue.
Alternatively downloading and installing the SDK 2.9 will fix it. (This will not overwrite the latest version of the SDK.)

Electron App & FFMpeg - Library not loaded

I've recently upgraded Electron to v0.37, and upon trying to start my app, I'm getting an error of the following.
dyld: Library not loaded: /usr/local/lib/libffmpeg.dylib
Referenced from: /usr/local/lib/node_modules/electron-prebuilt/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework
Reason: image not found
I have ffmpeg installed on my machine via homebrew, which I installed with brew install ffmpeg . I've tried uninstalling ffmpeg and reinstalling, but haven't had any luck.
I've noticed in more recent versions of Electron, since v0.36.8 they've 'Link with ffmpeg dynamically' according to the changelog.
I should note, I'm using ffmpeg in my electron app, and specifically, im utilizing the Fluent FFMpeg node library (https://www.npmjs.com/package/fluent-ffmpeg).
Has anyone come across this same issue? Any idea on a fix?
It is an known issue in version 0.37. As a temporary workaround you can downgrade to version 0.36.

How to compile ffmpeg with librtmp for android in Vitamio 5.0?

i was using vitamio 4.2.2 but google send me a mail about vitamio libs including security backdoors. And says update vitamio version. But im using vitamio version which was compiled ffmpeg with librtmp android. Now i will use Vitamio 5.0 But How to find ffmpeg rtmp build or who can compile ffmpeg librtmp for Vitamio 5.0 ? Please help me
for you: https://www.vitamio.org/Download/
note: Vitamio 5.0.0 only show dowload for China language.

Opencv video codec OSX

I'm working through the example in openCV Highgui that can be found here. It may be worth noting that i'm running osx. When running the file I get the error "WARNING: Couldn't read movie file video/Megamind.avi" . Is this a codec problem (the .avi file came with openCV) or an environment problem? How is this fixed?
sometime port install complains and screws up old installations. Try brew OS X's package manager to install ffmpeg
I believe Megamind.avi is in XVID. Try installing the XVID codec from XVID. I guess the OSX package manager can get it as well.
To answer your question more directly: I guess you could both build opencv with the right references but it worked for me (in Windows) just to setup the codec for my system in general.
I followed the instruction (See below) for installing opencv on mac os X with ffmpeg support.
It worked and I can see my .avi files working. There is a detail installation instruction,
step by step.
follow this link

Resources