On 8/19/07, Michael Beal [EMAIL PROTECTED] wrote:
No, that isn't what I ran into. Here's my freevo.conf:
[snip]
geometry = 1440x900
[snip]
Note the geometry line. The Panorama skin, built for anamorphic
display, _should_ have displayed itself properly but it didn't.
*No*, it shouldn't. As
On Sat, 2007-08-18 at 22:42 -0700, Michael Beal wrote:
On Aug 19, 2007, at 00:44, Michael Beal wrote:
All skin objects are positioned by hard-coded pixel-oriented
parameters. In other words, if you want something to be shown at
300 pixels from the left and 180 from the top, you set
Well further investigation leads me to believe that kaa.record is
needing modified
which I'm am attempting.is test/record.py up to date? or should i be
using something else for testing?
Thanks
Jonathan
On 8/18/07, Jonathan Isom [EMAIL PROTECTED] wrote:
Is there anything more that needs to be
[snip]
Sorry Michael I think you are misunderstanding this point, the base
skin resolution (normally 800x600) and the resolution in your
freevo.conf file are used to work out the ratio between the skin and
the actual screen.
[/snip]
Then the ratio calculations are faulty and need to be
Michael Beal wrote:
[snip]
The reality is this doesn't happen at screen resolutions over the
default 800x600. If I have my freevo.conf geometry at 800x600, choose
a skin built for 800x600 and do freevo -fs from the command line, I
get icons and images that are stretched. This is to be
On Sun, Aug 19, 2007 at 07:23:24PM +0200, Jean-Michel Sizun wrote:
Both cases feel perfectly explainable to me.
In the first case, you take a skin mean for a 4:3 screen with square
pixels and resize it to a 16:9 resolution, so it is normal things are
stretched.
I use the Bluestar skin in
On Sonntag 19 August 2007, Michael Beal wrote:
Then the ratio calculations are faulty and need to be addressed.
Michael, maybe it's just me, but I read a lot of unproductive criticism in
your postings. As long as you suspect others to poo-poo out ideas without
really understanding and
Andrew Flegg wrote:
On 8/19/07, Michael Beal [EMAIL PROTECTED] wrote:
No, that isn't what I ran into. Here's my freevo.conf:
[snip]
geometry = 1440x900
[snip]
Note the geometry line. The Panorama skin, built for anamorphic
display, _should_ have displayed itself properly but it didn't.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
KH KH Wrote:
Hi!
I'm packaging freevo for Fedora (6 and 7 and beyond)
It is available from my own repository for now,
but i plan to provide it to official Fedora repository,
as everything necessary to build freevo is here.
(tvtime will be
Hi!
I am a new freevo user who might be interested in a bit of development
work
also.
I have a picoLCD display hooked up to my freevo-box and want to be able to
use the keypads that is attached to it.
I have managed to get it working by modifying plugins/lcd.py but I'm
having
problems
Duncan-
I have found a plugin that is listed in local_config.py but unknown
by freevo. The video.reencode2 is in the local_config.py but freevo
does not recognize it. There are however 2 other reencode plugins:
video.reencode and video.reencode-old. Changing the name to from
reencode2 to
11 matches
Mail list logo
