Opened 13 years ago
Closed 12 years ago
Last modified 12 years ago
#11079 closed Bug Report - General (fixed)
nuvexport fail with mythtv 0.26 du to UTC change
Reported by: | Owned by: | xris | |
---|---|---|---|
Priority: | minor | Milestone: | 0.26.1 |
Component: | Apps - Nuvexport | Version: | Master Head |
Severity: | high | Keywords: | nuvexport |
Cc: | Ticket locked: | no |
Description
Hello
nuvexport do not work anymore after the mythtv 0.26 UTC change (nuvexport do not find the video record information in the database). As I am using mencoder for exporting, adding the UTC offset in export/mencoder.pm, mythtv/recordings.pm and nuv_export/ui.pm solve the problem
Thanks in advance, zeloise
Attachments (2)
Change History (9)
comment:1 Changed 13 years ago by
comment:2 Changed 12 years ago by
I've run into this as well...
I'm not sure that this fix is right though - arguably unix_to_myth_time is now wrong (myth_to_unix_time definitely is)
Try the attached two patches?
comment:3 Changed 12 years ago by
I'm not sure if these are right; have posted to mythtv-dev for comment
comment:4 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:7 Changed 12 years ago by
Milestone: | unknown → 0.26.1 |
---|
Note: See
TracTickets for help on using
tickets.
I too came across this problem, but I'm using ffmpeg. I'm no Perl expert, but I modified export/ffmprg.pm as follows to get it working:
At the top of the file:
Then, down at around line 182, where the $mythtranscode command is constructed:
So I added the lines that create the '@t' and the '$utc_offset_in_seconds' variables, at the start. Then I modified the '--starttime' parameter to take account of the UTC offset. This seems to work for recordings created both before and after the changeover from Daylight Saving Time.
I know it's not a definitive solution, but it might help others and provide someone more able with some help to create a proper fix.