jhoff80 87 Posted August 14, 2014 Share Posted August 14, 2014 I noticed after today's upgrade that there were two separate FFMPEG folders within my Media Browser Server folder in AppData. One, had the date of 06/12/14, and the other was one in July 2014. Assuming that the June one wasn't being used anymore, I deleted that folder... and it turns out that is exactly the version MBS is using, not the newer July one. I'm just wondering... was this an intentional move backwards, or was it just a mistake in switching over to the newer version. Link to comment Share on other sites More sharing options...
DGMayor 88 Posted September 13, 2014 Share Posted September 13, 2014 I was going to ask a similar question. I have 20 folders dating back to april 2013. 1.4gb of ffmpeg installs. surely I don't need all of these.. 1 Link to comment Share on other sites More sharing options...
aremann 0 Posted September 13, 2014 Share Posted September 13, 2014 (edited) im having huge problems with FFMPEG.exe ATM, getting huge loads on the CPU (100% on an i7 3960X) and it never stops. does not matter if i scan my library or anything. the usage is still really high. need to make a full report in the morning after some sleep. i cant use the server at all as it is now since it keep slowing down everything that MB does. Edited September 13, 2014 by aremann Link to comment Share on other sites More sharing options...
overClocked! 63 Posted September 13, 2014 Share Posted September 13, 2014 I was going to ask a similar question. I have 20 folders dating back to april 2013. 1.4gb of ffmpeg installs. surely I don't need all of these.. Seems like each successive install of MBS installs the latest build of the custom version of ffmpeg Mediabrowser uses. It seems to me that these are specific to the versions of MBS you have installed over time. I speculate that If you roll back an installation, the previous version will only invoke ffmpeg.exe from a specific path. If that path and build does not exist, then playback or transcoding will fail. So this may be a necessary side effect given the way installs work (installing over the existing installation without having the benefit of the previous versions installation files). I hope I'm making sense. I just woke up. [emoji16] Link to comment Share on other sites More sharing options...
ebr 14929 Posted September 13, 2014 Share Posted September 13, 2014 The routine that updated ffmpeg really should be cleaning up the old versions but I don't think it does right now. 1 Link to comment Share on other sites More sharing options...
jhoff80 87 Posted September 13, 2014 Author Share Posted September 13, 2014 My suggestion in deleting them would be to play something and check the logs to confirm which version MB3 is using before deleting them, because as I was saying in my original post, there was one time in which the newest one was not the one that MB3 was using. Otherwise you'll break everything. Link to comment Share on other sites More sharing options...
Luke 37112 Posted September 14, 2014 Share Posted September 14, 2014 the next release will clean them up autoamtically 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