Erik 120 Posted December 19, 2016 Share Posted December 19, 2016 (edited) Hi, Just checking out the changes and it seems the default under transcoding is custom version of ffmpeg, with the path also pre-completed (I have never used a custom version. EDIT: I switched back to use system installed version but then I get error msg of unable to locate ffmpeg and needed info ffprobe in same folder when I try to save the setting... Thanks Edited December 19, 2016 by Erik Link to comment Share on other sites More sharing options...
jordy 284 Posted December 19, 2016 Share Posted December 19, 2016 I think that Emby has always used a "Custom" version of ffmpeg. It is installed along with Emby Server, probably to ensure that everything works out of the box. You have the option of installing your own version as the "System version" but I'm not sure where that's looking. Luke should be able to tell you where that is. Link to comment Share on other sites More sharing options...
Erik 120 Posted December 19, 2016 Author Share Posted December 19, 2016 Thanks @@jordy That would make sense. However, when it's on the default installed setting (use custom) it shows the selectable path on the line below. Then if you select system installed version the ability to select the path is hidden. So unless I'm misunderstanding that seems reversed, no? Link to comment Share on other sites More sharing options...
FrostByte 5053 Posted December 19, 2016 Share Posted December 19, 2016 The way you describe what you're seeing it sounds correct to me. If the system is installing ffmpeg for you then you don't really need to see the path as it will do all that for you and if you're using a custom version of ffmpeg which you downloaded from the ffmpeg dev site then you want to see the box where you can input the path Here is the path it installs to if using the default Emby installed version C:\Users\user\AppData\Roaming\Emby-Server\ffmpeg\20160410\ffmpeg.exe 1 Link to comment Share on other sites More sharing options...
sualfred 677 Posted December 19, 2016 Share Posted December 19, 2016 (edited) I assume it's a bug and the field is just hidden. Just check you config file in config/encoding.xml. You should be able to set the ffmpeg path there. <EncoderAppPath>/var/lib/emby-server/ffmpeg/3-1-6/ffmpeg</EncoderAppPath> Edited December 19, 2016 by sualfred Link to comment Share on other sites More sharing options...
FrostByte 5053 Posted December 19, 2016 Share Posted December 19, 2016 Why would it be a bug? You don't need to see the field if Emby is going to install its version because it knows where it's going to install it. Link to comment Share on other sites More sharing options...
Erik 120 Posted December 19, 2016 Author Share Posted December 19, 2016 That may be the new correct way. It's just a complete change from 3.0.85 where the path field was displayed, but no path was displayed or required unless you wanted to use your own custom version. That's why to me "system installed" sounds more like Emby installed and "custom version" sounds like I went and installed a different (non-Emby) version. So that's why I'm not sure if it's a bug or a new definition of it. Link to comment Share on other sites More sharing options...
sualfred 677 Posted December 19, 2016 Share Posted December 19, 2016 Why would it be a bug? You don't need to see the field if Emby is going to install its version because it knows where it's going to install it. Because there was a setting with "System installed version" and "Custom path". This is completely gone including the displayed path field next to it. Some Linux system aren't shipped with ffmpeg and you have to compile it on your own and set the path manually. Link to comment Share on other sites More sharing options...
FrostByte 5053 Posted December 19, 2016 Share Posted December 19, 2016 That's why to me "system installed" sounds more like Emby installed and "custom version" sounds like I went and installed a different (non-Emby) version. Correct. System installed is Emby installed and thus the field is hidden like you described in post #3 because you don't need to enter anything With a custom install the field is not hidden so you can tell Emby where you placed the files Link to comment Share on other sites More sharing options...
FrostByte 5053 Posted December 19, 2016 Share Posted December 19, 2016 Maybe I just haven't had enough coffee 1 Link to comment Share on other sites More sharing options...
Erik 120 Posted December 19, 2016 Author Share Posted December 19, 2016 (edited) So when I select system installed version...the path disappears (which makes sense) but then when I save the setting I get an error that ffmpeg cannot be found and the setting reverts to custom installed version with the path being the Emby install directory. So I'm saying the displayed info seems mostly correct. However, I believe the function is reversed. It should...... Select system installed (which should be the default), no path displayed...perfect (not working right now...) Select custom (not default as it is now), user customized path is displayed and you must point to the custom ffmpeg location. Edited December 19, 2016 by Erik 1 Link to comment Share on other sites More sharing options...
FrostByte 5053 Posted December 19, 2016 Share Posted December 19, 2016 Ya, that sounds like a bug I was just commenting on what you said in post #3. Wording sounds correct to me, just doesn't seem to work that way Link to comment Share on other sites More sharing options...
sualfred 677 Posted December 19, 2016 Share Posted December 19, 2016 I don't even have the option to choose between the system installed and custom version anymore 1 Link to comment Share on other sites More sharing options...
FrostByte 5053 Posted December 19, 2016 Share Posted December 19, 2016 You can download the Emby version from Github yourself if you want. Maybe just place that in a folder and enter that as a "custom" version to fool Emby for now. https://github.com/MediaBrowser/Emby.Resources/tree/master/ffmpeg/windows Link to comment Share on other sites More sharing options...
Luke 37132 Posted December 19, 2016 Share Posted December 19, 2016 The important thing is, are you experiencing a problem? Link to comment Share on other sites More sharing options...
Erik 120 Posted December 19, 2016 Author Share Posted December 19, 2016 @@Luke No...... But as I said, I went to change it from custom back to system installed thinking it was switch by mistake during the new install, but then I got an error. So, as it seems to be reversed from what it was before I spend a little time trying to figure it out, even installing Emby again to make sure. So...yes it works but caused a problem with me as I went through the new version. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now