tdiguy 99 Posted March 10, 2018 Author Posted March 10, 2018 After you scaled it down,what the codecs show? same as before: Media Info Video CodecH264 Codec tagavc1 AVCYes ProfileConstrained Baseline Level50 Resolution720x404 Aspect ratio16:9 AnamorphicNo InterlacedNo Framerate30 Bitrate4153 kbps Bit depth8 bit Pixel formatyuv420p Ref frames1 NAL4 Title480P H264 Audio Languageeng CodecAAC Codec tagmp4a ProfileLC Layoutstereo Channels2 ch Bitrate127 kbps Sample rate44100 Hz DefaultYes TitleEng AAC stereo Default Containermp4 Path/media/emby/Movies/Kids stuff/101 Dalmations-1.mp4
tdiguy 99 Posted March 10, 2018 Author Posted March 10, 2018 lol @ 13th warrior is one of my favorites.
tdiguy 99 Posted March 10, 2018 Author Posted March 10, 2018 Thanks for the help on this guys Still seems weird to me that it was a media issue but that seems to be what it was.
Guest asrequested Posted March 10, 2018 Posted March 10, 2018 Just tested your movie with the beta app. It played without a problem.
Guest asrequested Posted March 10, 2018 Posted March 10, 2018 Is the emby beta not working well, for you?
tdiguy 99 Posted March 10, 2018 Author Posted March 10, 2018 Is the emby beta not working well, for you? Not really, for me live tv was freezing a lot. On emby stable its far more rare that it freezes up.
Guest asrequested Posted March 10, 2018 Posted March 10, 2018 I've had some momentary freezes with Live TV, too.
PrincessClevage 175 Posted March 10, 2018 Posted March 10, 2018 I am not sure why that would be blocked, i have no controls on my router for outbound traffic. The connection to the mi box is a bit curious. Pinging it from the emby box its better but not great. Pinging my router is in the fractions os ms. 64 bytes from 192.168.1.179: icmp_seq=40 ttl=64 time=2085 ms 64 bytes from 192.168.1.179: icmp_seq=41 ttl=64 time=1071 ms 64 bytes from 192.168.1.179: icmp_seq=42 ttl=64 time=47.7 ms 64 bytes from 192.168.1.179: icmp_seq=43 ttl=64 time=1555 ms 64 bytes from 192.168.1.179: icmp_seq=44 ttl=64 time=544 ms 64 bytes from 192.168.1.179: icmp_seq=45 ttl=64 time=275 ms 64 bytes from 192.168.1.179: icmp_seq=46 ttl=64 time=90.8 ms 64 bytes from 192.168.1.179: icmp_seq=47 ttl=64 time=1.81 ms 64 bytes from 192.168.1.179: icmp_seq=48 ttl=64 time=46.0 ms 64 bytes from 192.168.1.179: icmp_seq=49 ttl=64 time=75.9 ms heath@heath-desktop:/temp-1/out$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.393 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.295 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.263 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.285 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.280 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.303 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.350 ms using the wired adapter it seems to help a lot. PING 192.168.1.106 (192.168.1.106) 56(84) bytes of data. 64 bytes from 192.168.1.106: icmp_seq=1 ttl=64 time=1.43 ms 64 bytes from 192.168.1.106: icmp_seq=2 ttl=64 time=1.40 ms 64 bytes from 192.168.1.106: icmp_seq=3 ttl=64 time=1.34 ms 64 bytes from 192.168.1.106: icmp_seq=4 ttl=64 time=1.37 ms 64 bytes from 192.168.1.106: icmp_seq=5 ttl=64 time=1.37 ms 64 bytes from 192.168.1.106: icmp_seq=6 ttl=64 time=1.35 ms But now i cant bloody log into my emby server from the mi box even on the kids account that doesnt have a pw. Its saying invalid user when i select my kids account which is on the server. Not sure if this helps, but when i have emby use vlc to play movies 101 dalmatians starts up quickly. Something is seriously wrong with your wifi (assuming the first results are wifi)
tdiguy 99 Posted March 10, 2018 Author Posted March 10, 2018 Something is seriously wrong with your wifi (assuming the first results are wifi)All but 1 set of results there are with WiFi. Sent from my SM-G900P using Tapatalk
PrincessClevage 175 Posted March 11, 2018 Posted March 11, 2018 All but 1 set of results there are with WiFi. Sent from my SM-G900P using Tapatalk The first result has major impact 192.168.1.179 I would be check this destination from multiple source locations and starting with troubleshooting why reply have such huge latency. I have recently purchased a Linksys Velop wireless mesh system (3 node but only using two) and after some initial setup and teething problems it has been fantastic, amazing how many issues poor wifi was causing me.
tdiguy 99 Posted March 11, 2018 Author Posted March 11, 2018 (edited) The wifi unit i have is pretty nice, not exactly top of the line but its a lower end business class device. its the tp-link EAP225. My network is modem --> router --> 16 port switch. Everything except my ooma box connects to the switch directly. The ooma box connects direct to the router. I am checking out the settings in the AP but fwiw I am still not seeing response times in seconds, its ms so to reach a second it would be 1k ms. Still though the ping times to the mi box suck compared to the ping times to my router. In fact my laptop is connected to the same AP as the mi box and hell it reaches google.com with better results than my emby server reaching the mi box Pinging google.com [2607:f8b0:4004:811::200e] with 32 bytes of data:Reply from 2607:f8b0:4004:811::200e: time=24msReply from 2607:f8b0:4004:811::200e: time=26msReply from 2607:f8b0:4004:811::200e: time=26msReply from 2607:f8b0:4004:811::200e: time=26ms from laptop to mi box Pinging 192.168.1.179 with 32 bytes of data:Reply from 192.168.1.179: bytes=32 time=4ms TTL=64Reply from 192.168.1.179: bytes=32 time=70ms TTL=64Reply from 192.168.1.179: bytes=32 time=68ms TTL=64Request timed out. I tend to think its likely the mi box on this though. or, it could be i was over saturating the mi box, given proximity to the AP is about 10 inches. I just lowered the tx power on the ap and i am now seeing: 64 bytes from 192.168.1.179: icmp_seq=12 ttl=64 time=1.00 ms64 bytes from 192.168.1.179: icmp_seq=13 ttl=64 time=1.08 ms64 bytes from 192.168.1.179: icmp_seq=14 ttl=64 time=1.01 ms64 bytes from 192.168.1.179: icmp_seq=15 ttl=64 time=1.06 ms64 bytes from 192.168.1.179: icmp_seq=16 ttl=64 time=1.01 ms64 bytes from 192.168.1.179: icmp_seq=17 ttl=64 time=1.02 ms64 bytes from 192.168.1.179: icmp_seq=18 ttl=64 time=0.995 ms64 bytes from 192.168.1.179: icmp_seq=19 ttl=64 time=1.07 ms64 bytes from 192.168.1.179: icmp_seq=20 ttl=64 time=0.998 ms64 bytes from 192.168.1.179: icmp_seq=21 ttl=64 time=1.03 ms64 bytes from 192.168.1.179: icmp_seq=22 ttl=64 time=1.13 ms64 bytes from 192.168.1.179: icmp_seq=23 ttl=64 time=1.08 ms64 bytes from 192.168.1.179: icmp_seq=24 ttl=64 time=2.42 ms64 bytes from 192.168.1.179: icmp_seq=25 ttl=64 time=195 ms64 bytes from 192.168.1.179: icmp_seq=26 ttl=64 time=5.65 ms64 bytes from 192.168.1.179: icmp_seq=27 ttl=64 time=10.2 ms Edited March 11, 2018 by tdiguy
Guest asrequested Posted March 11, 2018 Posted March 11, 2018 Interesting. Mine is about 3ft from the AP, but the AP is set to auto for the power. Maybe you'll have less issues in general, now?
tdiguy 99 Posted March 11, 2018 Author Posted March 11, 2018 Interesting. Mine is about 3ft from the AP, but the AP is set to auto for the power. Maybe you'll have less issues in general, now? Maybe, lol i will have to get some time with the mi and test it out. I imagine it will be more responsive at the very least. Wish my ap had a auto option for power. But since 5ghz is kinda short range anyway i am lowering the power on that and leaving the 2.4 high to cover the house and a good part of the back yard.
tdiguy 99 Posted March 17, 2018 Author Posted March 17, 2018 reducing the power did help a little bit with the connection. I have also tested to my other mi box that is not on the beta firmware and i think that might also be playing a part. One thing i have noticed also with the beta firmware, there are options in this that are clearly meant only for cell phones, like the cellular data controls. So i wonder how well this firmware was expected to work on the mi boxes. This is the pings to my stock firmware mi box: 64 bytes from 192.168.1.163: icmp_seq=28 ttl=64 time=33.5 ms64 bytes from 192.168.1.163: icmp_seq=29 ttl=64 time=54.2 ms64 bytes from 192.168.1.163: icmp_seq=30 ttl=64 time=77.2 ms64 bytes from 192.168.1.163: icmp_seq=31 ttl=64 time=70.3 ms64 bytes from 192.168.1.163: icmp_seq=32 ttl=64 time=20.0 ms64 bytes from 192.168.1.163: icmp_seq=33 ttl=64 time=6.18 ms64 bytes from 192.168.1.163: icmp_seq=34 ttl=64 time=66.4 ms64 bytes from 192.168.1.163: icmp_seq=35 ttl=64 time=87.9 ms From the beta fw: 64 bytes from 192.168.1.179: icmp_seq=1 ttl=64 time=6.35 ms64 bytes from 192.168.1.179: icmp_seq=2 ttl=64 time=728 ms64 bytes from 192.168.1.179: icmp_seq=3 ttl=64 time=644 ms64 bytes from 192.168.1.179: icmp_seq=4 ttl=64 time=775 ms64 bytes from 192.168.1.179: icmp_seq=5 ttl=64 time=799 ms64 bytes from 192.168.1.179: icmp_seq=6 ttl=64 time=6.56 ms64 bytes from 192.168.1.179: icmp_seq=7 ttl=64 time=5.98 ms64 bytes from 192.168.1.179: icmp_seq=8 ttl=64 time=5.79 ms64 bytes from 192.168.1.179: icmp_seq=9 ttl=64 time=1.88 ms Not the best of test i will agree since they are connected to different access points ( though they are the same make and model AP and connect to the same switch ) but it does make me wonder. I am going to look around the web and see if there is a safe way to revert firmware.
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