Hi,
in March 2011 1.9.2b2 was released. Will there be ever an usual release
of 1.9.2 or can the beta be considered as stable?
The reason for asking is that Arch Linux has 1.9.0 in their repos
because there is no 1.9.2 release. The maintainer is asking now if
there are any bugs in 1.9.2b2 so he s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.02.2010 11:41, schrieb Bjoern Franke:
> Hi,
>
> yesterday I tried to use the encodingserver to reencode tvrecordings
> after they have been recorded.
>
> But nothing gets reencoded and I get the following error message:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
yesterday I tried to use the encodingserver to reencode tvrecordings
after they have been recorded.
But nothing gets reencoded and I get the following error message:
Exception in thread Thread-5:
Traceback (most recent call last):
File "/usr/l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonsoir,
> I have installed freevo on my debian distro (unstable).
>
> I did configure the directories, the tv channels, and some mplayer options,
> but that's all.
> Freevo runs fine and I can watch live TV, browse EPG, and schedule
> recordings.
>
Hi Dischi,
> I do not think it ever did :)
However, some month ago it worked :)
> That happens if the disc reports subtitles and when kaa.metadata wants
> to read what kind of subtitles there are they are not available. Current
> kaa.metadata svn fixes that.
Thanks, I will install kaa.metadata
Hi,
my rf inferno - cell:nine-DVD is not detected by freevo any more:
2008-10-28 23:36:47,554 DEBUGrom_drives.py (445): Inserting disc in
drive CD-1
2008-10-28 23:36:53,766 DEBUGrom_drives.py (524): drive_status
changed 2 -> 4
2008-10-28 23:36:53,888 DEBUGTrying audio/cd
2008-10-28
Hello Duncan,
> Difficult to say from the description, you need to send some information
> about the TV card and how you have set up freevo to record.
>
> Consecutive recordings works quite well, the delaying only means that
> the pre-record interval is ignored. What hasn't happened is that th
Bjoern Franke schrieb:
> Hello,
>
> some months ago I had the same problem, but I don't remember how I fixed
> it.
> The freevo-webserver has problems with the german "Umlaute" in the
> TV.xml-file.
>
> Freevo is version 1.8.1, LOCALE in local_config.py
Hello,
some months ago I had the same problem, but I don't remember how I fixed
it.
The freevo-webserver has problems with the german "Umlaute" in the
TV.xml-file.
Freevo is version 1.8.1, LOCALE in local_config.py is set to iso-8859-15.
web.Server Traceback (most recent call last):
: 'utf8'
Bjoern Franke schrieb:
> Hello,
>
> since some weeks, this appears when I try to access the webinterface. I
> don't believe anything, but.,.. My box is running Freevo 1.7.3 (debian
> packages).
>
>
> web.Server Traceback (most recent call last):
The problem
Hello,
since some weeks, this appears when I try to access the webinterface. I
don't believe anything, but.,.. My box is running Freevo 1.7.3 (debian
packages).
web.Server Traceback (most recent call last):
exceptions.UnicodeDecodeError: 'utf8' codec can't decode bytes in
position 1-3: inva
Hi Duncan,
Duncan Webb schrieb:
>
> Have you run the tv_sort program on the TV.xml file, it usually fixes
> bad data files. Were there any problems before 2008? How I hate the
> crappy perl scripts that grab tv data they are always breaking.
>
Using tv_sort seems to fix this problem. Sorry f
John Molohan schrieb:
> Bjoern Franke wrote:
>> Hi Tanka,
>>
>> Tanja schrieb:
>>
>>> I have just checked and see the same problem in the webinterface.
>>> In the normal freevo interface everything works fine. The data is there in
>>
Hi Tanka,
Tanja schrieb:
> I have just checked and see the same problem in the webinterface.
> In the normal freevo interface everything works fine. The data is there in
> the xml file.
> It seems to be a problem of the webinterface...
Perhaps I should add this to the bugtracker?
> The reason
Hi Tanja,
> For now we did some googling and found another possible source: www.tvprog.org
> The data is not as extensive as the data from epgdata.com, but it is easy to
> get.
> It seems to origin from the dvb-t data stream itself and contains good data
> for the next
> 6 days for most of the i
On Wed, 30 Aug 2006 00:30:40 +0200, you wrote:
>I would like to know how should I configure the local_conf.py if I
>have a PIII 650. I mean, resolution, size to view TV, size to record
>TV, VCR_CMD (buffer,stereo??, video codecs, audio codecs) I have a
>SAA7134 card. Because I think I may not be a
On Sun, 09 Jul 2006 08:53:56 -0700, you wrote:
>So I have two questions. One, why is mplayer doing this, and can it be
>fixed. Two, if it cannot be fixed is there a way to make xine the
>default player for recorded shows only?
Perhaps you can take a look at the logs what mplayer does or yo
Hi,
some weeks ago I upgraded my freevobox to a Duron 750 with 384MB RAM.
The last three years I used lavc/mpeg4 for encoding in 320x240 from my
bttv-card. This codec produced large files, 1 hour = 500-600MB.
Now I tried xvid (also in 320x240) and the files are smaller.
I would rather like to us
Hello,
I run freevo since 2 years on a P3 450 with 256MB RAM and a gf2mx400.
The box is connected via composite to my TV and runs debian sid.
Recording TV and watching DVDs works fine, but sometimes the machine
slows down because it swaps around. A memory upgrade is not possible
because the mobo
On Sun, 28 Aug 2005 17:39:50 +0200, you wrote:
>The error comes when I try to download a plugin og a skin. The first
>line in the error is:
>
>Warning: fopen(files/Plugins/Freevo-Weather-0.8-nl.tar.gz.dlcnt): failed
>to open stream: Read-only file system
>in /home/groups/f/fr/freevo/htdocs/addons/
On Mon, 30 May 2005 21:12:01 +0200, you wrote:
>I am completely new to Python, what is wrong here?
>In which package is the module?
>
>Traceback (most recent call last):
> File "setup.py", line 16, in ?
> from util.distribution import setup, Extension, check_libs,
>docbook_finder
> File "
Hello,
after updating my debian-sid-system some strange things happen:
freevo records only damaged avi's.
I enabled CHILDAPP_DEBUG=1, but nothing is logged into
/tmp/freevo/recorder_stdout and _err.
excert from recordserver-0.log:
2005/03/24 22:17 CET [*RecordServer*] found a program to clean
200
On Thu, 17 Feb 2005 20:34:00 +0100, you wrote:
>> tv_grab_de_tvtoday grabs the data without error, but freevo always
>> says no channel data loaded.
>Did you removed the old TV.xml.pickled in /var/cache/freevo or /tmp/freevo ?
>If not, remove it, run freevo cache (not sure if it's neccessary) and
Hello,
freevo worked fine with the dumped XML-file from nxtvepg, but nxtvepg
does not work here any more. So I tried to use tv_grab_de_tvtoday and
changed the channel-ids in local_config.py.
tv_grab_de_tvtoday grabs the data without error, but freevo always
says no channel data loaded.
Any idea
>Thanks, I will give this a try. I am a little confused though.
>Everything I have been reading says that with a Composite connection you
>can only achieve 640x480i resolution. Also that PAL and NTSC can only
>do about 15 khz. From your configuration, it looks like you are
>achieving 800x600 an
On Thu, 15 Jan 2004 08:14:50 -0500, you wrote:
>recorded all crazy.. Is there anyway to speed it up??? Oh and how about
>sound , why did it not record sound?
>
You can set the recording device of /dev/dsp to e.g. line-in with the
command aumix -l R -l
HTH
bjo
--
ICQ# 12220433 | http://www.the
On Wed, 14 Jan 2004 18:35:51 -0800, you wrote:
>Well, I finally got the answer to my question about my Hitachi TV's scan rates.
>Since I am connecting to the TV using an S-Video cable, the horizontal scan rate is
>the standard NTSC at 15.75. Until I buy one of those nifty VGA to Component boxe
Hello,
I'm running freevo 1.4.1 and use the TV.xml-file dumped by nxtvepg.
After changing the syntax of the mencoder-call in the config-file
mencoder records now, but the recordserver calls it with the wrong
channel.
2004/01/12 05:09 CET [*RecordServer*] RECORDSERVER GOT EVENT NOTICE
2004/01/12 0
28 matches
Mail list logo
