![]() If it is on wireless then go to its network connection options and delete the connection. If it is connected wired then remove the cable. VERY IMPORTANT make sure your TV is off the network. I have some suggestions for your next test. I don't know what the 2nd unknown renderer is yet, the other one is a loopback test I think and around 700 is normal. The xbox is better but probably not ideal, but would be enough to overcome to the network spam from the TV. Renderer XBOXONE has an estimated network speed of 30.44228784631511 Mb/s Renderer Unknown renderer has an estimated network speed of 26.74284272376118 Mb/s Renderer Unknown renderer has an estimated network speed of 700.7744 Mb/s Renderer PlayStation 4 has an estimated network speed of 8.341913184584177 Mb/s Renderer LG LA6200 has an estimated network speed of 16.582101980707893 Mb/s I don't know anything about this communication but I noticed that the ID of that file is very largeĬode: Select all Renderer Windows Media Player has an estimated network speed of 86.89845333333332 Mb/s , ,, ,dc:creator, :cleartextSize,dc:date,upnp:genre,res,, ,upnp:albumArtURI,upnp:originalTrackNumber,upnp:album,upnp:artist,upnp:authorĬode: Select all The unescaped sent to 47LA6200-UA is: SOAPAction: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"ĭ: %5bTV%5d%5bLG%5d47LA6200-UA POST /upnp/control/content_directory HTTP/1.1 I don't know if UMS is trying to read these massive logs during normal operation/logging, but that would be a problem if it is and splitting log files would alleviate this.Ĭode: Select all Received a browse request from 47LA6200-UA (192.168.1.8:51770): You could even achieve this with the log.prev but adding a number every time that is being added to so you have separate files, log.prev1, log.prev2, etc. Log lines are date/time stamps, so it wouldn't be that difficult to cap log file size and make UMS start writing a new log at some point while using those time stamps to get different file names for each log. The massive logs is probably another issue that should be addressed. Did not verify when I played it on my Xbox One. I did make sure my TV was disconnected last time I tested it on my PS4. If it was a little glitchy then it may have been because the network spam from your TV was slowing it down or increasing I/O to your drives.ĭid you make sure that your TV was disconnected from the network? as I think something its doing could be the cause. If I remember, Suicide Squad was in a supported format for the PS4 so it should have been streamed, so it won't need as much bandwidth then it would if it was being transcoded. I'll see if I can split them into manageable chunks later to get an idea what is happening. It's trial period had run out anyway so I will need to set it up again from scratch. I tried to load them in my log viewer and my system ran out of memory and crashed. I think we have enough data from 1.5.0 at this point. I'm going to upgrade back to 1.8.2 now and see how things go. Since they are so massive I had to make a mega folder: ![]() Needless to say bad encoding would not surprise me at all.) The second, later log is from when stuttering started happening again, (it was a 1080p 50 min long video, which for some reason was nearly 3GB in size. There are 2 logs, the first log batch is from when I had the successful Xbox test. UMS froze/crashed while trying to save the latest log, so I had to manually zip it from the ProgramData folder. I have been growing the test library but it is still miniscule compared to my actual media library. So if I want to use headphones I have to use my PS4.)Īlso the logs are getting suuuuper big again and I just encoutered stuttering issues again with UMS 1.5.0. (The funny thing is the Xbox One is my preferred DVD/Bluray player/streaming device because the PS4 optical drive is cheap garbage, but I don't have the revised controllers that have the normal headphone jack. I did test that video on my Xbox One (since it support 5GHz wifi) and it played perfectly on my Xbox. There was that one Suicide Squad video that still played a little glitchy, buuuut a couple updates: It's one of the reasons we do this initial scan.Īnyway back to the problems, so Startropic1 are you saying that 10.5 works well for you but 10.6 onwards does not? I'm getting a bit lost in all the conversation Without it, each folder needs to parse its contents in realtime, which for folders that have thousands of files can lead to timeouts on the renderer. Also there are big speed advantages to having the initial scan run for ALL users, because it pre-populates the cache. The main ones I'm aware of like Plex and Serviio do it too. I think it's generally understood that media servers do these scans to keep up to date with the files. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |