All Activity

When I am back in the car later, I will try it again and submit an updated log

Hi @Lukeits v2.2.8 on my Samsung TV

I opened emby on my computer's web browser and tried uploading pictures in 5 different formats: jpg, png,webp,gif,apng Only jpg and png files can be uploaded - any other format just keeps looping and won't upload. Also, Apple TV won't display animated images. Are you going to fix this? 518.mov

Is this issue solved? I have the same problem so I do not upgrade the version to 4.9 or later.

had you spotted this scheduled task (id never clocked it before)....i wonder what it does..but it might have a part to play.

Also tried using the "external player" function in the Emby app. The sony "Media Player" app plays the h264 10bit video fine.

Thatś strange, I dont recognize this behevior. Iĺl check the log.

Oh, I see. I see, so the problem is somewhere else, I'll look for that. Thanks.

Added to the todo list.

I never really thought of that, i will add it to the to do list. Thank you for the suggestion!

Hello @Luke I tested one VOD with disabling extraction on the fly settings. Same behavior: subtitles (not forced) start to appear after 4 mns. I noticed something strange: on my others clients (PC, Smartphone): forced subs not appeared but not forced subs appear immediatly Here the logs embyserver.txt

Yeah, that's true. However, Vimu has been gaining a lot of traction lately because of its unique features. First, it offers flexible manual control over the pre-buffer size (the developer specifically optimizes the player for smooth online torrent playback via TorrServer). On top of that, it has a feature that was previously exclusive to Kodi: playing Dolby Vision Profile 7 as actual Dolby Vision by converting it on the fly to Profile 8 for MKV and M2TS files. Along the way, Vimu implemented advanced audio passthrough support and flexible conversion to AC3 or EAC3 for audio formats not natively supported by the TV box, all while preserving the multichannel layout. Honestly, I don't know of any other player that offers this kind of functionality while remaining so straightforward to configure.

Tried to transcode to h264 (x264) 10bit with handbreak. That has the same problem as the screenshot I posted earlier. Then transcoded to 264h (x264) not 10bit, that plays fine. Then transcoded to 264 (x65) 10bit, also plays fine. Already tried AV1 10bit before, that also played fine. So it does seem to be the specific combination of h264 + 10bit. But again, only in the Android app. The Android-tv app handles the video fine without transcoding, on the same device. When I look at the webinterface, while it plays the original h264 10bit version without problems in the Android-tv app, it shows:

Hi Team, I‘m really enjoying the WMC Beta and the progress made is amazing. The only thing I am missing are the APKs for Android which were there till some point. The idea to be able to enjoy my local media in WMC style, still being able to use my streaming services Apps on my Android device is awesome. Was there an announcement regarding the Android build I missed? Thanks

On Android Auto - it loads playlists and artists, but no albums or songs, I still have to click the album from the device to get them to load

@Luke To clarify, the issue isn't about standard guide data updates—it is a specific bug in how Emby processes the native HDHomeRun HTTP API (/lineup.json and /lineup_status.json). Emby’s network polling driver actually handles the hardware protocol brilliantly right now. When the tuner completes a scan and ScanInProgress transitions from 1 → 0, Emby instantly triggers an immediate background pull of /lineup.json to synchronize the lineup. The real issue is that this real-time background pull acts as a strict database upsert: Additions work perfectly: Newly added channels are injected instantly into the Live TV guide. Deletions fail completely: Channels that have been removed from the tuner's JSON payload are left behind as "ghost channels." Because Emby retains these defunct channels instead of clearing them out during the hardware sync, it causes severe channel overlaps and mapping conflicts in the guide. Currently, the only way to resolve these broken overlaps is to completely delete and re-add the HDHomeRun TV source. Since Emby is already doing the heavy lifting of monitoring the hardware flag and fetching the fresh JSON payload in real-time, matching the database state to the actual payload (dropping channels no longer present) would make the HDHR HTTP integration perfectly seamless. Appreciate you taking a second look at the database ingest side of this hardware handshake!

Awesome thank you

There's quite a bit of changes so I would suggest re-evaluating any issues you may have been having.

Hi, what version number of the app do you have installed?

The exact same video plays without problems on the Emby Android-tv app, without transcoding. Transcoding manually with handbreak to "AV1-10bit SVT" also lets the Android (not tv) app play the video. So yes, it should support 10bit video.

Not sure when it was added but i finally noticed it and it is more useful then i expected!! on a anime movie spree and super interesting to see as i go through them i watched them all 5 years ago, each one i pick, date last played 2021 hah thank you so much for adding it!

There is another Emby app in the Play Store (without "for Android TV"); it works with that one.

Does anyone who why I keep seeing the red box over the last 3-4 months like the one pictured? I had to power off my Samsung TV to make it go away. I’ve noticed this box pops up quite a lot. please help?

What does the new one fix?

It turned out to be a different problem. The Emby iPad app thinks remote (cellular) connections are remote connections. When you set these two playback settings (remote and remote (cellular)) as different values you can see it doing this in Stats for Nerds. I was changing remote (cellular) and it was not changing the bitrate, but not because of my original post but instead because it was following remote playback setting instead. Once I realized this I can see that my original post is not true, instead it is this problem with following remote playback settings when on remote (cellular) connection. I don't really see how uploading logs will help me show this since the different is seen in the app but if you want some please let me know what to collect. There is also an odd behavior where sometimes the app will show remote and remote (cellular) under playback settings and other times it will show only remote, when I haven't changed the connectivity. It was on remote (cellular) the whole time while I went out and back into the playback settings screen and the remote (cellular) setting kept disappearing and reappearing.