Is that not why we have a testing repo??? or beta??? Yeah, it could cause problems with pre-existing installs of imagemagick. That is why I told people to uninstall any imagemagick packages before they tried it out. I tested some before I put it out.
Life if full of risk. Be like Volker and face your fear. Read his sig.
Anyway, you enjoy this stuff.
With plugins, having a testing repo or beta is fine. Put non-plugin (binaries) packages in the repo will upgrade anyone's system who enables the repo. This isn't just about people who willing to try emby.
Read my sig... I am using svn OMV 2.x. Obviously, I am willing to take risk. I just don't want some unmaintainable, workaround checkinstall package with my signature on it. Is it too much to ask to not do something half-ass??
Aaron, are you telling me you can't figure it out? I thought we agreed already not to use checkinstall.
Some type of warning that any version of imagemagick will be removed before proceeding.
Maybe test upgrading ImageMagick to package created????
I'm sure I can figure it out. I just got it to compile without the configure flags. Were they necessary for emby or just to get the package to compile?
No, there were some deprecations it passed through and like 4 folders needed to be added for it to complete successfully.
I know you can do it... Hope you're not getting mad. 
These were necessary for Emby:
./configure --with-webp=yes --with-quantum-depth=8
Webp:
With plugins, having a testing repo or beta is fine. Put non-plugin (binaries) packages in the repo will upgrade anyone's system who enables the repo. This isn't just about people who willing to try emby.
Read my sig... I am using svn OMV 2.x. Obviously, I am willing to take risk. I just don't want some unmaintainable, workaround checkinstall package with my signature on it. Is it too much to ask to not do something half-ass??
And there's something more. This version of imagemagick is specially compiled for working with quantum 8 that gives a shitty quality. Being enough for Emby thumbs, doesn't mean that any user running some other program that uses the library for high quality image editing wouldn't want to kill us after an unexpected upgrade.
I've been suggested to use docker for Emby. And that's pretty interesting.
Anyway guys, could we discuss the advanced implementation/developing details on PM? Users will get nuts if that continues 
MediaBrowser it's so picky with the subtitles. They may be in a format that is not supported. I had those problems with some of my content. You may ask on MediaBrowser forums.
Thanks!
I installed it, but cant view the client or admin page.
I rebooted the nas.
In chrome : ERR_CONNECTION_REFUSED
How is the status oft the mediabrowser or embi Plugin?
ah right. I started by hand, I now get emby and have to register, but it says short disk full...looking how to clean my system disk by now.
Edit: deinstall saves me about 400 mb
A lot on a 2gb d.o.m.
looking for a 4gb now.
Edit 2. Does a Atom 32bit processor perform enough, system has 4gb of ram.
Any news from emby Plugin?
Aaron needs to compile/sign the webp and imagemagick first, and host them. The plugin should not take very long to update at all. Told him there is no rush. It is working with instructions on pg. 23.
Aaron needs to compile/sign the webp and imagemagick first, and host them.
I can't get them to compile the debian way with 6.9.1. Is 6.8.9 new enough?
Yes... Make sure you configure correctly. I saw people using versions older than that and it is working.
./configure --with-webp=yes --with-quantum-depth=8
Everything is proven to work. Luke is doing a good job. It is running better and better. Just wish they had a version that was not dependent on mono, a native linux package.
Will try in a bit
Anyone want to try the q16 libraries? Packages built but forgot to add q8 flag...
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
