josh4trunks 70 Posted January 10, 2016 Posted January 10, 2016 (edited) @@kjp4756 or anyone else using FreeNAS. Mind testing if this update @@razzfazz's mono patches works as expected? Thanks! https://www.jruehlig.com/owncloud/index.php/s/0wgwxyD0JVz7cD1 Edited January 10, 2016 by josh4trunks
sluggo45 47 Posted January 10, 2016 Posted January 10, 2016 Seems to work ok for me in a test jail. Are there other changes? FFMpeg looks like it is still 2.7.2 - the 2.8.x (2.8.4) branch is generally better and includes the new "built in" AAC decoder which the FFMpeg team recommends as the default now; it's supposedly better and isn't encumbered by licensing or GPL issues. I use it currently with my main install (I manually updated Emby using the Emby-mono.zip for 5785, also build FFMpeg and Mono myself and changed the init script to use them) with no problems, but I'm not 100% on whether there are reasons not to use it on FreeBSD/FreeNAS with Emby or not. Seems to work fine transcoding.
kjp4756 41 Posted January 10, 2016 Posted January 10, 2016 @@kjp4756 or anyone else using FreeNAS. Mind testing if this update @@razzfazz's mono patches works as expected? Thanks! https://www.jruehlig.com/owncloud/index.php/s/0wgwxyD0JVz7cD1 Works for me as well.
josh4trunks 70 Posted January 10, 2016 Posted January 10, 2016 Thanks for taking a look. I'll rebuild the plugin with the latest ffmpeg and post it to the repo tonight.
razzfazz 11 Posted January 10, 2016 Posted January 10, 2016 Will your update actually enable the realtime library monitor by default as well? I believe Luke recently disabled it for everything except Windows...
josh4trunks 70 Posted January 10, 2016 Posted January 10, 2016 Will your update actually enable the realtime library monitor by default as well? I believe Luke recently disabled it for everything except Windows...nope
keyboard99 0 Posted January 10, 2016 Posted January 10, 2016 (edited) deleted! newbie! Edited January 11, 2016 by keyboard99
bluemonkey07 590 Posted January 11, 2016 Posted January 11, 2016 You will need to set up path substitution in Emby server dashboard
keyboard99 0 Posted January 11, 2016 Posted January 11, 2016 Thanks Vidman just seen this after deleting my post. Guess what I had just done. Path sun worked a treat. Sent from my SM-G900F using Tapatalk
josh4trunks 70 Posted January 11, 2016 Posted January 11, 2016 Seems to work ok for me in a test jail. Are there other changes? FFMpeg looks like it is still 2.7.2 - the 2.8.x (2.8.4) branch is generally better and includes the new "built in" AAC decoder which the FFMpeg team recommends as the default now; it's supposedly better and isn't encumbered by licensing or GPL issues. I use it currently with my main install (I manually updated Emby using the Emby-mono.zip for 5785, also build FFMpeg and Mono myself and changed the init script to use them) with no problems, but I'm not 100% on whether there are reasons not to use it on FreeBSD/FreeNAS with Emby or not. Seems to work fine transcoding. When I build the ffmpeg port, which option do I need to enable to use the built in AAC decoder? Or do I just disable everything (currently enabling AACPLUS) and it will be used?
alscritter 0 Posted January 11, 2016 Posted January 11, 2016 Hello all, I'm on version 3.0.5781.8 and a some what newbie to freenas. On my emby server GUI it states that there is a new version available Version 3.0.5785.0. When I go to my freenas plugins it does not give me the option to upgrade. Previously it would give me the option to upgrade. I was wondering if the plugin upgrade has been pushed to freenas or do I need to upload a file and upgrade that way.
PhilWhite 64 Posted January 11, 2016 Posted January 11, 2016 (edited) From what I understand Josh is still working on it. The plugin upgrade should be available shortly. Edited January 11, 2016 by PhilWhite
razzfazz 11 Posted January 11, 2016 Posted January 11, 2016 Is he not just using the version from the FreeBSD ports tree? That is still at 3.0.5781.2...
spencerisadog 4 Posted January 11, 2016 Posted January 11, 2016 Hello all, I'm on version 3.0.5781.8 and a some what newbie to freenas. On my emby server GUI it states that there is a new version available Version 3.0.5785.0. When I go to my freenas plugins it does not give me the option to upgrade. Previously it would give me the option to upgrade. I was wondering if the plugin upgrade has been pushed to freenas or do I need to upload a file and upgrade that way. The pbi (updated install in your FreeNAS available plugins) gets built by Josh4Trunks. The "update available" does not always line up with the FreeNAS available plugins. If you installed it manually, then you can update it manually, but most of us just wait for Josh to publish the pbi to the FreeNAS directory.
josh4trunks 70 Posted January 11, 2016 Posted January 11, 2016 If I don't get a reply about the new AAC I'll post the PBI I linked previously to the freenas repo, would be available tomorrow morning.
alscritter 0 Posted January 11, 2016 Posted January 11, 2016 Ok thanks I usually just wait for it to appear in the repo, which i will continue to do. Thanks for all the hard work.
Barlog9511 17 Posted January 12, 2016 Posted January 12, 2016 i doesnt start emby after upgrade .. i have error like this Freed UMA keg (udp_inpcb) was not empty (30 items). Lost 3 pages of memory. Freed UMA keg (udpcb) was not empty (249 items). Lost 1 pages of memory. ifa_del_loopback_route: deletion failed: 48
josh4trunks 70 Posted January 12, 2016 Posted January 12, 2016 i doesnt start emby after upgrade .. i have error like this Freed UMA keg (udp_inpcb) was not empty (30 items). Lost 3 pages of memory. Freed UMA keg (udpcb) was not empty (249 items). Lost 1 pages of memory. ifa_del_loopback_route: deletion failed: 48 where are those errors showing?did you stop emby before applying the update? what happens when you try 'service emby-server start' in the jail?
scharbag 19 Posted January 13, 2016 Posted January 13, 2016 Installed fine for me. Those errors posted above look like what happens when you simply turn a jail off. Cheers,
bluemonkey07 590 Posted January 13, 2016 Posted January 13, 2016 (edited) So is the library monitoring functioning in this update? Edited January 13, 2016 by Vidman
sluggo45 47 Posted January 13, 2016 Posted January 13, 2016 (edited) When I build the ffmpeg port, which option do I need to enable to use the built in AAC decoder? Or do I just disable everything (currently enabling AACPLUS) and it will be used? Sorry for the delay Josh. It's libfdk_aac that is the native one. I think it is the default now unless you choose another one of the AAC decoders. Note that if you build with "nonfree" disabled it won't use it because it's not compatible with the GPL (it's under LGPL 2.1 like the most of the rest of FFMpeg). Edited January 13, 2016 by sluggo45
josh4trunks 70 Posted January 13, 2016 Posted January 13, 2016 So is the library monitoring functioning in this update? I believe so, though you probably need to enable it.
josh4trunks 70 Posted January 13, 2016 Posted January 13, 2016 Sorry for the delay Josh. It's libfdk_aac that is the native one. I think it is the default now unless you choose another one of the AAC decoders. Note that if you build with "nonfree" disabled it won't use it because it's not compatible with the GPL (it's under LGPL 2.1 like the most of the rest of FFMpeg). Thanks, I'll use that one next time I build an update. It looks like with the freebsd port FDK_AAC it is disabled by default (probably because of licensing reasons). But if you do enable it, it automatically enableds the NONFREE option.
josh4trunks 70 Posted January 13, 2016 Posted January 13, 2016 @@sluggo45 From reading this it looks like the native AAC encoder and libfdk_aac are actually different things. And maybe I can just disable FDK_AAC and AACPLUS and aac encoding will still work with the native encoder? Something we can test out.
josh4trunks 70 Posted January 13, 2016 Posted January 13, 2016 (edited) Ok, here's a build with the latest ffmpeg, and AAC libraries disabled (but hopefully the new native library will kick in). If anyone has a chance to test if AAC still works that would be helpful for the next release. Thanks https://www.jruehlig.com/owncloud/index.php/s/jWAifnKn7LscBWx Edited January 13, 2016 by josh4trunks
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