Locating multiple ffmpeg installations

I use multiple tools that rely on ffmpeg, a couple of which have downloaded different versions of ffmpeg from the one provided in the package repositories (e.g., mpv and moviepy via imageio). The separate ffmpeg binaries for these programs have not interfered with each other, but I am having difficulties related to some inconsistencies between the different versions.

My question is: how do I locate the different versions of ffmpeg (other than the ubuntu package) that exist on my system so that I can point everything toward the binary of the most current version (in my case, the ffmpeg running with mpv)?

Thanks!

edited Dec 30 '18 at 1:22

asked Dec 30 '18 at 0:57

hb_

316

What's wrong with find / -name ffmpeg?

– Pedro Lobito
Dec 30 '18 at 5:33

add a comment |

Thanks!

edited Dec 30 '18 at 1:22

asked Dec 30 '18 at 0:57

hb_

316

What's wrong with find / -name ffmpeg?

– Pedro Lobito
Dec 30 '18 at 5:33

add a comment |

Thanks!

edited Dec 30 '18 at 1:22

asked Dec 30 '18 at 0:57

hb_

316

Thanks!

software-installation ffmpeg mpv-media-player

edited Dec 30 '18 at 1:22

asked Dec 30 '18 at 0:57

hb_

316

edited Dec 30 '18 at 1:22

asked Dec 30 '18 at 0:57

hb_

316

edited Dec 30 '18 at 1:22

asked Dec 30 '18 at 0:57

hb_

316

asked Dec 30 '18 at 0:57

hb_

316

asked Dec 30 '18 at 0:57

hb_

316

What's wrong with find / -name ffmpeg?

– Pedro Lobito
Dec 30 '18 at 5:33

add a comment |

What's wrong with find / -name ffmpeg?

– Pedro Lobito
Dec 30 '18 at 5:33

What's wrong with find / -name ffmpeg?

– Pedro Lobito
Dec 30 '18 at 5:33

add a comment |

2 Answers
2

active

oldest

votes

Experimenting a bit more, I was able to locate the alternate ffmpeg binaries installed by other programs using locate and egrep:

locate mpv | egrep 'ffmpeg$'
locate imageio | egrep 'ffmpeg$'

And then use alias to redirect the ffmpeg command to the most up-to-date binary without breaking other dependencies.

edited Dec 30 '18 at 2:47

answered Dec 30 '18 at 1:20

hb_

316

@mchid yeah, I did build mpv from source, but it left binaries in ~/mpv-build/build_libs/bin/ and ~/mpv-build/ffmpeg_build/, and not in /usr/local/bin/ for whatever reason

– hb_
Dec 30 '18 at 2:34

@hb Okay, /usr/local/bin is not used because this is a local install.

– mchid
Dec 30 '18 at 9:08

add a comment |

There are two commands you can use to determine which binary is in use and also if there is more than one ffmpeg installed.

First, to determine which binary is currently in use, run the following command:

which ffmpeg

Next, you can show where ffmpeg files and binaries are by running the following command:

whereis ffmpeg

The whereis command should show where the different binaries are if there is more than one and the binaries are usually under a bin directory.

answered Dec 30 '18 at 1:39

mchid

22.7k25184

hm, it seems whereis only gives me the current binary in use, but doesn't give me the locations of the ffmpeg binaries installed by mpv and imageio, whereas locate does (though along with a lot of other locations I don't need)

– hb_
Dec 30 '18 at 2:42

@hb_ It looks like whereis does not work when trying to find something installed locally.

– mchid
Dec 30 '18 at 9:12

@hb_ This is maybe because the directory is not in your $PATH. I have stuff installed in /home/$USER/.local/bin that shows up but /home/$USER/.local/bin is in my $PATH.

– mchid
Dec 31 '18 at 22:04

thanks for clarifying this! /home/$USER/.local/bin was indeed not in my path

– hb_
Jan 2 at 4:30

@hb_ I wouldn't mess with it if you found a way to make it work so I wouldn't add that to my path unless needed. Besides, it didn't look like ffmpeg was installed in /home/$USER/.local/bin. I was just using /home/$USER/.local/bin as an example because that is where some python stuff shows up if installed locally and whereis does show the python apps installed because this is in my $PATH.

– mchid
Jan 2 at 16:45

add a comment |

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105490%2flocating-multiple-ffmpeg-installations%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

Experimenting a bit more, I was able to locate the alternate ffmpeg binaries installed by other programs using locate and egrep:

locate mpv | egrep 'ffmpeg$'
locate imageio | egrep 'ffmpeg$'

And then use alias to redirect the ffmpeg command to the most up-to-date binary without breaking other dependencies.

edited Dec 30 '18 at 2:47

answered Dec 30 '18 at 1:20

hb_

316

@mchid yeah, I did build mpv from source, but it left binaries in ~/mpv-build/build_libs/bin/ and ~/mpv-build/ffmpeg_build/, and not in /usr/local/bin/ for whatever reason

– hb_
Dec 30 '18 at 2:34

@hb Okay, /usr/local/bin is not used because this is a local install.

– mchid
Dec 30 '18 at 9:08

add a comment |

Experimenting a bit more, I was able to locate the alternate ffmpeg binaries installed by other programs using locate and egrep:

locate mpv | egrep 'ffmpeg$'
locate imageio | egrep 'ffmpeg$'

And then use alias to redirect the ffmpeg command to the most up-to-date binary without breaking other dependencies.

edited Dec 30 '18 at 2:47

answered Dec 30 '18 at 1:20

hb_

316

@mchid yeah, I did build mpv from source, but it left binaries in ~/mpv-build/build_libs/bin/ and ~/mpv-build/ffmpeg_build/, and not in /usr/local/bin/ for whatever reason

– hb_
Dec 30 '18 at 2:34

@hb Okay, /usr/local/bin is not used because this is a local install.

– mchid
Dec 30 '18 at 9:08

add a comment |

Experimenting a bit more, I was able to locate the alternate ffmpeg binaries installed by other programs using locate and egrep:

locate mpv | egrep 'ffmpeg$'
locate imageio | egrep 'ffmpeg$'

And then use alias to redirect the ffmpeg command to the most up-to-date binary without breaking other dependencies.

edited Dec 30 '18 at 2:47

answered Dec 30 '18 at 1:20

hb_

316

Experimenting a bit more, I was able to locate the alternate ffmpeg binaries installed by other programs using locate and egrep:

locate mpv | egrep 'ffmpeg$'
locate imageio | egrep 'ffmpeg$'

And then use alias to redirect the ffmpeg command to the most up-to-date binary without breaking other dependencies.

edited Dec 30 '18 at 2:47

answered Dec 30 '18 at 1:20

hb_

316

edited Dec 30 '18 at 2:47

answered Dec 30 '18 at 1:20

hb_

316

answered Dec 30 '18 at 1:20

hb_

316

answered Dec 30 '18 at 1:20

hb_

316

@mchid yeah, I did build mpv from source, but it left binaries in ~/mpv-build/build_libs/bin/ and ~/mpv-build/ffmpeg_build/, and not in /usr/local/bin/ for whatever reason

– hb_
Dec 30 '18 at 2:34

@hb Okay, /usr/local/bin is not used because this is a local install.

– mchid
Dec 30 '18 at 9:08

add a comment |

@mchid yeah, I did build mpv from source, but it left binaries in ~/mpv-build/build_libs/bin/ and ~/mpv-build/ffmpeg_build/, and not in /usr/local/bin/ for whatever reason

– hb_
Dec 30 '18 at 2:34

@hb Okay, /usr/local/bin is not used because this is a local install.

– mchid
Dec 30 '18 at 9:08

@mchid yeah, I did build mpv from source, but it left binaries in ~/mpv-build/build_libs/bin/ and ~/mpv-build/ffmpeg_build/, and not in /usr/local/bin/ for whatever reason

– hb_
Dec 30 '18 at 2:34

@hb Okay, /usr/local/bin is not used because this is a local install.

– mchid
Dec 30 '18 at 9:08

add a comment |

There are two commands you can use to determine which binary is in use and also if there is more than one ffmpeg installed.

First, to determine which binary is currently in use, run the following command:

which ffmpeg

Next, you can show where ffmpeg files and binaries are by running the following command:

whereis ffmpeg

The whereis command should show where the different binaries are if there is more than one and the binaries are usually under a bin directory.

answered Dec 30 '18 at 1:39

mchid

22.7k25184

hm, it seems whereis only gives me the current binary in use, but doesn't give me the locations of the ffmpeg binaries installed by mpv and imageio, whereas locate does (though along with a lot of other locations I don't need)

– hb_
Dec 30 '18 at 2:42

@hb_ It looks like whereis does not work when trying to find something installed locally.

– mchid
Dec 30 '18 at 9:12

@hb_ This is maybe because the directory is not in your $PATH. I have stuff installed in /home/$USER/.local/bin that shows up but /home/$USER/.local/bin is in my $PATH.

– mchid
Dec 31 '18 at 22:04

thanks for clarifying this! /home/$USER/.local/bin was indeed not in my path

– hb_
Jan 2 at 4:30

@hb_ I wouldn't mess with it if you found a way to make it work so I wouldn't add that to my path unless needed. Besides, it didn't look like ffmpeg was installed in /home/$USER/.local/bin. I was just using /home/$USER/.local/bin as an example because that is where some python stuff shows up if installed locally and whereis does show the python apps installed because this is in my $PATH.

– mchid
Jan 2 at 16:45

add a comment |

There are two commands you can use to determine which binary is in use and also if there is more than one ffmpeg installed.

First, to determine which binary is currently in use, run the following command:

which ffmpeg

Next, you can show where ffmpeg files and binaries are by running the following command:

whereis ffmpeg

The whereis command should show where the different binaries are if there is more than one and the binaries are usually under a bin directory.

answered Dec 30 '18 at 1:39

mchid

22.7k25184

hm, it seems whereis only gives me the current binary in use, but doesn't give me the locations of the ffmpeg binaries installed by mpv and imageio, whereas locate does (though along with a lot of other locations I don't need)

– hb_
Dec 30 '18 at 2:42

@hb_ It looks like whereis does not work when trying to find something installed locally.

– mchid
Dec 30 '18 at 9:12

@hb_ This is maybe because the directory is not in your $PATH. I have stuff installed in /home/$USER/.local/bin that shows up but /home/$USER/.local/bin is in my $PATH.

– mchid
Dec 31 '18 at 22:04

thanks for clarifying this! /home/$USER/.local/bin was indeed not in my path

– hb_
Jan 2 at 4:30

@hb_ I wouldn't mess with it if you found a way to make it work so I wouldn't add that to my path unless needed. Besides, it didn't look like ffmpeg was installed in /home/$USER/.local/bin. I was just using /home/$USER/.local/bin as an example because that is where some python stuff shows up if installed locally and whereis does show the python apps installed because this is in my $PATH.

– mchid
Jan 2 at 16:45

add a comment |

There are two commands you can use to determine which binary is in use and also if there is more than one ffmpeg installed.

First, to determine which binary is currently in use, run the following command:

which ffmpeg

Next, you can show where ffmpeg files and binaries are by running the following command:

whereis ffmpeg

The whereis command should show where the different binaries are if there is more than one and the binaries are usually under a bin directory.

answered Dec 30 '18 at 1:39

mchid

22.7k25184

There are two commands you can use to determine which binary is in use and also if there is more than one ffmpeg installed.

First, to determine which binary is currently in use, run the following command:

which ffmpeg

Next, you can show where ffmpeg files and binaries are by running the following command:

whereis ffmpeg

The whereis command should show where the different binaries are if there is more than one and the binaries are usually under a bin directory.

answered Dec 30 '18 at 1:39

mchid

22.7k25184

answered Dec 30 '18 at 1:39

mchid

22.7k25184

answered Dec 30 '18 at 1:39

mchid

22.7k25184

answered Dec 30 '18 at 1:39

mchid

22.7k25184

hm, it seems whereis only gives me the current binary in use, but doesn't give me the locations of the ffmpeg binaries installed by mpv and imageio, whereas locate does (though along with a lot of other locations I don't need)

– hb_
Dec 30 '18 at 2:42

@hb_ It looks like whereis does not work when trying to find something installed locally.

– mchid
Dec 30 '18 at 9:12

@hb_ This is maybe because the directory is not in your $PATH. I have stuff installed in /home/$USER/.local/bin that shows up but /home/$USER/.local/bin is in my $PATH.

– mchid
Dec 31 '18 at 22:04

thanks for clarifying this! /home/$USER/.local/bin was indeed not in my path

– hb_
Jan 2 at 4:30

@hb_ I wouldn't mess with it if you found a way to make it work so I wouldn't add that to my path unless needed. Besides, it didn't look like ffmpeg was installed in /home/$USER/.local/bin. I was just using /home/$USER/.local/bin as an example because that is where some python stuff shows up if installed locally and whereis does show the python apps installed because this is in my $PATH.

– mchid
Jan 2 at 16:45

add a comment |

hm, it seems whereis only gives me the current binary in use, but doesn't give me the locations of the ffmpeg binaries installed by mpv and imageio, whereas locate does (though along with a lot of other locations I don't need)

– hb_
Dec 30 '18 at 2:42

@hb_ It looks like whereis does not work when trying to find something installed locally.

– mchid
Dec 30 '18 at 9:12

@hb_ This is maybe because the directory is not in your $PATH. I have stuff installed in /home/$USER/.local/bin that shows up but /home/$USER/.local/bin is in my $PATH.

– mchid
Dec 31 '18 at 22:04

thanks for clarifying this! /home/$USER/.local/bin was indeed not in my path

– hb_
Jan 2 at 4:30

@hb_ I wouldn't mess with it if you found a way to make it work so I wouldn't add that to my path unless needed. Besides, it didn't look like ffmpeg was installed in /home/$USER/.local/bin. I was just using /home/$USER/.local/bin as an example because that is where some python stuff shows up if installed locally and whereis does show the python apps installed because this is in my $PATH.

– mchid
Jan 2 at 16:45

hm, it seems whereis only gives me the current binary in use, but doesn't give me the locations of the ffmpeg binaries installed by mpv and imageio, whereas locate does (though along with a lot of other locations I don't need)

– hb_
Dec 30 '18 at 2:42

@hb_ It looks like whereis does not work when trying to find something installed locally.

– mchid
Dec 30 '18 at 9:12

@hb_ This is maybe because the directory is not in your $PATH. I have stuff installed in /home/$USER/.local/bin that shows up but /home/$USER/.local/bin is in my $PATH.

– mchid
Dec 31 '18 at 22:04

thanks for clarifying this! /home/$USER/.local/bin was indeed not in my path

– hb_
Jan 2 at 4:30

@hb_ I wouldn't mess with it if you found a way to make it work so I wouldn't add that to my path unless needed. Besides, it didn't look like ffmpeg was installed in /home/$USER/.local/bin. I was just using /home/$USER/.local/bin as an example because that is where some python stuff shows up if installed locally and whereis does show the python apps installed because this is in my $PATH.

– mchid
Jan 2 at 16:45

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Ask Ubuntu!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu