> I tried setting the bframes to 3 and I got some shakiness back. I can't
> explain why, but 2 bframes seems like the magic number. Is it possible
> that
> bframes starts at 0? 0,1,2 then 2 bframes actually means 3?
>From the firmware api docs.
NameIVTV_API_ASSIGN_GOP_PROPERTIES
Enum151/0
I tried setting the bframes to 3 and I got some shakiness back. I can't
explain why, but 2 bframes seems like the magic number. Is it possible that
bframes starts at 0? 0,1,2 then 2 bframes actually means 3?
On 4/23/07, Justin Wetherell <[EMAIL PROTECTED]> wrote:
Maybe it was me but I'll try ch
Maybe it was me but I'll try changing the bframes around again and see what
happens.
On 4/23/07, Duncan Webb <[EMAIL PROTECTED]> wrote:
Justin Wetherell wrote:
> After further testing, it seems like it's a combo of aspect and bframes.
>
> Setting aspect to 2 and bframes to 3, REALLY makes the v
Dirk Meyer <[EMAIL PROTECTED]> wrote:
> video.change_stream('audio-en,video')? But we may not need it. If I
> specifiy audio for visually impaired people I get that stream if
> possible and normal audio if not. The stream should auto-switch to the
> maching pids.
Nice idea but I think it's not tha
Duncan Webb wrote:
> Radek Šťastný wrote:
>> Hello,
>> a bit updated cs po file against freevo-1 svn.
>
> Thanks Radek,
> Please add this as either a bug report or feature request in the tracker.
> https://sourceforge.net/tracker/?func=add&group_id=46652&atid=446895
>
>> PS: in one case I don't n
On 2007-04-23 15:49, Soenke Schwardt wrote:
>> | video = device.get_stream(channel, 'audio,video')
>> | text = device.get_stream(channel, 'teletext')
>
> As Alessandro already mentioned it's sometimes clever to choose a
> specific audio stream if multiple are available. Changing audio stream
> whil
"Soenke Schwardt" wrote:
> Hi!
>
> Following my brain dump while reading dischi's mail :-)
doing the same :)
> Dirk Meyer <[EMAIL PROTECTED]> wrote:
>> First we need to get the device. No idea what kind of device you need?
>> Just call get_device().
>>
>> | device = kaa.record.get_device('dvb0')
Hi!
Following my brain dump while reading dischi's mail :-)
Dirk Meyer <[EMAIL PROTECTED]> wrote:
> First we need to get the device. No idea what kind of device you need?
> Just call get_device().
>
> | device = kaa.record.get_device('dvb0')
How do I know that a 'dvb0' device is present?
| dev
Justin Wetherell wrote:
> After further testing, it seems like it's a combo of aspect and bframes.
>
> Setting aspect to 2 and bframes to 3, REALLY makes the video jumpy
> Setting aspect to 1 and bframes to 3, KIND of makes the video jumpy
> Setting aspect to 2 and bframes to 2, Still jumpy but no
On 2007-04-23 11:14, James Oakley wrote:
> The current xmltv.py uses cElementTree.
1.x does, yes. In kaa we are using xml.sax everywhere, and the
performance is quite acceptable. The main bottlenecks were never due to
xml parsing anyway. For my setup, Freevo 1.7 takes 7 minutes to
download and
On Monday 23 April 2007 9:11 am, Hans Meine wrote:
> Hi!
>
> I just read this note by Roman Yakovenko (on the c++-sig ML):
> > Recently I worked on performance. I believe Py++ is now 30-50% faster.
> >
> > The first improvement comes from pygccxml - standard XML SAX parser was
> > replaced with cEl
Hi!
I just read this note by Roman Yakovenko (on the c++-sig ML):
> Recently I worked on performance. I believe Py++ is now 30-50% faster.
>
> The first improvement comes from pygccxml - standard XML SAX parser was
> replaced with cElementTree iterparse functionality. The old parser is still
> ava
Dirk Meyer wrote:
>>And what I would like is to add an extra UI (using remote-control) for
>>the player's configuration (basicly to setup and test networking).
>
> You need that part of kaa that is not finished yet. Freevo 2.0 now
> uses kaa.mevas as gui engine, but it is too slow. There is kaa.
"Alessandro Decina" wrote:
> On 4/22/07, Dirk Meyer <[EMAIL PROTECTED]> wrote:
>> This is a proposal for the interface of kaa.record2. This is not
>> implemented yet, but if we agree to make it this way I will do
>> it. This doc does not cover how this is done in the internals of
>> kaa.record2.
>
On 4/22/07, Dirk Meyer <[EMAIL PROTECTED]> wrote:
> This is a proposal for the interface of kaa.record2. This is not
> implemented yet, but if we agree to make it this way I will do
> it. This doc does not cover how this is done in the internals of
> kaa.record2.
> Next we want some parts from tha
> Hi.
> Yesterday I set to record some video through ivtv.
> After some time I forget about this and start ivtv-radio.
> After some time I play record video - and understand that record radio
> (green screen video with radio station sound).
>
> ivtv record and ivtv radio must not run together.
> Ca
16 matches
Mail list logo
