Compiling from source, ffmpeg versioning. Confused
Posted: Mon May 02, 2016 2:06 pm
Linux version Fedora 23; Audacity 2.1.2 built from source.
Have read and followed all instructions elsewhere to successfully compile audacity from git, and have managed to understand the build config options. Like many people I have many different music formats in my library, and I need to be able to get at all of them, patent and licensing restrictions aside (but noted).
I read that even if compiling locally Audacity only supports ffmpeg up to version 2.3. Not surprisingly my current system (Fedora 23) has version 2.8.6 installed via other software, and even later versions of it are available elsewhere.
I thought about building an earlier copy of ffmpeg, but it's proven so fraught that I thought instead to try downgrading my currently installed version via dnf and package manager. However, the bash output tells me that it would remove packages like "vlc core" along with some of the gstreamer plugins, which of course would effectively break other parts of my system (including of course music replay!)
Can anyone tell me:
is it possible to build and install ffmpeg 2.3.* somewhere locally and have the build config for audacity compile to that, and which would NOT mess up or overwrite my other libraries (needed for video replay etc) - meaning effectively that I'll have a local instance of it purely for audacity.
If not, would building with earlier versions of libav resolve the problem, or is that simply another side of the same coin (libav being compiled into ffmeg? am I right?).
It appears to me at present that although yes, we all understand that "due to licensing restrictions..." yada yada what this effectively boils down to is that it would be impossible to use a current version of audacity on an up to date Linux system if I want all of its features supported (and why would I not??)
I have the full functioning version on Windows, but it would be an utter pain to keep swapping music files back and forth across computers just for the sake of some edits.
Have read and followed all instructions elsewhere to successfully compile audacity from git, and have managed to understand the build config options. Like many people I have many different music formats in my library, and I need to be able to get at all of them, patent and licensing restrictions aside (but noted).
I read that even if compiling locally Audacity only supports ffmpeg up to version 2.3. Not surprisingly my current system (Fedora 23) has version 2.8.6 installed via other software, and even later versions of it are available elsewhere.
I thought about building an earlier copy of ffmpeg, but it's proven so fraught that I thought instead to try downgrading my currently installed version via dnf and package manager. However, the bash output tells me that it would remove packages like "vlc core" along with some of the gstreamer plugins, which of course would effectively break other parts of my system (including of course music replay!)
Can anyone tell me:
is it possible to build and install ffmpeg 2.3.* somewhere locally and have the build config for audacity compile to that, and which would NOT mess up or overwrite my other libraries (needed for video replay etc) - meaning effectively that I'll have a local instance of it purely for audacity.
If not, would building with earlier versions of libav resolve the problem, or is that simply another side of the same coin (libav being compiled into ffmeg? am I right?).
It appears to me at present that although yes, we all understand that "due to licensing restrictions..." yada yada what this effectively boils down to is that it would be impossible to use a current version of audacity on an up to date Linux system if I want all of its features supported (and why would I not??)
I have the full functioning version on Windows, but it would be an utter pain to keep swapping music files back and forth across computers just for the sake of some edits.