The guide installs ffmpeg to ~/bin because:
- it avoids conflicts with repository packages
- it is non-destructive and avoids messing with the system (useful for users with no sudo privileges, like some server users)
- it avoids the complexity of the package management system
- removal is simple
Adding ~/bin to your PATH
The Persistent Environment Variables section of the guide has the following instructions:
The first line allows you to use "man ffmpeg" to get the associated man pages for your new ffmpeg. The second line sources ~/.profile which should immediately add ~/bin to your PATH, meaning that when you run "ffmpeg" in the terminal it will use ~/bin/ffmpeg (instead of the old, fake, crappy repository version for Ubuntu releases older than 14.04). However, now that I wrote that I now notice that in post #6 that ~/bin is now in your PATH, so it looks like you already did this.
echo "MANPATH_MAP $HOME/bin $HOME/ffmpeg_build/share/man" >> ~/.manpath
Sinthgunt, even if it did recognize it, may not work with your new ffmpeg. FFmpeg development is very active, and these GUIs tend to age quickly. You can try using ffmpeg directly. If you have any questions you can ask them here.