[mythtv-users] converting mp4 and trans coding failing
Hika van den Hoven
hikavdh at gmail.com
Mon Nov 3 15:47:34 UTC 2014
Hoi Michael,
Monday, November 3, 2014, 4:19:28 PM, you wrote:
> On 11/03/2014 09:35 AM, Hika van den Hoven wrote:
>> Monday, November 3, 2014, 2:47:19 PM, you wrote:
>>
>>> On 10/30/2014 06:00 PM, Hika van den Hoven wrote:
>>>> Thursday, October 30, 2014, 10:52:36 PM, you wrote:
>>>>
>>>>> I your right I added this to /etc/local.conf the error went away
>>>>> LC_COLLATE=C
>>>>> LANG="en_US.UTF-8"
>>>>> LANGUAGE="en_US.UTF-8"
>>>>> I also added looses trans coding option in mythtv-setup and I will see if that helps.
>>>>> Is there script that will conver my recordings to mkv or mp4 and
>>>>> put them in proper folder based on show name and season.
>>>> I don't know, but it also complains about nl_NL.UTF-8 which it
>>>> shouldn't and all works OK.
>>> No, it is not complaining about 'nl_NL' and if it is complaining, all
>>> doesn't work OK (you just haven't tried doing the things that won't work
>>> with a bad codeset).
>>> The message means you haven't properly specified 'nl_NL.UTF-8' in the
>>> environment in which the MythTV application is running. So the first
>>> thing to check is that it's specified in the environment running (all)
>>> MythTV applications (i.e. the environment set up by your system start
>>> scripts/service and/or the environment set up by login for the user that
>>> (directly) runs MythTV applications or the environment set up by the
>>> script that runs the MythTV applications as the mythtv user (for example
>>> in a distro with a mythfrontend and mythfrontend.real)).
>>> If all looks good there, then you're probably specifying LANG as
>>> 'nl_NL.UTF-8', but also have LC_* variables set. The LANG environment
>>> variable is the old way that language (and to some extent, codeset)
>>> information was specified. However, since it's just one value, the
>>> modern approach of using LC_* variables (to allow specifying different
>>> values for different pieces) was developed. If you've specified
>>> LC_CTYPE (set directly or using LC_ALL) and specified LANG, the LANG is
>>> ignored since the LC_* variables are preferred. LANG is just a
>>> (basically deprecated) fallback when no LC_* variables are specified.
>> On gentoo I use eselect locale to set the language etc. I assume the
>> gentoo eselect utility sets it right. Also it was set on install, but
>> still I see all the time complaints in the log. I for a long time now
>> just ignore them, knowing it IS set right.
> Not knowing Gentoo, I can't say for sure, but I would presume that
> eselect is setting the locale settings for a specific user or all user's
> login environments. Many times applications--especially services--are
> executed in non-login environments (i.e. by shell scripts executed by
> init or similar). If that's the case, any MythTV application executed
> in such an environment (such as mythbackend, and all its child processes
> including mythfilldatabase and mythtranscode and mythcommflag and
> mythmetadatalookup and ...) won't have the "set for login environments"
> locale settings specified. Note, too, that if you're using sudo or su
> or ksu or similar, they almost always specifically exclude execution of
> login/profile scripts unless you explicitly request their execution by
> "simulating" initial login--i.e. sudo -i or su - or su -l or ksu -a -l .
> Mike
> _______________________________________________
I checked and both as root and as mythtv there is just a
LANG=nl_NL.utf8 variable. But now looking up I see up nl_NL.UTF-8,
which is what I set on generation of the locale, but on selection I
can among others select nl_NL.utf8 and en_US.utf8. So possibly MythTV
is not recognizing it while the system does!
Tot mails,
Hika mailto:hikavdh at gmail.com
"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"
De lerende Mens
More information about the mythtv-users
mailing list