Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#10116 closed Bug Report - General (Won't Fix)

Mythpreviewgen using wrong frame rate

Reported by: J.Pilk@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.24-fixes
Severity: medium Keywords:
Cc: Ticket locked: no


I'm in the UK recording dvb-t, SD. I added a call to mythpreviewgen, with no arguments, to my copy of mythcut projectx. The log reports the calculated position of the preview, in seconds, but the preview is actually created at a position (30/25 times this) seconds in ... or maybe it's 29.96/25.

Change History (4)

comment:1 Changed 9 years ago by danielk

Resolution: Won't Fix
Status: newclosed

If you provide a patch it will be looked at, but this doesn't really impact our use of mythpreviewgen so I'm marking it as wontfix

comment:2 Changed 9 years ago by J.Pilk@…

OK: I'll try to see what's going wrong, but it still produces a preview even if it falls off the eof, so wontfix is reasonable.

Log includes...Reading locale defaults from /usr/share/mythtvlocales/en_gb.xml

On the terminal there's a double slash between mythtv and locales but this gets eaten here by trac. Looks suspicious to me.

comment:3 Changed 9 years ago by J.Pilk@…

When I run previewgen in a terminal I see: Current locale EN_GB

/usr/share/mythtvlocales/en_gb.xml contains:

<setting name="Language">en_GB</setting>

and specifies UTF-8 encoding.

Typing 'locale' at the terminal produces:

$ locale



and so on. says:

The files are stored in the mythtv/locales/ directory. The naming scheme takes the iso_639-2 language code and the iso_3166-1 country code combining them into a standard locale string e.g. pt_BR, en_US. This should match your system locale as reported by locale (on linux). The files are given the suffix .xml.

There is clearly confusion in case-matching here: probably in the mythpreviewgen source code, and also in the names of the .xml files.

comment:4 Changed 9 years ago by stuartm

The locale stuff appears to be working correctly and in any case it has no relationship to the framerate used - that is always derived from the video itself.

Note: See TracTickets for help on using tickets.