And i have no idea why restarting the PC does help with the problem, conceptually.Ĭode: Select all DEBUG 07:22:00.572 Matched media renderer "Android" based on dlna details "Vimu on AFTT 192.168.178.32 uuid:40bba8e6-f428-4652-b220-2034a5b35d22 GTVBox Vimu Player v4 Media player for Android TV" Sometimes its working like a charm, and just a few hours later, it stops working. What bothers me a bit is the irreproducibility. I am feeling i am THIS close to a fully satisfactory solution. Since the firestick is in use, UMS has recognized to new renderers which are running under nf and, respectively. Measurement directly next to the TV with my cell phone yielded WiFi bandwidths ~50-70 Mbit. The TV runs on IEE 802.11a/B/G and N, but sofar has never been a problem (and currently the Firestick is serving as the WLAN receiver, anyway, which is brand new). I have fairly new hardware (Ryzen 7 2700X) and a Fritzbox 6490 is running WiFi on IEEE 802.11ac, n, g, b, a. I tested this several times (recognize the stuttering, switch to the Samsung internal app, and play the same file). I should have mentioned that the stuttering only occurs with Firestick, i can play the files with the AllShare App on the TV itself just fine. Usually that isn't a problem on a home network, but older WiFi standards (pre ac) are known to be insufficient in some situations (depending on the content). UMS has to stick to something that the average computer can manage in real-time, which means much more bandwidth use. The streaming services have already encoded the videos in advance and just serves them, so they can afford to use much stronger compression. UMS requires much higher network bandwidth than the streaming services, because it has to transcode in real time. Anything less than 802.11ac could be problematic. It also depends on your router of course. I assume the Firestick use WiFi, but I don't really know what WiFi standard it supports. The crucial issue here, as I see it, is figuring out the stuttering. Don't do all kind of different things in one log though, it's just confusing. A log would reveal all these things, if you made a log while playing a file with one of these issues. I'm pretty sure that the subtitles issue is caused by the renderer configuration is use. There's really no reason why these shouldn't be able to do it just fine as long as UMS is configured correctly, unless they are bugged in someway of course - but that seems unlikely for three different applications. My guess is that there's no good renderer configuration for any of these "apps" in UMS, so things are running under "less than ideal conditions". I would have to know more about your setup to guess what is the most probable. The stuttering issue might be due to limited network bandwidth, or it might be because your PC isn't powerful enough to transcode the file in question. It shouldn't really matter what "app" you're running as long as it supports UPnP AV/DLNA. I can upload logs if you are willing to check why Firestick apps sometimes ignore subtitles. Turned out that my old Samsung via its Allshare App itself plays UMS content more reliably than the Firestick can.ĭo you have any advice, in terms of apps i can test or settings i can change in UMS? So far, my results have been far from spectacular. Vimu also has a horrible way to navigate through your files. Does not always find external subtitles, most often only after the hosting PC (not UMS!) is restarted, for unknown reasons. stutters randomly, but less severe than Airscreen. I tried several solutions to play UMS-hosted content via DLNA on said firestick:Īirscreen -> does find UMS. Recently, i bought a Amazon FireStick to replace the vastly outdated smart hub of my samsung E-series (alt TV). I am running UMS 9.0.1 (due to some recent subtitle problems on my Samsung MU, i downgraded UMS) on a Win10 64 Bit System.
0 Comments
Leave a Reply. |