Leaderboard

Lösung: Hat nur ein wenig gedauert bis der emby lief. Jetzt funktioniert die Web-Oberfläche

I'm a big fan of services such as Rifftrax, and I hate having to manually mux files every time I purchase another release. Much in the same way that external subtitle file support was added, it would be nice to have external audio track support for TV and movies added as well. I wouldn't expect Emby to handle the offset calculations needed to sync the audio. It's not too difficult for me to modify that now.

Hi, Check out the faq, link in the first page of this thread. Cheers

Or copy/paste right where you want.

Like I said, buy discs and this problem goes away.

Do I take that to mean this is a bulk torrent that's floating around? Yet again, people obtaining their movies illegally and complaining that the system doesn't work for them. Buy discs and these problems go away.

Perfect, thank you both.

Hi. Yes the above will work, or, if you select the server and the connection times out, then the app will also offer you the option of removing it then. Please let us know if this answers your question. Thanks.

The multi-version feature is designed for different qualities of the same item as opposed to different cuts of a movie so, yes, these types of issues will occur if you use it for different cuts. Another option would be to use separate items and a collection. Thanks.

If hardware accelerated transcoding is important to you then the native package will generally be the easiest to get that working with.

Lool 4 days ago i was a noob(new user) now im a noob emby expert becausee of u guys

Scan 100% finished!!!! Thank You all especially to "CAYARS" This forum and EMBY simply rocks !!!i just uninstalled plex after 7-8 years i think Gracias .

I don't think Docker limits the number of cores for containers unless you specify it. I run Emby server on Debian in a docker container and all my 8 cores get used when transcoding. Your 100% CPU usage might be due to Snap not detecting quicksync or maybe you have to point the snap package to your CPU device driver, I'm not really familiar with Snap. I tell you this because for Docker, provided you have a recent i3-i5-i7 CPU, you have to provide the path to the driver to get quicksync working. In my case I gotta use the "--device /dev/dri" to the docker run command. If I don't specify that, transcodes take pretty much all my CPU resources instead of maybe 1/10th of that with quicksync enabled. Native install doesn't have this issue because the installed app has full access to your computer. In Docker, you kinda got to tell it what resource can be used for your container. Once you get familiar with Docker, you won't go back. It's so much more customizable than a Snap/Flatpak package. You can specify where you want all the config files to be stored at making backups very easy. With native or Snap/Flatpak, you gotta hunt for the location of settings/config files and sometimes they all over the place. Where Snap/Flatpak is useful is for Apps that don't rely on user configs. If there are user configs to be setup, I'd recommend Docker instead. As for native installs, I usually would only do it in a VM where there's nothing else on it. You can then back up the whole VM file. If there's gonna be other stuff installed on that machine, then I go for Docker. If you don't need/want to backup anything, then just native install everything.

This is currently being worked on as part of a larger project. Thanks for the feedback.

You already have the power to restrict this via user device access, although granted I wouldn't recommend it. We will rework this in future updates so that we can provide options to only show devices that they have used.