Jason Tackaberry wrote: > On Wed, 2005-08-03 at 11:23 +0200, Dirk Meyer wrote: >> I have no matroska files. Send me one (small) file and I will take a >> look at it. > > I put a couple short clips from Hide & Seek at > http://sault.org/~tack/mkvclips/ > > The aspect one stores the movie's aspect ratio in the matroska header. > The dsize one stores the display size. kaa.metadata should handle both > cases.
I never used matroska before (I didn't even wrote the parser). But I
hope to fix it this weekend.
>
>> > Of course, without software scaling, if we're playing a VCD that's
>> > 352x240, which gets expanded to 352x264, that means our OSD canvas is
>> > that big.
>>
>> And when freevo has a big image to show, it won't find with your
>> html-style. I would prefer dynamic resizing.
>
> I don't understand what you mean here. Can you give an example?
Sure. Everything in Freevo knows that the size is e.g. 800x600. Let's
say the osd plugin is writing you a message ("Encoding foo.avi is
finished"). This text is added to the canvas as an object with lets'
say a width of 400 (loooong text). You don't care about the message
and you start a movie (or you start at the same time as the text is
displayed). The text will be shown for the next 2 seconds, so it has
to move to the mplayer canvas. But when this canvas has a width of
less than 400, we have a problem.
And right now our current skin code uses absolute values. The skin is
designed for 800x600 and will scale when it is loaded to the real
resolution. So it wants to draw on position 700/100. It will be a huge
rewrite to adjust that.
The best way would be to have a 800x600 canvas for mplayer (or
whatever the resolution is) and scale it between evas and copying to
mplayer.
Dischi
--
I don't do drugs anymore 'cause I find I get the same effect just by
standing up really fast.
pgpcm5bgDA4LX.pgp
Description: PGP signature
