Leaderboard

I need to make another compatibility update.

We use Apple TVs as our preferred devices ( have tried Shield and others) and I really prefer the Apple TV. I came to emby from the other platforms and have used Infuse with them in the past. I setup Infuse to work with Emby and I can play Atmos files that have the compressed lossy format. I understand the Apple TV only supports this version of atmos and not TrueHD. Would you please add support for lossy Atmos to the app so that we can play these files without needing to use Infuse? I would rather use the native app. I have seen a number of users request this from the "other platforms" and they have not gotten there. I expect this will bring a lot of new customers to Emby and sell Premiere subscriptions. If there is a licensing fee that Emby has to pay to enable this, I would also be willing to pay a one time enablement fee to add the feature to my server in addition to the premier subscription. Thanks.

Hello, I'm an Emby Premiere user since multiple years and love it. When I switched to an iPhone and started using Carplay, I was so happy to see Emby supports it. But when I found out it does not work with the files downloaded to my phone, I was honestly shocked. Most apps which offer music content allow offline downloads to be working with Carplay. It's even more strange to me, since Carplay is an advertised feature working with Emby Premiere only. Please add offline media support, at least for music, to Carplay. It's a very important feature to many I guess and I think it's missing way too long.

You can open the library.db with a DB browser and look at some of the items in the MediaItems table to see their path and figure it out from there. This query might work.

If installed to default Windows path: C:\Users\{yourusername]\AppData\Roaming\Emby-Server\programdata\root\default will list all your libraries with each respective options.xml listing library path/drive.

Unplug your drives from your PC, run Emby server and check to see what directories your libraries are in. Take note of it, plug your drives in and see what library is on what drive and assign drive letters accordingly. You could also probably just look at the logs if you don't want to spin it up.

Im not "an image embedded track" guy, so not speaking from experience/stake in the game... so personally i wouldnt miss the removal of custom track images (inheriting image from album works for me) presumably its a rare case for someone to have embedded track images but not want them and expect a change of album image in Emby to trickle down/overwrite embedded images....maybe the gold plated solution is to to have a non-default library option "read embedded image metadata" (i think thats in line with the existing option to use embedded title metadata) and establish it the users responsibility to more carefully manage their [embedded / in media folder album and track image] metadata offline ready from Emby to ingest if they wish to use that option. equally could leave as it is and just agree its the users responsibility to sort out their embedded metadata. This presumably affects very few people and there is a solution (sort out embedded metadata)

Thanks Luke, I managed to fumble through and get my head around it. I just created a new pfx using the renewed certificate pem and pointed emby to that. Easy process in the end.

OK we'll have to look into what our options are. Thanks.

Sorry, uploaded wrong log. Here are the logs created during installation (?) / running of new version embyserver-63852077000.txt embyserver-63852079135.txt embyserver-63852079322.txt embyserver-63852079352.txt embyserver-63852079452.txt embyserver-63852079516.txt embyserver-63852079686.txt

HI, from Emby's perspective, you don't need to revoke anything, although you may still wish to do that. You just need to point it to the pfx and supply the password. Please let us know how things go. Thanks !

HI, are you using the devices screen to delete the device from Emby server while it's trying to play? That could cause a problem.

OK we'll take a look at it. Thanks.

No. It needs to be addressed in the server. Thanks.

When it happens again, I'll send a log. Thanks

Same here, makes me sad Workaround: open emby on you cellphone, hit the shuffle there. But, you won't see the queued songs in the infotainment. Please add this feature.

Thanks for your replies, guys. I will have a look into those tools, especially if I can't manage to get it done the easy way. @Luke: Thanks for the info. I will try to do that this weekend.

Thanks for the response, Emby sent a new link and it worked.

Hi For those in community who like to know what EMBY is defining as an EMBYARTIST here is a sample purely for testing, please respect any digital rights of the band : 04 The Bomber_ Closet Queen _ Bolero _ Cast Your Fate to the Wind 2024-05-23.flac The above is a track from the "The James Gang Rides Again" I just take the tags from MB. MB follows the ID3 definitions. But anyone feel free to put the track in a tagger of your choice. @Luke@ebrperhaps you guys should tag it with what ever Tagging Tool Emby tests with Picard, MP3Tag, ? . The relationships that emby creates by grouping ..??. is Great, Not So great, OK, Poor, or pick your adjective. Don't really care. It is a user/customer choice and needs to be so

FYI this is available already in our Android TV, Fire TV and Roku apps.

Ok, yup, recording itself was a permissions problem. Still not quite sure why the initial add of the schedule didn't start until the following week, but it's such a relatively small thing for me that I don't need to pursue it at the moment. Thanks!

Yeah, that's something I'll try and see... Thanks all!

Cheers mate, you were right! - redid the XML and direct linked to the source rather than local and fixed it - highly appreciate the quick support and engagement you have with the Emby community @Luke - if only more platforms had dedicated SA's / Devs like yourself.

Hi there, what exactly happens when you try to connect? Where did you reset your password?

Not sure why would beta issues be discussed here? @jaycedkwas clear which server version he's running and all assumptions were based on that. But yeah, seeing same/lack of People tab in Search results on beta .20.

Is it possible to use the picture of the person specific to the content instead of the general picture? why? so it is easier to find the person you are looking for. If this is declined, is it possible to create it as a plugin with the existing api? or could there be support created? if so, could i get a few links with where i would need to search for getting the info like how do you create specific metadata for a specific media content i understand that this will increase the size so maybe make it togglable? i also think that it looks better with what you are looking at that it is all themed to the content, and there are probably also places where there is no specific image so a fallback is required Sorry, i think that a post for this feature already exists but i could not find it

I've been playing around with it. I think the issue is it crashes on exit; hence why it crashes on install, because it wants to restart. Logs attached. kodi.log

Short answer: Yes. It is here as well: https://github.com/Ghawken/FrontView

People tab missing is bug in current beta already reported.

ok, i'll play around with it some more on my Windows 11 setup

Would it not be a good idea to have a metadata option for music videos that is actually for music, so that if there's nothing available in a music video db it could be identified from a music db ?

I have a similar setup and reported this same issue many months ago, but no resolution from Emby devs.

Here I detect an error in log file : But I don't understand what it mean. I had try 5 different location including (/share/Public) but it's always the same result. EDIT (& SOLUCE) ! The path was not the problem. So it's more simple to keep the same path then "/volume0/usr/builtin/etc/certificate/ssl.pfx" After generating the pfx file, you just need to execute "chmod 644 ssl.pfx" and restart emby server So happy, all works well now !

I've been known to do the wrong thing when setting things up lol. Just so you know I unhooked my flex 4k and connected my hdhr duo in it's place. It shows up literally the same way as 2 flex 4k's.

That appears to be the problem - and the fix. Several years ago my playback was extremely poor, and I experimented with lots of things - obviously including that value. The problem turned out to be Windows backup (using file history) which was backing up all of the hauppauge intermediate files. That change was made years ago - the current problem only started months ago. Anyway, thanks for your analysis and perserverance.

May have been file system permission problem on my end. If tomorrow's doesn't record, I'll do the full report. Thanks!

@LessajSorry for the long delay, this device is Wifi, its not an ideal connection, but thats a pretty wild swing. I can try get some logs on a wired client also!

Or try one of these. https://github.com/linuxserver/reverse-proxy-confs/blob/master/emby.subdomain.conf.sample https://github.com/linuxserver/reverse-proxy-confs/blob/master/emby.subfolder.conf.sample

Emby 3.3.94 directly from here has definitely no issues with any of these Audio HD formats, did not notice any stuttering of video, but I only watched like 5 minutes of maybe 5 movies to check on the Audio, just got this box today, will investigate a little further.

I backed up my Emby Server, wiped it off my Mac Mini, and reinstalled and restored the backup and everything seems to be working smoothly now.

You don't necessarily have to wipe the old and start fresh - just setup another instance of emby, running on a different port - but pointing to the same same libraries. Let that scan the items in the background and when it's finished, then import the play state from the corrupt db - then move that over as the new instance. If you unlink all the items in the current db, then its possible that would suffice, but I would be concerned about what else is corrupt - there is no way of knowing unfortunately.

Hi there, sorry I’ve been away. Let me report it the next time it happens. Thanks

I thought I'd give it a go and submitted a PR: Add option to prefer movie.nfo when reading/writing nfo files by randellhodges · Pull Request #8 · MediaBrowser/NfoMetadata (github.com)

@LukeI will send you a PM.

Yes, Emby will play my TV recording now a and the transcoding settings have been fixed. I have other problems with playing recording like progress bar does not traveling across as the recording plays it stays at zero and if I try to jump ahead it starts over again at the beginning. So if I am at 10 minutes and I jump ahead the recording returns back to zero and plays from there. But I should probably start a new thread for this problem.

okay, found it: i chnged the systax in compose-yaml from - TZ:"Europe/Berlin" (syntax as in Luke's link above) to - TZ=Europe/Berlin (as i found it in another yaml running on my server) i wonder why docker does not throgh an error if there is something nonunderstandable but anyway, now it works

Why is there an undefined in the file location name on line 205 of the embyserve.txt? Did the backup folder not get setup in the filesystem?

Hi @juro1971 May I toss in a different installation for you? But first the USB drive. Raspberry PI OS full install auto mounts USB drives, so you can pop out and in drives without issuing a mount, but for safety you should issue a umount before disconnecting to ensure the file system is in a known state. I actually don't ever run the full OS, I only run Lite as I have no need for a desktop or mult-media support as I run headless, no monitor, no keyboard, no mice. ever. no, not even during setup. All of my PIs get a Lite Install, then I install docker/docker compose. My Emby runs as a container. So I have a folder on the host with all of the config files, and other folders for the media files. These are mounted onto file points within the Emby container when it starts. Installing the latest Emby container image is simply: docker-compose pull emby starting up and shutting down simply: docker-compose up -d docker-compose down From a fresh instance of the Raspberry Pi OS: # make sure all up to date ssh youruser@your machine sudo apt-get update sudo apt-get -y upgrade # make the container data folder sudo mkdir /mnt/emby sudo mkdir /mnt/media sudo chown 1000:1000 /mnt/emby sudo chown 1000:1000 /mnt/media # instal Docker sudo curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh sudo rm get-docker.sh sudo usermod -aG docker 1000 #exit, then log back in and ensure user 1000 can run: exit ssh youruser@your machine docker version # install stand alone docker-compose sudo curl -SL https://github.com/docker/compose/releases/download/v2.27.0/docker-compose-linux-aarch64 -o /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose sudo systemctl enable docker # do a network speed test docker run --rm robinmanuelthiel/speedtest:latest Here is what your docker-compose file would look like: services: emby: image: emby/embyserver_arm64v8 container_name: emby network_mode: host #network_mode: "service:gluetun" environment: - UID=1000 - GID=1000 - TZ=America/Toronto volumes: - /mnt/emby:/config - /mnt/media/television:/tvshows - /mnt/media/movies:/movies - /mnt/media/recordings:/recordings restart: unless-stopped If you also want to run Emby through a VPN like Nord to ensure privacy on streaming some channels.. then into that docker-compose file you can include the below and change the network_mode line above: gluetun: image: qmcgaw/gluetun container_name: gluetun cap_add: - NET_ADMIN network_mode: host environment: - VPN_SERVICE_PROVIDER=nordvpn - VPN_TYPE=openvpn # or wireguard - OPENVPN_USER=a_secret - OPENVPN_PASSWORD=another_secrret - SERVER_COUNTRIES=Canada # or somewhere else restart: unless-stopped To load up the config folder, you can start Emby with the /mnt/emby folder empty and it will create all configs fresh, you can then set up as required. There really isn't that much. after starting the container once, shut it down and copy over an existing config into the appropriate (and freshly made) folders. Note that from Emby's perspective, your data folders are all in the container's /. Containers are really the way to go, it simplifies everything you do on a Linux (or other) box. And backing up is simply backing up your docker-compose.yml file and your /mnt folder (or other path, some guys use /opt/ of /home/ and if you use docker volumes (I don't) they are in /var/lib/docker/volume. Hope this helps Daniel

@Luke

But why they are crazy power hungry. You are better of using a cheap android box.