|
|
This was alreadey reported / discussed as 0017555 -- so closing 0017555 and tracking it here. It is technically easier to make the separate config for the sub-nodes on the 'Shared Content' tab (preferred) than to take the MM4 approach. |
|
|
Additional information related to the impact that this has on client performance at 0018410 |
|
|
Impact of this issue; unable to serve large collection to TV set: MM4 setup * 48500 tracks * Collection type=Music, Classical Music and Title is Known * Subnodes: AlbumArtist, Album only * Columns: Title, Artwork, Album, Length, Path, Track# only TV experience: Can browse by either Album or Album Artist effectively (ie. there is a tree of starting letters for each, with individual album|AlbumArtist leafs) : can play music, see art, all works well) MM5 setup * same Tv * same tracks * same collection, nb MM5 can't customise columns being published (?) * TV experience: total fail, no browsing ... I get indices relevant to videos (Series, Director, etc) even though the collection contains only music tracks but all indices are empty of content, including AllTracks ... no error message no way to play anything MM5 setup with only 3,000 tracks: * works OK, same as MM4, except the UI is cluttered with indices that I tried to suppress at the collection level ... this works as expected when served from MM4 |
|
|
Additional comment from Barry: OK, but a heads up re deferral to 5.0.3 I tested MM5 in comparison to MM4: MM4: shared a Collection with 46+k tracks, configured collection to have minimal sub-nodes and columns ==> fully function in the TV ... can browse, can play music, and can see artwork in TV MM5: same Collection with same configuration (except columns, as n/a in MM5) ==> is broken in TV ... no browsing, no playing,, nothing except error message ("Too much content on this device to list it all") |
|
|
AFAIK the columns cannot be configurable even in MM4. Only nodes visibility can be configurable in MM4. So I don't quite understand what is the performance impact? @Barry: Can you clarify? |
|
|
I noticed that MM4 was able to serve my collection to my TV, but MM5 could not, due to "too much content". I have no visibility of the xml file that you export to the TV, so I looked at MM4|MM5 for configuration differences. The differences were: 1) In both Collections (MM4 & MM5) I had unchecked most of the Tree Nodes ... only 3 were checked ... MM4 respects this restriction, and MM5 does not 2) In MM4 I had also unchecked most of the columns in the Columns tab in the Collection Options panel ... this tab is AWOL in MM5 ... why? I don't whether #2 has any affect upon the volume of data that is published to the TV. It does have an impact upon what columns are available for display within MM itself. |
|
|
Implemented in 5.0.3.2600 Now visibility of all subnodes is configurable (either per client or per server) within the 'Shared Content' tab. As for the the Barry's problem with "too much content". I haven't noticed this problem on any of my clients, but I guess that this config should do the trick? [x] Show index for categories with many items [250] i.e. lowering the default 250 to something lower? |
|
|
image-2.png (33,778 bytes) |
|
|
Verified on 2600, user can customize which nodes can be shared over DLNA independently from Collection settings and this is seen by clients. |
- Anonymous
