View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011301 | MMA | UPnP / Casting | public | 2013-09-19 19:07 | 2014-12-02 15:05 |
| Reporter | marek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.1.0 | Fixed in Version | 1.1.0 | ||
| Summary | 0011301: Playback of large amount of upnp tracks | ||||
| Description | One user reported that his library stored on remote upnp server cannot be randomly played. There are two issues that has to be probably solved. 1. Limit somehow the size of now playing list because size of phone's memory isn't unlimited. 2. Loading of his playlist fails on connection timeout/ no response. There should be second attempt when upnp request fails. | ||||
| Additional Information | User report: <?xml version='1.0' encoding='UTF-8' standalone='yes' ?><Log timeStamp="2013-09-07 11:30:16" id="4KAS8TAKX1" userEmail="enigma0456@gmail.com"><message>crashes i want to randomly play my whole library 32000 tracks nexus 7 upnp iomega media server like I do with the pc version. Very glad you finally came to android. Let me know how I can help.</message><application version="1.0.4.0162" build="162" package="com.ventismedia.android.mediamonkeybeta" firstInstall="2013-06-29 11:58:14" /><device brand="google" model="Nexus 7" product="nakasi" model="Nexus 7" api="18" /><configuration orientation="1" dpi="213" screenHeightDp="880" screenWidthDp="600" /></Log> | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | |||||
|
|
1. it is quite solved by new way of storing the NP tracklist to DB in 1.1.0. So the OOME won't occur. But still a huge tracklist will be loaded to MMA. I don't know whether it is good have such no-limit operation. 2. It was already fixed by implementing common service class for UPnP |
|
|
1. I can't think of any alternative behavior that would make sense. One possibility is to limit what's loaded into the NP list to those tracks that are displayed in MMA OR set an arbitrary limit and indicate a toast message that 'x/y tracks have been loaded in the Now Playing list'. BUT that could be annoying as well and probably isn't what the user expects. Would it make sense just just load the NP list as a non-blocking background process? (currently MMA loads the NP list based on what was loaded into the UPnP tracklist view). |
|
|
1. Well ok we can leave it as it is for now. But I probably don't understand. It is loaded in non-blocking background process. It is not related to tracklist view - because tracklist view doesn't show all tracks and it would to slow transfer the data to playback service. From tracklist view we use only current, previous and next track to start playback asap. Other tracks are loaded separately from server with no relation to view. |
|
|
Verified in 1.1.0.344. 1. Non-blocking playlist loading functions as intended. 2. previously fixed. |
