Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#11164 closed Patch - Feature (Won't Fix)

upnp lists no directory structure

Reported by: manwe@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - UPnP Version: 0.26
Severity: medium Keywords: upnp directory subdir structure list
Cc: Ticket locked: no

Description

the title says all. on every upnp-client (ps3,smartphone,pc all with different programs) i/we see tons of videos in only one big list. it's the same issue since v0.25, but there it wont be fixed due to the change of configuration and database.

the upnp is nearly unusable. thats why i've declared this ticket with severity:high.

i think i've located the problem in "./programs/mythbackend/upnpcdsvideo.cpp" near line 34. based on the code in "UPnpCDSRootInfo" i cant find any code for a 'list-file-system-directory-structure' feature.

someone needs to create new code here. i'm not able to do this.

(i'm very sorry of my rusty english, but hope you understand)

Change History (7)

comment:1 Changed 7 years ago by Raymond Wagner

Component: MythTV - GeneralMythTV - UPnP
Milestone: 0.26.1unknown
Resolution: Feature request without patch
Severity: highmedium
Status: newclosed

comment:2 Changed 7 years ago by manwe@…

Resolution: Feature request without patch
Status: closednew

This is NOT a feature request!

It works until version 0.24 Since version 0.25 it does'nt work. So it means its a "new implemented Bug" / "a destroyed feature".

Have you solved the Problem? - No - Why do you close this ticket?

comment:3 Changed 7 years ago by Raymond Wagner

Resolution: Won't Fix
Status: newclosed

When the UPnP server was converted over to Storage Groups and the Video Library's database tables, that code was completely rewritten, and the directory support you're requesting was never re-implemented. While a previous version of MythTV supported a tree view of the content, the current code never has, so whether or not this is a feature request or a bug is really a question of semantics.

Regardless, tying the UPnP server back into the directory structure is not the ideal, or planned, solution. Since the UPnP server now uses the Video Library's tables, and has access to the Video Library's metadata for the content, the planned solution is to incorporate the assorted metadata-generated views available in the frontend, one of which is uses the existing directory structure. Hardwiring this to the directory structure, as was the previous behavior, is at best a temporary stopgap solution.

comment:4 Changed 7 years ago by johanh.botha@…

I use the UPnP function of my TV to watch programs on the Mythtv server. Because everything is now one big list - including series, I can only see up to programs starting with D on my TV, and it is a lot of scrolling to get there. You may call it a feature request, but I see it as a serious bug. It is also a problem on my son's Windows notebook where he used VLC to connect. I have switched to a Plex Server on Linux with a XBMC client to get past this problem, but basically I won't be able to switch back until this "feature" has been fixed.

comment:5 Changed 5 years ago by srikantmarakani@…

I also think that this is a weird way to implement the upnp server and it makes it essentially unusable (unless your video database is really small). The directory structure (or something analogous using metadata) is essential for any decent sized video database.

comment:6 Changed 5 years ago by mpebsen@…

There seems to be a reoccurring thread here…

Many of us have a large video collection. This is further exacerbated by the fact that we don’t always want to use the Mythtv frontend to “see” all of the video files in our collection. I utilize a combination of Sony/Roku? like media boxes to serve the larger TV screens in the house and only use the myth frontend for my PC screen.

I believe that MythTV should (must) preserve the user directory structure created within the video and recordings storage groups.

comment:7 Changed 5 years ago by stuartm

So supply a patch, this is open source, if you want it, you write it.

Note: See TracTickets for help on using tickets.