View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007879 | MMW v4 | Other | public | 2011-05-25 20:49 | 2011-06-06 04:08 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 4.0 | ||||
Target Version | 4.0 | Fixed in Version | 4.0 | ||
Summary | 0007879: No way to browse 'all' collection content via UPnP | ||||
Description | When MM shares a Collection via UPnP, there is no node that displays all of the content that is being shared. e.g. if 'Music' is shared by MM UPnP server, and MM UPnP client browses that collection, then the Column Browser is displayed, however, it isn't populated because there are no nodes that display all of the shared tracks. Two possible approaches to fixing this: 1) UPnP server can add an 'All' node 2) UPnP server can populate the <collection> node (it's currently empty) Note: I'm not sure if the above are necessarily the best approaches--WMP seems to handle this at the client end (e.g. via an 'All Music' node)--perhaps that's a better approach? | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 1383 | ||||
|
I would prefer 1), i.e. adding the 'all' node otherwise it could cause some performance issues and wouldn't look good for clients that shows the structure like XBMC or iPhone's m-connect: [..] [Directory1] [Directory2] Item1.mp3 Item2.mp3 |
|
Agreed, let's add 'All' node to each shared collection. |
|
Fixed in build 1381. |
|
Browsing All node in MediaMonkey (client) from same MediaMonkey (server) causes AV and crash (elogs send). |
|
Could you please re-test with build 1382 whether it is still reproducable? If it is still reproducable with 1382 then please generate standard debug log using DbgView. I haven't been able to reproduce the AV and I also haven't found a reason for it. |
|
Yes, it still happens on 1382 (elog send). MM: opens first All node without crash, but no files, on switch to Location node > AV Samsung: fails to open All node with error message, returns to home screen, is no longer able to access MMserver, AV on MM close. Roku: fails to open all node, returns to previous screen, is no longer able to access MMserver, AV on MM close. |
|
It might be a list size issue. I'm seeing no issues when using the All node in the TV collection which only has a few files (also checked on Samsung). |
|
You are right, I am able to reproduce it with a very big DB. |
|
Fixed in build 1383. |
|
Verified in 1383. Could this be a user setting like the All node in MM itself. Preferably it's a setting per Collection as the All node is very slow on large Collections (thus better to be disabled) while still useful on small Collections. Otherwise a Media Server specific setting for showing/hiding the All node will do. |
|
Rusty, any preference on this? I wouldn't like to introduce any new string, particularly since it isn't clear what exactly is really needed. |
|
The requested config option to 'show all' is very different from the 'show all' option in the Library > Appearance settings, so for now, MM should just always add that node for DLNA (i.e. keep the two features separate). Since a new string is required, this will have to be treated as a separate feature post 4.0. |
|
Verified 1384. |