On 21:03:29 Nov 11, Reinhard Nissl wrote:
> I recall this behavior when I had a FF card for testing. Maybe it's a
> feature to stop flickering one pixel high horizontal lines in still
> images by doubling one field of the frame. Maybe there exists a switch
> to turn this feature off.
>
> You've
En/na Reinhard Nissl ha escrit:
> Hi,
>
> Luca Olivetti schrieb:
>
>> Is it possible that newer version generate more traffic/are more
>> sensible to network latencies?
>
> Yes, at least in the buffer monitoring phase, which was introduced with
> 0.7.7. Try to set it to 0 in vdr-xine's setup me
Hi,
Luca Olivetti schrieb:
> Is it possible that newer version generate more traffic/are more
> sensible to network latencies?
Yes, at least in the buffer monitoring phase, which was introduced with
0.7.7. Try to set it to 0 in vdr-xine's setup menu.
I'll need some time to provide a proper fix
Hi,
Klaus Schmidinger schrieb:
>> Do you get the same jagged images when editing cutting marks? Most
>> likely such an I frame isn't larger than 40 KB.
>
> Yes, they are smooth for a brief moment, and then get jagged.
I recall this behavior when I had a FF card for testing. Maybe it's a
feature
Dear Fritz!Box- and VDR-Users,
a new version of the Fritz!Box Plugin is available at
http://joachim-wilke.de/index.htm?alias=vdr-fritz
- - -
The Fritz!Box Plugin connects to your Fritz!Box to inform you about
incoming calls. The plugin can automatically mute or pause VDR when a
call comes in.
V
On 11/11/07 17:29, Reinhard Nissl wrote:
> Hi,
>
> Klaus Schmidinger schrieb:
>
>>> But I still think that there is no need to repeat anything. Sending a
>>> progressive I-frame as still image should be sufficient, no matter what
>>> size the file has. Don't know whether the DVB-API has some limi
Hi,
Klaus Schmidinger schrieb:
>> But I still think that there is no need to repeat anything. Sending a
>> progressive I-frame as still image should be sufficient, no matter what
>> size the file has. Don't know whether the DVB-API has some limitations
>> regarding image size of still frames.
>
On 11/11/07 16:54, Reinhard Nissl wrote:
> Hi,
>
> Klaus Schmidinger schrieb:
>
>>> Hhm, if you set -n 3 for ppmtoy4m, mpeg2enc should detect, that there
>>> are no changes.
>> The command sequence I use now looks like this:
>>
>> pnmscale $S $TMP1 | \
>> pnmpad -black -width 704 -height 576
Hi,
Klaus Schmidinger schrieb:
>> Hhm, if you set -n 3 for ppmtoy4m, mpeg2enc should detect, that there
>> are no changes.
>
> The command sequence I use now looks like this:
>
> pnmscale $S $TMP1 | \
> pnmpad -black -width 704 -height 576 | \
> ppmntsc --pal | \
> ppmtoy4m -F 25:1 -A 4
On 11/11/07 16:05, Reinhard Nissl wrote:
> Hi,
>
> Klaus Schmidinger schrieb:
>
>> Looks like it is the file size.
>> I have now changed the line
>>
>> mpeg2enc -f 7 -T 90 -F 3 -np -a 2 -v 0 -o "$TMP2"
>>
>> to
>>
>> mpeg2enc -f 7 -T 40 -F 3 -np -a 2 -v 0 -o "$TMP2"
>>
>> so that the resultin
Hi,
Klaus Schmidinger schrieb:
> Looks like it is the file size.
> I have now changed the line
>
> mpeg2enc -f 7 -T 90 -F 3 -np -a 2 -v 0 -o "$TMP2"
>
> to
>
> mpeg2enc -f 7 -T 40 -F 3 -np -a 2 -v 0 -o "$TMP2"
>
> so that the resulting file is about the same size as yours, and now
> my im
On 11/11/07 15:45, Reinhard Nissl wrote:
> Hi,
>
> Klaus Schmidinger schrieb:
>
How does the attached PES file look like? In vdr-xine, I send it just
once and it looks OK in xine.
When it looks ok, I'll have to search for the commands which created it ;-)
I think, I
Hi,
Klaus Schmidinger schrieb:
>>> How does the attached PES file look like? In vdr-xine, I send it just
>>> once and it looks OK in xine.
>>>
>>> When it looks ok, I'll have to search for the commands which created it ;-)
>>>
>>> I think, I had specified an option to create progressive frames.
>
On 11/11/07 15:30, Klaus Schmidinger wrote:
> On 11/11/07 15:20, Reinhard Nissl wrote:
>> Hi,
>>
>> Klaus Schmidinger schrieb:
>>
>>> When I display a picture generated with this script through a call
>>> to DeviceStillPicture(), the display looks very nice for a short while,
>>> and after that sla
On 11/11/07 15:20, Reinhard Nissl wrote:
> Hi,
>
> Klaus Schmidinger schrieb:
>
>> When I display a picture generated with this script through a call
>> to DeviceStillPicture(), the display looks very nice for a short while,
>> and after that slanted lines get jagged. It appears as if the two
>>
Davide Cavalca ha scritto:
> Hello everybody,
> I've recorded some shows (with subtitles) with vdr 1.5.10, I wanted to
> demux the recordings with projectx but it looks like it has some
> problems coping with the new subtitles; the error is "suppic unknown
> cmd: 44"
Just tried with the last Proje
On 11/01/07 13:21, Stefan Huelswitt wrote:
> On 01 Nov 2007 Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
>> I'm looking for a method to convert a JPEG image to an
>> MPEG-2 I-frame that can be displayed through VDR's
>> cDevice::StillPicture() function. The conversion should
>> be done by a (seq
El Sábado, 10 de Noviembre de 2007, Reinhard Nissl escribió:
> Hi,
>
> Reinhard Nissl schrieb:
> >>> Though, a cleaner solution would be to fix the result buffer to allow
> >>> retrieving any packet as soon as it is completely available in the
> >>> buffer (final subtitle packets are about 100 byte
Hello everybody,
I've recorded some shows (with subtitles) with vdr 1.5.10, I wanted to
demux the recordings with projectx but it looks like it has some
problems coping with the new subtitles; the error is "suppic unknown
cmd: 44", a full log follows:
<<< session infos >>>
domenica 11 novembre 20
Hello all,
here's a proposal for speed control for vdr-dvd. It uses SG_IO and
GPCMD_SET_STREAMING so there's no need for VDR to run as root. The user
needs rw permissions on the drive, though. When the plug-in is
terminated the drive will be set to its initial speed (vacuum cleaner
mode).
The
20 matches
Mail list logo