Freevo - Media Centre Platform

Bart Heremans wrote:
> Hi,

Hi,

> I'm trying to set freevo with a pvr350 card using the IVTV record
> plugin.
> 
> DEBUG=1 is set in the local_config.
> I'm using the freevo and mmpython cvs version on gentoo. python 2.3.3
> 
> This is the first error I get when using the ivtv record plugin :
> 
> --------------------------------------------------------------------
> 2004/07/06 18:25 CEST [*RecordServer*] vnorm: PAL
> 2004/07/06 18:25 CEST [*RecordServer*] Setting Input to 4
> 2004/07/06 18:25 CEST [*RecordServer*] Setting Channel to E9
> 2004/07/06 18:25 CEST [*RecordServer*] USING STANDARD FREQUENCY:
> chan="E9", freq="203250"
> 2004/07/06 18:25 CEST [*RecordServer*] Video Opened at /dev/video1
> 2004/07/06 18:25 CEST [*RecordServer*] Exception in thread Thread-1:
> 2004/07/06 18:25 CEST [*RecordServer*] Traceback (most recent call
> last):
> 2004/07/06 18:25 CEST [*RecordServer*]   File
> "/usr/lib/python2.3/threading.py", line 436, in __bootstrap
> 2004/07/06 18:25 CEST [*RecordServer*]     self.run()
> 2004/07/06 18:25 CEST [*RecordServer*]   File
> "/usr/lib/python2.3/site-packages/freevo/tv/plugins/ivtv_record.py",
> line 197, in run
> 2004/07/06 18:25 CEST [*RecordServer*]     if DEBUG: v.print_settings()
> 2004/07/06 18:25 CEST [*RecordServer*]   File
> "/usr/lib/python2.3/site-packages/freevo/tv/ivtv.py", line 146, in
> print_settings
> 2004/07/06 18:25 CEST [*RecordServer*]
> tv.v4l2.Videodev.print_settings(self)2004/07/06 18:25 CEST
> [*RecordServer*]   File
> "/usr/lib/python2.3/site-packages/freevo/tv/v4l2.py", line 314, in
> print_settings
> 2004/07/06 18:25 CEST [*RecordServer*]     print 'Driver: %s' %
> self.driver
> 2004/07/06 18:25 CEST [*RecordServer*]   File
> "/usr/lib/python2.3/site-packages/twisted/python/log.py", line 307, in
> write
> 2004/07/06 18:25 CEST [*RecordServer*]     d = (self.buf +
> data).split('\n')
> 2004/07/06 18:25 CEST [*RecordServer*] UnicodeDecodeError: 'ascii' codec
> can't decode byte 0xc4 in position 13: ordinal not in range(128)
> 2004/07/06 18:25 CEST [*RecordServer*]
> --------------------------------------------------------------------
> 
> in v4l2.py there are some print statements and I get a Unidecode error
> when setting these ptint statements in comment I can go on.

I am using a PVR-250 and started having the same problem a while ago 
after updating my driver.  Which version of ivtv are you using?  I tried 
messing around with Unicode and String objects but nothing really worked 
for me.  I was beginning to think that the driver is returning bad data 
or the interface has changed.  I ultimately ended up commenting those 
prints out (Driver, Card, Version).

> The second problem is NTSC <=> PAL.
> I am a pal user, ivtv driver is installed correctly I can capture
> without problems when I do cat /dev/video1 > somefile.mpg The result is
> a 720x576 mpeg file with sound. 
> 
> My pvr350 card is /dev/video1, /dev/video0 is a from the dvb card that
> isn't configured in freevo at the moment.
> 
> When capturing with freevo I get a 720x480 mpeg file.
> This are some lines from my local_config file
> 
> ----------------------------------------------------------
> TV_REC_SIZE = (720, 576)

Hmm, I think TV_REC_SIZE may be ignored by the ivtv code.

> IVTV_OPTIONS = {
...
>     'resolution'    : '720x576',
...
>     }
...

> 2004/07/06 18:35 CEST [*RecordServer*] Width: 720, Height: 480
> --------------------------------------------------------------------------
> 
> So the video standard is correct but the resolution is incorrect. AM I
> missing something ?

I don't think you're missing anything.  Maybe the setCodec interface 
hace changed slightly, the explicit set to '720x576' fails and it 
defaults back to NTSC resolution?  I should have a chance to take a 
closer look a bit later.

-Rob

On Tue, 2004-07-06 at 16:16 -0300, Rob Shortt wrote:


> I am using a PVR-250 and started having the same problem a while ago 
> after updating my driver.  Which version of ivtv are you using?  I tried 
> messing around with Unicode and String objects but nothing really worked 
> for me.  I was beginning to think that the driver is returning bad data 
> or the interface has changed.  I ultimately ended up commenting those 
> prints out (Driver, Card, Version).
> 

I'm using one with Chris Kennedys IVTV patches
http://kmos.org/~ckennedy/ivtv/ : ivtv-0.1.10-pre2-ck98p.tgz 


> > TV_REC_SIZE = (720, 576)
> 
> Hmm, I think TV_REC_SIZE may be ignored by the ivtv code.
> 

I thaught so, was just to be sure

> I don't think you're missing anything.  Maybe the setCodec interface 
> hace changed slightly, the explicit set to '720x576' fails and it 
> defaults back to NTSC resolution?  I should have a chance to take a 
> closer look a bit later.
> 
> -Rob

Thanks, maybe I will use another driver if I find one that works well
with 2.6 kernel, 0.1.9 won't compile

And another question, is it possible with the video groups to use more
than one tuner, a searched the mailing list but don't really know how to
set it up. there are three tuners in the pc

1) dvb-s haupage nexus
2) pvr350
3) bttv

didn't really try more than one at the moment because I'm already stuck
with the pvr350. (I got in wortking some months ago in my pc, now it is
in my brothers). the bttv card was working well alone, never used the
dbv-s card with freevo.

Hi,

ck ivtv patches are outputting this info when passing a ioctl
QUERYCAP_ST on the video device.

Driver: ivtvrÎàâÒÍóŒÄ
Card: Vanilla iTVC15 card qÎâ[À
Version: 266
Capabilities: 17236019
Enumerating supported Standards.
  0: 0x3000 NTSC
  1: 0xff PAL
  2: 0x7f0000 SECAM

In v4l2.py QUERYCAP_ST is defined like this.

QUERYCAP_ST  = "16s32s32sLL16x"
QUERYCAP_NO  = _IOR('V',  0, QUERYCAP_ST)

Not sure what to make of this mumbo jumbo ;-) Rob can you explain what
you are trying to do here with 16s32s32sLL16x ? Willing to help if you
got some pointers.

Bart, if you set DEBUG to 0 it doesn't try to print out the
QUERYCAP ioctl output and all should work as excpected.


     /Robert 

Tuesday, July 6, 2004, 6:31:21 PM, Bart wrote:

> On Tue, 2004-07-06 at 16:16 -0300, Rob Shortt wrote:


>> I am using a PVR-250 and started having the same problem a while ago
>> after updating my driver.  Which version of ivtv are you using? I tried
>> messing around with Unicode and String objects but nothing really worked
>> for me.  I was beginning to think that the driver is returning bad data
>> or the interface has changed.  I ultimately ended up commenting those
>> prints out (Driver, Card, Version).
>> 

> I'm using one with Chris Kennedys IVTV patches
> http://kmos.org/~ckennedy/ivtv/ : ivtv-0.1.10-pre2-ck98p.tgz 


>> > TV_REC_SIZE = (720, 576)
>> 
>> Hmm, I think TV_REC_SIZE may be ignored by the ivtv code.
>> 

> I thaught so, was just to be sure

>> I don't think you're missing anything.  Maybe the setCodec interface
>> hace changed slightly, the explicit set to '720x576' fails and it 
>> defaults back to NTSC resolution?  I should have a chance to take a
>> closer look a bit later.
>> 
>> -Rob

> Thanks, maybe I will use another driver if I find one that works well
> with 2.6 kernel, 0.1.9 won't compile

> And another question, is it possible with the video groups to use more
> than one tuner, a searched the mailing list but don't really know how to
> set it up. there are three tuners in the pc

> 1) dvb-s haupage nexus
> 2) pvr350
> 3) bttv

> didn't really try more than one at the moment because I'm already stuck
> with the pvr350. (I got in wortking some months ago in my pc, now it is
> in my brothers). the bttv card was working well alone, never used the
> dbv-s card with freevo.



> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
> digital self defense, top technical experts, no vendor pitches, 
> unmatched networking opportunities. Visit http://www.blackhat.com
> _______________________________________________
> Freevo-users mailing list
> Freevo-users@...
> https://lists.sourceforge.net/lists/listinfo/freevo-users

Robert Winder wrote:
> Driver: ivtvr=CE=E0=E2=D2=CD=F3=BC=C4
> Card: Vanilla iTVC15 card q=CE=E2[=C0

Yeah, that junk's causing problems.

> QUERYCAP_ST  =3D "16s32s32sLL16x"
> QUERYCAP_NO  =3D _IOR('V',  0, QUERYCAP_ST)
>=20
> Not sure what to make of this mumbo jumbo ;-) Rob can you explain wha=
t
> you are trying to do here with 16s32s32sLL16x ? Willing to help if yo=
u
> got some pointers.

Heh.  Ok, start by reading:

http://www.python.org/doc/2.3.4/lib/module-struct.html

We need to turn the results of the QUERYCAP_NO (really a hex number)=20
driver ioctl call into something python and understands.

     def querycap(self):
         val =3D struct.pack( QUERYCAP_ST, "", "", "", 0, 0 )
         r =3D fcntl.ioctl(self.device, long(QUERYCAP_NO), val)
         return struct.unpack( QUERYCAP_ST, r )

That function gives us a list returned by the ioctl.  Also note in the=20
struct pack line: "", "", "", 0, 0; a string, string, string, int, int.=
=20
    Well in C these tyles are more complec, and from reading the v4l=20
header file you can see the struct returned has members like 16 char=20
array, 2 - 32 char arrays, 2 - unsigned longs, and 16 bytes of padding.=
=20
  Ok, so this one probably doesn't ring a bell now because I just=20
remembered Thomas was the one who made this file, and I think that was=20
based on another project, so, perhaps the interface has changed.  Maybe=
=20
someone should review the v4l or ivtv header files and compare all the=20
struct packing/unpacking.  I will take a peek later perhaps but atm I'm=
=20
a bit busy.

-Rob

Just put any of the fxd files into any of your music directories.
They work with mplayer and 1.5RC4 (at least).

Kari

-----Original Message-----
From: freevo-users-admin@...
[mailto:freevo-users-admin@...] On Behalf Of Michael =
Osten
Sent: 6. hein=E4kuuta 2004 22:15
To: freevo-users@...
Subject: Re: [Freevo-users] FXD Shoutcast listings


What is the usage syntax for this?

Try taking the mplayer command that freevo runs (from
/tmp/freevo/main-501.log?) and run it on the command line. If you get =
the
same results remove mplayer options one by one (I think there's some =
post
processing done by default). When your happy with the playback put the
options in MPLAYER_ARGS_DEF. HTH

> -----Original Message-----
> From: freevo-users-admin@...
> [mailto:freevo-users-admin@...] On Behalf=20
> Of Andreas F=FCrtig
> Sent: 06 July 2004 15:23
> To: Freevo Maillist
> Subject: [Freevo-users] freevo plays video files very slow=20
> (xine and mplayer)
>=20
> Hi!
>=20
> i have a big problem:
> i have a pentium III 500 and 192 mb ram, archlinux with 2.6.7=20
> kernel and freevo version 1.5.0-rc4. when i try to start a=20
> video file with freevo (same error with mplayer 1.0pre4-3.4.0=20
> or xine 0.99.1), the video is very very slow, its like a slideshow :)
>=20
> when i try to watch a moove without freevo, only in my x=20
> (xfce4), then its running normaly!
>=20
> any ideas? you will find my complete freevo/local_config.py here:
> http://andieh.kicks-ass.net/upload/local_conf.py )
>=20
> thank you for your help!
>=20
> andreas fuertig
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
> digital self defense, top technical experts, no vendor=20
> pitches, unmatched networking opportunities. Visit=20
> http://www.blackhat.com _______________________________________________
> Freevo-users mailing list
> Freevo-users@...
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>=20

Hi,

VDR has support for teletext and teletext subtiles and I have written a
freevo plugin for vdr. It requires vdr with vdr_xine plugin and a
patched xine.

You can download it from the plugin page... it is called vdr_xine.py

/Ove

On Tue, 2004-07-06 at 12:44, Matthieu Weber wrote:
> I've just been browsing around searching for teletext (aka videotext)
> and DVB. There is an old program called dvbtext which gets teletext data
> from a dvb stream and saves it to files.
>=20
> Then we need a decoder:=20
>  - AleVT is a teletext browser which uses the /dev/vbi interface, but
> should also be able to read teletext data from files.
>  - alevtd is a Web server serving teletext pages as html documents,
> which should also be able to read from files.
>=20
> Both come from the xawtv package.
>=20
> Is there teletext support in Freevo? Someone interested in implementing
> something?
>=20
> Matthieu
> --=20
>  (~._.~)        Matthieu Weber - Universit=E9 de Jyv=E4skyl=E4         (~=
._.~)
>   ( ? )                email : mweber@...                  ( ? )=20
>  ()- -()               public key id : 452AE0AD                  ()- -()
>  (_)-(_)  "Humor ist, wenn man trotzdem lacht (Germain Muller)"  (_)-(_)
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
> digital self defense, top technical experts, no vendor pitches,=20
> unmatched networking opportunities. Visit http://www.blackhat.com
> _______________________________________________
> Freevo-users mailing list
> Freevo-users@...
> https://lists.sourceforge.net/lists/listinfo/freevo-users

On Tue 06.07.2004 at 01:23:09PM +0200, Ove Risberg wrote:
> Hi,
>=20
> VDR has support for teletext and teletext subtiles and I have written a
> freevo plugin for vdr. It requires vdr with vdr_xine plugin and a
> patched xine.

How do these ones work together? vdr gets the DVB data and xine reads
the data? Does xine display Teletext information? Will it work with a
"budget" DVB card (i.e. without the MPEG2 decoder and the OSD module)?

Matthieu
--=20
 (~._.~)        Matthieu Weber - Universit=E9 de Jyv=E4skyl=E4         (~=
._.~)
  ( ? )                email : mweber@...                  ( ? )=20
 ()- -()               public key id : 452AE0AD                  ()- -()
 (_)-(_)  "Humor ist, wenn man trotzdem lacht (Germain Muller)"  (_)-(_)

On Tue, 2004-07-06 at 14:14, Matthieu Weber wrote:
> On Tue 06.07.2004 at 01:23:09PM +0200, Ove Risberg wrote:
> > Hi,
> >=20
> > VDR has support for teletext and teletext subtiles and I have written a
> > freevo plugin for vdr. It requires vdr with vdr_xine plugin and a
> > patched xine.
>=20
> How do these ones work together? vdr gets the DVB data and xine reads
> the data? Does xine display Teletext information? Will it work with a
> "budget" DVB card (i.e. without the MPEG2 decoder and the OSD module)?

VDR gets the DVB data and the vdr_xine plugin sends the data via a named
pipe to xine (xine needs a patch from vdr_xine).

It will work with "budget" DVB cards... I use the vdr-streamdev plugin
to stream data from my VDR server to vdr with vdr_xine on my laptop ;-)

I am not sure if VDR or xine makes the OSD but it looks just like a
"full featue" DVB card.

To use teletext you need a vdr plugin called osdteletext.

My vdr-xine.py plugin starts the patched xine with the correct options
and makes the necessary key bindings. VDR has to be started separately
with at least "-P'xine -r'" as option...

>=20
> Matthieu
> --=20
>  (~._.~)        Matthieu Weber - Universit=E9 de Jyv=E4skyl=E4         (~=
._.~)
>   ( ? )                email : mweber@...                  ( ? )=20
>  ()- -()               public key id : 452AE0AD                  ()- -()
>  (_)-(_)  "Humor ist, wenn man trotzdem lacht (Germain Muller)"  (_)-(_)
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
> digital self defense, top technical experts, no vendor pitches,=20
> unmatched networking opportunities. Visit http://www.blackhat.com
> _______________________________________________
> Freevo-users mailing list
> Freevo-users@...
> https://lists.sourceforge.net/lists/listinfo/freevo-users

Matthieu Weber wrote:
> On Tue 06.07.2004 at 01:23:09PM +0200, Ove Risberg wrote:
>> Hi,
>> 
>> VDR has support for teletext and teletext subtiles and I have written a
>> freevo plugin for vdr. It requires vdr with vdr_xine plugin and a
>> patched xine.
>
> How do these ones work together? vdr gets the DVB data and xine reads
> the data? Does xine display Teletext information? Will it work with a
> "budget" DVB card (i.e. without the MPEG2 decoder and the OSD module)?

His plugin (and mine in WIP/Dischi, too) uses the xine plugin for
vdr. vdr puts the output to xine. This works even with budget cards. 


Dischi

-- 
Hidden DOS secret: add BUGS=OFF to your CONFIG.SYS

"module" is a general unix term, not a freevo term.

man lsmod
man modprobe
man insmod

lsmod | grep bttv
tail -n /var/log/messages &
modprobe bttv

mick
On Tue, 2004-07-06 at 10:29, Jon Morris wrote:
> The signal isn't the issue, a VCR hooked to the same cable works fine.
> =20
> As for the BTTV module, for my TV_DRIVER I was using V4L2.  This seemed t=
o work for a while.  When I changed that value to BTTV, I didn't even get t=
he blue screen.  Is there another way I should be loading the bttv module?
> =20
> Thanks,
> Jon
>=20
> 	-----Original Message-----=20
> 	From: freevo-users-admin@... on behalf of john molohan=
=20
> 	Sent: Sun 7/4/2004 6:12 AM=20
> 	To: freevo-users@...
> 	Cc:=20
> 	Subject: RE: [Freevo-users] Blue Screen...
> =09
> =09
>=20
> 	If the bttv module isn't loaded you would get this behaviour as well.
> =09
> 	On Sun, 2004-07-04 at 14:07 +0800, Mick wrote:
> 	> Maybe no arial signal?
> 	>
> 	> Mick
> 	>
> =09
>=20
> N=18HS^=E9=9A=8A[){([=19ZrA=DA=B4=1Ayj)

V4L2 should work fine with any 2.6 kernel, do a lsmod see if bttv module
is loaded. Can you view TV outside freevo using xzwtv or tvtime?

On Tue, 2004-07-06 at 03:29, Jon Morris wrote:
> The signal isn't the issue, a VCR hooked to the same cable works fine.
>  
> As for the BTTV module, for my TV_DRIVER I was using V4L2.  This seemed to work for a while.  When I changed that value to BTTV, I didn't even get the blue screen.  Is there another way I should be loading the bttv module?
>  
> Thanks,
> Jon
> 
> 	-----Original Message----- 
> 	From: freevo-users-admin@... on behalf of john molohan 
> 	Sent: Sun 7/4/2004 6:12 AM 
> 	To: freevo-users@... 
> 	Cc: 
> 	Subject: RE: [Freevo-users] Blue Screen...
> 	
> 	
> 
> 	If the bttv module isn't loaded you would get this behaviour as well.
> 	
> 	On Sun, 2004-07-04 at 14:07 +0800, Mick wrote:
> 	> Maybe no arial signal?
> 	>
> 	> Mick
> 	>
> 	
> 
> NHS^隊[){([ZrAڴyj)