All Activity

These match that time code. ffmpeg-remux-83a0d006-5f8e-4d17-b882-bf8c5e2de737_1.txt ffmpeg-remux-562bfa10-c5ef-423e-99cb-f59758b28a9c_1.txt ffmpeg-transcode-ff911f90-b670-43b2-bb47-005298bc10cc_1.txt hardware_detection-63919966273.txt

See above where I say no CGNAT and static IP

@Neminemyou don't need to be a knob I’m only asking if others have done what I want to do with my hardware and what the best option are as there are many.

Hi, I'm on 4.10.0.20 (docker, linux) and i always used /emby/Items?Recursive=true&api_key=<apikey>&Fields=Path&Path=<encodeURIComponent(movie folder)> to find the movie within this particular folder. Now this isn't working anymore. Only using the full movie path works, so with the movie file included. Is this intentional? Or did something change ? Thanks

Think I will leave it alone - don't fancy the 30 day thing . Thank you

The usb is the latest.

Is (v2.2.8) the newest version or is the usb 30 day that frostbyte was talking about the newer one

Not sure if this has been answered. I'm using the latest Emby app on a FireTV cube (not the Emby for FireTV app) and when I play a movie I am getting a thin white line at the top of the movie I have also noticed this on TV episodes too. I am using the latest emby server as well. When I was using the the Emby for FireTV app I didn't not have this thin line. Any ideas on how to resolve this?

Interesting. Maybe there was a defect in that version, although I don't recall it being mentioned before.

The standard Android app which Henkmeister said is working for him. Search "Emb" in the store. That's the one Emby plans moving to in the future.

The first image is from my pc on edge browser & elvis movies are date added - the second is from samsung tv app under release date which I realise now they are not the same as next image - the third is from samsung tv under date added which should be the same as edge browser pic but as you can see not the same , EMBY is up to date server side

Hi, can you please show a screenshot example? Thanks.

The easiest and most painless solution is a static IP from your ISP. Otherwise, if your ISP is using a CGNat, then you'll need a VPN or TailScale.

Have you checked to see if your ISP is using a cgnat?

Ding ding ding. Yes this should be a post. They Emby app sends a post, so something in your stack is modifying the request. I would start by resolving that.

@ebr

The support article M3U Tuners has now been updated to cover the changes for the Referer / Referrer http header

The support article M3U Tuners has now been updated to cover the changes for the Referer / Referrer http header

Unfortunately, Android compresses the logs so I can't see the early playback behavior but, I think, this is the first thing that is happening: 07-18 10:12:58.139 7248 7248 I System.out: ***** Got error from Exo player: Response code: 404 07-18 10:12:58.139 7248 7248 I System.out: Playback error - Failed to load video 07-18 10:12:58.140 7248 7248 I System.out: Player error encountered - retrying ... which is quite odd - to get a 404 on a playback url. Can I please see the server log that includes those times?

Sorry all found the problem , my synology updated and removed port forwarding from the firewall inside synology and i was checking the router all the time. All seem to be working now

OMG! This finally works! I didnt do the extensinve testing, but i just updated the app, started and tried to play via glasses. All controils are in place and wokring! Thank you!

je precise que en DLNA mes fichiers audio .FLAC sont lu directement par la TV (je n'aime pas cette methode), avec jellyfin les .FLAC ne sont plus lu egalement I should point out that with DLNA, my .FLAC audio files are played directly by the TV (I don't like this method), whereas with Jellyfin, the .FLAC files don't play either.

HI, please try Emby for Android 3.5.39: Thanks.

HI, please try Emby for Android 3.5.39: Thanks.

HI, please try Emby for Android 3.5.39: Thanks.