openmediavault-emby plugin (formerly mediabrowser)

The mediabrowser is the old one.

apt-get --purge remove openmediavault-mediabrowser

Then install the openmediavault-emby

Thanks, tekkb.

@Meniak The ffmpeg is normally downloaded by the Emby server. This is how it works for the amd64 and i386 CPUs. I have done everything for the plugin to work with the armv71 cpu except ffmpeg. I had hoped months ago the Emby developers would add ffmpeg so it would auto download for armv71 architecture. That is where it sits. But like I said if you see on their forums someone has a working version (with ffprobe) you can get this plugin working for armv71. You guys might ask them on the Emby forums to add ffmpeg so it auto downloads for the armv71 architecture. Maybe a little pressure there will get it done.

@tekkb I asked already but no answer still. I saw on their forums people are asking in the Qnap section too. I'm not familiar enough with CLI to install ffmpeg by myself so I hope someone includes it in Emby. I'm running the server on a NUC but that's used for home automation so it would be better if I can run Emby on my NAS. I have the paying version so I can probably transfer a backup to the new Emby.

Apparently there's a working ffmpeg version in deb-multimedia.org

emby has test repos for Synology NAS. Maybe you can find a matching arm ffmpeg there too http://emby.media/community/in…pic/22921-synology-setup/

That synology package is not going to work.

Hi I would like to install emby on my system but i have the dependency error. (sorry it's in french, my system is in french)

Les paquets suivants contiennent des dépendances non satisfaites :
 openmediavault-emby : Dépend: libmono-cil-dev (>= 3.10) mais 2.10.8.1-8+deb7u1 devra être installé
                       Dépend: libgdiplus (>= 3.8) mais 2.10-3+b1 devra être installé

I see that some suggestion to test with the testing dependance, and remove the ffmpeg, but i still have the issue.

Can you help me ?

Did you enable the mono repo in OMV Extras?

If you look at this you can see the package you are pulling up (2.10.8.1-8+deb7u1) is coming from the standard Debian repos. That tells me you do not have the mono project repo endabled that is in OMV Extras:

root@stoneburnervm:~# apt-cache policy libmono-cil-dev
libmono-cil-dev:
  Installed: 4.0.4.1-0xamarin1
  Candidate: 4.0.4.1-0xamarin1
  Version table:
 *** 4.0.4.1-0xamarin1 0
        995 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages
        100 /var/lib/dpkg/status
     2.10.8.1-8+deb7u1 0
        995 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
        995 http://security.debian.org/ wheezy/updates/main amd64 Packages

PS- The command "apt-cache policy packagename" will tell you the repo in which a package resides.

Yes i have the mono depot activated, i try to put the testing but with same result.

For the command it's seem that the depot is activated but for the installation, it's the debian that will be used

apt-cache policy libmono-cil-dev
libmono-cil-dev:
  Installé : (aucun)
  Candidat : 2.10.8.1-8+deb7u1
 Table de version :
     4.0.4.1-0xamarin1 0
        990 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages
     2.10.8.1-8+deb7u1 0
        995 http://ftp.fr.debian.org/debian/ wheezy/main amd64 Packages
        995 http://security.debian.org/ wheezy/updates/main amd64 Packages

Maybe, how can i be sure ?

It is the pinning... hold on. I have to start a vm.

Give me results of this:

ls -la /etc/apt/preferences.d/99omv-extras-org

Sorry, when I copied and pasted I missed the / in front of the etc.

for the command : ls -la /etc/apt/preferences.d/99omv-extras-org

-rw-r--r-- 1 root root 1845 oct.  20 20:05 /etc/apt/preferences.d/99omv-extras-org

for the content of the file : cat 99omv-extras-org

Package: *
Pin: release n=stoneburner, origin packages.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-vb, origin packages.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-plex, origin packages.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-greyhole, origin packages.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-vdr, origin packages.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release o=e-tobi.net
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-miller, origin dh2k.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=precise, origin ppa.launchpad.net/deluge-team/ppa/ubuntu
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-btsync, origin packages.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=wheezy, origin debian.yeasoft.net
Pin-Priority: 995
Package: *
Pin: release n=stoneburner-vpn, origin dh2k.omv-extras.org
Pin-Priority: 995
Package: *
Pin: release n=wheezy, origin archive.zfsonlinux.org
Pin-Priority: 400
Package: *
Pin: release n=stoneburner-zfs, origin packages.omv-extras.org
Pin-Priority: 996
Package: *
Pin: release n=stoneburner-gluster, origin packages.omv-extras.org
Pin-Priority: 996
Package: *
Pin: release o=download.gluster.org
Pin-Priority: 1001
Package: *
Pin: release n=stoneburner-mono, origin packages.omv-extras.org
Pin-Priority: 996
Package: *
Pin: release o=download.mono-project.com
Pin-Priority: 1001
Package: *
Pin: release n=stoneburner-docker, origin packages.omv-extras.org
Pin-Priority: 996
Package: *
Pin: release o=apt.dockerproject.org
Pin-Priority: 1001
Package: *
Pin: release n=stoneburner-hwraid, origin packages.omv-extras.org
Pin-Priority: 996
Package: *
Pin: release n=stoneburner-backports, origin packages.omv-extras.org
Pin-Priority: 995

Yes, I wanted the cat command,, not ls -la. Hmm...

Yeah, you have a higher pin priority for the mono project. It should be using that repo but is not.
I know nothing about regional stuff. I'm native English speaker.

Hopefully Aaron can look at this soon.

@ryecoaaron

Thanks for your help.
I don't know what can i do, so if you have an idea i will test.

Aaron, why is he getting 990 on apt-cache policy libmono-cil-dev ??? When I run this command I get 995. Did you notice that???

990 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages

@ryecoaaron

I resolve my issue.

I remove all the repository and save.
I do an apt clean
I reactivate the repository and i can install the emby plugin.

Thanks

for information:

apt-cache policy libmono-cil-dev

libmono-cil-dev:
Installé : (aucun)
Candidat : 4.0.4.1-0xamarin1
Table de version :
4.0.4.1-0xamarin1 0
990 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages
2.10.8.1-8+deb7u1 0
500 http://ftp.fr.debian.org/debian/ wheezy/main amd64 Packages
500 http://security.debian.org/ wheezy/updates/main amd64 Packages

Thanks for your help