Opened 9 years ago
Closed 4 years ago
#12388 closed Bug Report - General (Unverified)
UPnP, DVB .ts recordings and external 'transcoder'
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - General | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
This is essentially a continuation of #12181 and relates to changes introduced at v0.28-pre-2641-g487923f
For a long time I have used my mythDVBcut script instead of mythtranscode -m, mainly because its output files rarely give content-related problems within MythArchive?. This may now be true of mythtranscode; at present I don't want to switch.
It was simple to fix my script for the change to the .ts suffix, but the output didn't play via uPnP, which showed that its format was still MPEG2-TS.
The hack at #12181 didn't work. Currently a new mysql hack seems to be needed, like 'update recordedfile set container = 'MPEG2-PS' where recordedid =....'.
Other fields in that table are outdated too; I suppose that is what is implied in the closing comment of #12181
Change History (2)
comment:1 Changed 9 years ago by
comment:2 Changed 4 years ago by
Resolution: | → Unverified |
---|---|
Status: | new → closed |
Closing all old tickets in trac.
If your issue still persists, please open an issue in Github https://github.com/MythTV/mythtv/issues
and reference the existing trac ticket.
Before 0.28 is released there will be an extension to mythutil which will be able to inspect recordings and update the recordedfile table with any changes. Time permitting it may even be added as an automatic housekeeping task, but for changes caused by transcoding externally it will be best to call mythutil as part of your script.