View Issue Details

IDProjectCategoryView StatusLast Update
0007879MMW v4Otherpublic2011-06-06 04:08
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version4.0 
Target Version4.0Fixed in Version4.0 
Summary0007879: No way to browse 'all' collection content via UPnP
DescriptionWhen 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?
TagsNo tags attached.
Attached Files
bug.elf (60,520 bytes)
Fixed in build1383

Activities

Ludek

2011-05-26 10:12

developer   ~0025651

Last edited: 2011-05-26 10:12

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

jiri

2011-05-26 10:20

administrator   ~0025652

Agreed, let's add 'All' node to each shared collection.

Ludek

2011-05-26 12:50

developer   ~0025654

Fixed in build 1381.

lowlander

2011-05-31 20:22

developer   ~0025819

Browsing All node in MediaMonkey (client) from same MediaMonkey (server) causes AV and crash (elogs send).

Ludek

2011-06-01 10:06

developer   ~0025827

Last edited: 2011-06-01 14:58

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.

lowlander

2011-06-01 16:29

developer   ~0025841

Last edited: 2011-06-01 16:30

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.

lowlander

2011-06-01 17:51

developer   ~0025853

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).

Ludek

2011-06-01 19:14

developer   ~0025857

You are right, I am able to reproduce it with a very big DB.

Ludek

2011-06-01 20:54

developer   ~0025864

Fixed in build 1383.

lowlander

2011-06-03 18:39

developer   ~0025905

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.

jiri

2011-06-05 18:43

administrator   ~0025936

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.

rusty

2011-06-05 19:02

administrator   ~0025937

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.

rusty

2011-06-06 04:08

administrator   ~0025945

Verified 1384.