Reinhard Nissl wrote:
> Hi,
>
> Petri Helin wrote:
>
>>> Please try the attached patch which adds VPID clipping to some locations.
>> I can gladly tell you that now there are several "00 00 01" blocks in
>> the sample.ts file. So something has changed to better. But for some
>> reason I am unab
Hi,
Petri Helin wrote:
>>> I am now also able to record h.264 encoded programs, just like mpeg2
>>> encoded, and as a result xxx.vdr files are created. But still, i cannot
>>> replay them either.
>>
>> Stock xine-lib-1.1.7 or higher can play those files. You may also want
>> to use vdr-xine-0.7
Hi!
I upgraded my VDR from 1.5.1 to 1.5.9 yesterday. Its work fine, but
I have a question:
In some channels I have the EPG with characters in ISO-8859-2. These
chars are replaced to '?'. How can I set EPG charset in VDR?
It would be useful an option in setup.conf - EPGCharset = ISO-8859-2
On 09/01/07 16:52, Boguslaw Juza wrote:
> Hi!
>
> I upgraded my VDR from 1.5.1 to 1.5.9 yesterday. Its work fine, but
> I have a question:
>
> In some channels I have the EPG with characters in ISO-8859-2. These
> chars are replaced to '?'. How can I set EPG charset in VDR?
> It would be usef
On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
> The character set is defined in the first byte(s) of the data that
> is broadcast for each string. VDR uses that information to convert
> that string to the character set used on your system.
Which function do this conversion and where?
On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
>
> On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
>
> > The character set is defined in the first byte(s) of the data that
> > is broadcast for each string. VDR uses that information to convert
> > that string to the character set used on your syst
On Sat, 1 Sep 2007, Stone wrote:
> On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
>> On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
>>> The character set is defined in the first byte(s) of the data that
>>> is broadcast for each string. VDR uses that information to convert
>>> that string to th
On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
> The character set is defined in the first byte(s) of the data that
> is broadcast for each string. VDR uses that information to convert
> that string to the character set used on your system.
Well, I found this piece of code and check returned charse
On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
>
> On Sat, 1 Sep 2007, Stone wrote:
>
> > On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
> >> On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
> >>> The character set is defined in the first byte(s) of the data that
> >>> is broadcast for each s
Gergely TAMAS wrote:
> Does someone have a patch which enables xineliboutput 1.0.0rc2 to work
> with vdr 1.5.9 ?
There's an official patch on the dev' web page:
http://phivdr.dyndns.org/vdr/vdr-xineliboutput/
(You'll need both, the 1.5.3 patch and the 1.5.9 patch)
Cheers,
Udo
Hi,
Reinhard Nissl wrote:
> the attached vdr-1.5.9-h264.patch adds H.264 support to VDR's remuxer.
After the above patch, my "sync early" patch fails to apply. Attached
you'll find an updated version which should apply cleanly.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
On 09/01/07 21:26, Boguslaw Juza wrote:
> On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
>
>> The character set is defined in the first byte(s) of the data that
>> is broadcast for each string. VDR uses that information to convert
>> that string to the character set used on your system.
>
> Well, I
On Sat, 1 Sep 2007, Stone wrote:
> When you do export LANG to pl_PL.ISO-8859-2, does VDR say the locale is
> recognized on startup?
I do:
export LC_CTYPE=pl_PL
Its enough - in vdr.c:
...
if (setlocale(LC_CTYPE, ""))
CodeSet = nl_langinfo(CODESET);
...
it sets CodeSet to "ISO-8859-2". And
13 matches
Mail list logo
