gcoupe 63 Posted June 25, 2014 Posted June 25, 2014 I'm running the WP8 App version 8.0.61.0 against the Server version 3.0.5287.19943, and Music Albums are listed alphabetically only by the first letter, but not further. That is, all albums beginning with A are grouped together, as are all albums beginning with B, and so on. However, within a letter group, albums seem to be listed in random order. For example: V-N-X is not alphabetic... This is not happening with the Artists listing, only with Albums. It's also unique to the WP8 App, other Mediabrowser clients are displaying Albums in full alphabetic order.
ScottIsAFool 517 Posted June 26, 2014 Posted June 26, 2014 Could you raise a bug on github for me please.
ScottIsAFool 517 Posted August 28, 2014 Posted August 28, 2014 This will be fixed in the upcoming release.
Solution ScottIsAFool 517 Posted September 11, 2014 Solution Posted September 11, 2014 This is in the 8.0.62.0 release that just got published, update should be live in the store shortly. 1
gcoupe 63 Posted September 12, 2014 Author Posted September 12, 2014 (edited) OK, thanks, the sort order is fixed, but the rest of the App is now giving me problems. Having authenticated again, the App now displays the entry screen with "getting server details" at the top for about 75 seconds before I see the "Views" screen. I've powered down the phone and tried again, with the same results. It also seems to take forever to start playing media (well, 90 seconds). Clearly something is not right. Perhaps I should just uninstall/reinstall? Edited September 12, 2014 by gcoupe
ScottIsAFool 517 Posted September 12, 2014 Posted September 12, 2014 Hmmm, odd, not had that reported from the beta. Might be worth a reinstall (although I appreciate that's a drastic fix if it works).
gcoupe 63 Posted September 12, 2014 Author Posted September 12, 2014 OK, uninstalled/reinstalled, and restarted the server. Same thing. The App spends 75 seconds getting the server app, and 90 seconds to open a media file for playing. Not seeing these symptoms on other apps connected to the server
ScottIsAFool 517 Posted September 12, 2014 Posted September 12, 2014 Can you clear out your logs on the phone (from the about page), close the app, then enter it again. If it takes that long again, go to the about page and send me the logs.
ScottIsAFool 517 Posted September 13, 2014 Posted September 13, 2014 Thanks, got it. It shows what I thought it would show, making the call to check the system info is taking a very long time to come back from the server. Out of interest, if you put http://<machinename>:8096/mediabrowser/System/Info?format=json into your browser, how long does that take to come back?
gcoupe 63 Posted September 13, 2014 Author Posted September 13, 2014 (edited) Immediate (in the Phone browser, I assume you mean); although it then asks me to install an app to read the json file... Edit: OK, so now I've installed a JSON viewer, and if I enter this URL into that then after a few seconds it gives me a 404 error... Edited September 13, 2014 by gcoupe
gcoupe 63 Posted September 13, 2014 Author Posted September 13, 2014 Here's what I get when I use that URL in my Desktop browser, with a JSON viewer installed: {"TranscodingTempPath":"C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\transcoding-temp","InternalMetadataPath":"C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\data\metadata","WebSocketPortNumber":8096,"HasPendingRestart":False,"Id":"76c30683770a4f84ac2b472942df706f","WanAddress":"(redacted)","ItemsByNamePath":"C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\ImagesByName","CanSelfUpdate":True,"FailedPluginAssemblies":[],"IsNetworkDeployed":True,"SupportsRunningAsService":True,"LogPath":"C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\logs","LocalAddress":"http://192.168.178.24:8096","MacAddress":"E0-3F-49-6D-1C-60","CachePath":"C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\cache","IsRunningAsService":False,"HttpServerPortNumber":8096,"CanSelfRestart":True,"InProgressInstallations":[],"SupportsAutoRunAtStartup":True,"OperatingSystem":"Microsoft Windows NT 6.1.7601 Service Pack 1","ServerName":"DEGAS","Version":"3.0.5366.22005","ProgramDataPath":"C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server","CompletedInstallations":[],"HasUpdateAvailable":False,"SupportsNativeWebSocket":True,}
gcoupe 63 Posted September 13, 2014 Author Posted September 13, 2014 Just wondering - is the Phone app trying to use the internet address instead of the local network address?
ScottIsAFool 517 Posted September 13, 2014 Posted September 13, 2014 Sorry, the reason for getting you to put that address into a browser was more to see how long it took, not what it returned and the app is using whatever you put in (I just omitted it from the post here, privacy and all that ). If you want to see if it's DNS related, try putting your server's IP address in instead of machine name.
gcoupe 63 Posted September 13, 2014 Author Posted September 13, 2014 OK, then the browser is working normal speed - I can use the Dashboard via the phone browser, and moving around in that proceeds normally. However, when I used the browser to play media, then I get the long pause before the media starts playing...
gcoupe 63 Posted September 14, 2014 Author Posted September 14, 2014 Sorry, the reason for getting you to put that address into a browser was more to see how long it took, not what it returned and the app is using whatever you put in (I just omitted it from the post here, privacy and all that ). If you want to see if it's DNS related, try putting your server's IP address in instead of machine name. OK, I've tried a new connection using the IP address instead of the server name. Same symptoms; the App spends 70+ seconds "getting server details" before the home screen appears, and takes 90 seconds to load media (e.g. to start playing a music track). Something clearly is not right.
gcoupe 63 Posted September 20, 2014 Author Posted September 20, 2014 I wiped all the profiles and created a new one using the IP address. This time, the client connects with the server immediately, and media loads quickly. So whatever the issue was, it seems to have been cleared. One thing, I'm running both IPv4 and IPv6 in my network. Perhaps that caused the issue?
ScottIsAFool 517 Posted October 3, 2014 Posted October 3, 2014 Possibly. I've seen an issue with Server 2012 R2 where instead of putting the machine name in normally, you have to do machinename.domain.local instead. So possibly the same kind of weirdness.
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