Opened 7 years ago
Closed 3 years ago
#13149 closed Bug Report - General (Trac EOL)
upnp Recordings menu complete, but only the most recent 19 will play
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | needs_triage |
Component: | MythTV - General | Version: | Master Head |
Severity: | medium | Keywords: | upnp |
Cc: | Ticket locked: | no |
Description
Yesterday I became aware of the v30 Ubuntu PPA builds, and upgraded from v29-40 to v30-Pre-197. The Ticket summary describes the problem. Earlier recordings get 'Cannot read file'. Panasonic TV. I am not certain that I had used upnp with v29-40 but it had worked in the recent past.
I had several obsolete thumbnail images in the folder, so I deleted all thumbnails. Only 19 of those for upnp have been regenerated.
I don't see this problem on my v30-Pre-65 el7 system, which has many more recordings.
Change History (5)
comment:1 Changed 7 years ago by
comment:2 Changed 7 years ago by
Doing things like
select title, starttime, recordedid, hostname from recorded order by recordedid limit 100 ;
shows that the short hostname was in use from 2015 until mid-September 2017, when I re-ran mythtv-setup.real in a different location; the earlier recordings are now playable by the frontend but not by upnp. I had imported two others into the el7 system using MythArchive? native mode, which preserves the original hostname, (and, I believe, the recordedid) and the same applies there. So it no longer looks to me if there has been a recent change in upnp playback. But ought upnp to be hostname-sensitive? The frontend isn't.
comment:3 Changed 7 years ago by
Did you select "Master backend override" in mythtv-setup? That will allow the master backend to stream files that were recorded on any backend, otherwise they only stream from the server where they were recorded. Maybe this option is being interpreted differently in upnp from the normal backend code.
If you rename a backend or frontend you should follow the procedure for that, documented in the wiki. It involves backup and restore of your database with an option for renaming a server.
comment:4 Changed 7 years ago by
"Master backend override" was not enabled but hasn't changed upnp. And yes, I have re-re-read "mythbackend migration" - but not yet done it. I'm afraid the change in hostname crept up on me.
Hmm. Output of mythbackend -v upnp. One name was system-generated, the other supplied by me during various attempts to get the system working. I suppose it's 'user error' and google will know about it, but suggestions would be welcome.