SolentUK 1 Posted March 31, 2021 Posted March 31, 2021 I'm thinking of making the switch from Plex to Emby, so I've been giving Emby a try. Same setup for both: HDHomerun tuner Server running on Windows 10 (Beelink SII mini PC) Chromecast with Google TV I'm finding that Plex is much quicker at playing live HD channels. Plex takes about 7 seconds to Direct Stream the channel (see below on the right). Emby takes 15-18 seconds to start playing - the dashboard begins by attempting to Direct Play, but then falls back to some hardware transcoding (see below on the left). I've fiddled with a few settings but I can't get Emby to perform any better. Any ideas?
Abobader 3464 Posted March 31, 2021 Posted March 31, 2021 Hello SolentUK, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team
Carlo 4561 Posted March 31, 2021 Posted March 31, 2021 Hi, the reason you're seeing different startup times is due to the transcoding taking place in Emby for that client. What we need to figure out is WHY it's transcoding. Is the Chromecast on the same LAN as your Emby Server? Can you play back the channel above and then upload the ffmpeg log file generated during playback? We can take a look at this and maybe give you a recommendation or two.
ebr 16185 Posted March 31, 2021 Posted March 31, 2021 My guess is an interlaced channel and that this will be solved by a combination of the next server and app update. But we should look at details to confirm. 1
rbjtech 5284 Posted March 31, 2021 Posted March 31, 2021 Yep - just tried this myself - ffmpeg log is showing it is interlaced. Using VLC as an external player plays it DirectPlay (instantly), but the output looks horrendous as it's clearly interlaced. To the OP - Does the Plex output look interlaced - ie very jaggy edges/lines on movement ?
Sammy 790 Posted March 31, 2021 Posted March 31, 2021 16 minutes ago, ebr said: My guess is an interlaced channel and that this will be solved by a combination of the next server and app update. But we should look at details to confirm. I'm thinking this isn't going to make it into 4.6.1.0..
ebr 16185 Posted March 31, 2021 Posted March 31, 2021 Just now, Sammy said: I'm thinking this isn't going to make it into 4.6.1.0.. You'd be incorrect as it is already in the beta. 1
Sammy 790 Posted March 31, 2021 Posted March 31, 2021 1 minute ago, ebr said: You'd be incorrect as it is already in the beta. Okay.. That fix. I was thinking of something else altogether..
SolentUK 1 Posted March 31, 2021 Author Posted March 31, 2021 The server and the chromecast are on different subnets (the chromecast is on a subnet for IoT devices) but I have specified both subnets in the LAN Networks setting ("192.168.3.0/255.255.255.0, 192.168.6.0/255.255.255.0"). The Plex setup is exactly the same. The ffmpeg log is attached. The picture looks fine in Plex - not jagged at all. That's how we've been watching TV for months now. ffmpeg-transcode-01f9485f-4459-49eb-ad43-41d63fb6fda2_1.txt
rbjtech 5284 Posted March 31, 2021 Posted March 31, 2021 24 minutes ago, ebr said: You'd be incorrect as it is already in the beta. Ah ok - let me test it in emby server beta .. subnets/vlan's will not make any difference - this is an interlaced issue which is forcing transcoding on the Release version ..
ebr 16185 Posted March 31, 2021 Posted March 31, 2021 Yep, it is a 1080i channel. The current release of the server is forcing this to transcode. The next release of the server and app will allow it to direct stream again. 1
rbjtech 5284 Posted March 31, 2021 Posted March 31, 2021 So on the latest emby server beta, Release FireTV Client, DirectPlay TV in the settings results in a spinning circle - no playback even starts (left for 1 minute plus). If I remove DirectPlay - then it starts to directplay, but then fails, failing back to transcode. The transcode reason looks to be the aac. Output looks interlaced ... it is not deinterlaced, same as the Release version. Log attached. ffmpeg-remux-96f9d777-7ffd-4f7e-acba-cc0b0d399494_1.txt
Sammy 790 Posted March 31, 2021 Posted March 31, 2021 3 minutes ago, rbjtech said: So on the latest emby server beta, Release FireTV Client, DirectPlay TV in the settings results in a spinning circle - no playback even starts (left for 1 minute plus). If I remove DirectPlay - then it starts to directplay, but then fails, failing back to transcode. The transcode reason looks to be the aac. Output looks interlaced ... it is not deinterlaced, same as the Release version. Log attached. ffmpeg-remux-96f9d777-7ffd-4f7e-acba-cc0b0d399494_1.txt 31.25 kB · 1 download What version of the AndroidTV app (FireTV app) are you using?
SolentUK 1 Posted March 31, 2021 Author Posted March 31, 2021 I also find that enabling Direct Play Live TV in the app settings stops the channel playing at all - just the spinning circle. App version is 1.8.55g on the chromecast.
rbjtech 5284 Posted March 31, 2021 Posted March 31, 2021 28 minutes ago, Sammy said: What version of the AndroidTV app (FireTV app) are you using? 1.8.55a Beta Emby Server, but release FireTV Client. I do have a Shield on the Beta Client which i can test if we need both the beta server and beta client ?
Carlo 4561 Posted March 31, 2021 Posted March 31, 2021 If running the beta server you will want to upgrade the clients to the latest beta as well which will allow direct play of Live TV. 1
rbjtech 5284 Posted March 31, 2021 Posted March 31, 2021 (edited) 23 minutes ago, cayars said: If running the beta server you will want to upgrade the clients to the latest beta as well which will allow direct play of Live TV. Nope - latest Beta Server, latest Shield Beta - only one HD channel Direct Plays - everything else is a constant spinning circle, or if I turn off Direct TV, it transcodes. I'm going to do some proper testing when I get the chance - as for me personally, UK OTA HD TV channels via a HD Homerun have never worked consistently from one channel to the next but they all play perfectly if using the HD Homerun App. Edited March 31, 2021 by rbjtech
Carlo 4561 Posted March 31, 2021 Posted March 31, 2021 It might be another setting or two you might need to adjust. It's definitely direct playing for many of us who have been testing it including closed captions as well. PS My testing is limited to cable and OTA in the USA.
rbjtech 5284 Posted March 31, 2021 Posted March 31, 2021 I think it is channel related. I've never had any issues Recording, it's only live playback that seems inconsistent. I'll do some proper testing when I get the chance, and provide the sample .ts streams. AAC_LATM seems to be the main culprit in the transcode logs - so I'm suspecting that is also the reason it does not Direct Play.
Sammy 790 Posted March 31, 2021 Posted March 31, 2021 I have two channels of which I know don't play well on MiBox s. The latest beta server / app combinations have smoothed things up and allow CC's when transcoding with Allow Stream Copy unchecked in the LiveTV settings in the app. Load time for me is about 6 seconds or a bit longer, not over 10. If you don't want to force S/W transcoding in the app, make sure the Allow Stream Copy box is checked. This will give faster playback. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now