"NY" wrote
>"Jan Panteltje"  wrote in message
>news:pum4ct$t1m$1@dont-email.me...
>
>> If you however typed:
>> dvbstream  -c 0  -I 2  -qam 64  -gi 4  -cr 1_2  -crlp 1_2  -bw 8  -tm
>>   -f 562000  -o 8192 > /root/q1.ts
>> then you record the whole transponder (the whole transmitter content for
>> that frequency) to file /root/q1.ts
>
>Hmmm. That command, with various values of the f parameter for the
>frequencies of my transmitter's multiplexes, gives various error messages:
>dvbstream v0.7 - (C) Dave Chapman 2001-2004
>Released under the GPL.
>Latest version available from http://www.linuxstb.org/
>FRONTEND DEVICE: : Device or resource busy
>Tuning to 490000 Hz
>FE_GET_INFO: : Bad file descriptor
>dvbstream will stop after -1 seconds (71582788 minutes)
>Output to stdout
>Streaming 1 stream
>
>which look pretty fatal, but...
>
>
>I do actually get a recording of a different multiplex: whatever value of f
>I use (490 MHz is PSB3 - BBC1 and ITV HD) I always get mux COM7 (BBC News HD
>etc).
>
>
>That's with the command run under sudo.
>
>
>I wonder if the problem is that the Pi is running TVHeadend (though not
>actually tuned to anything) - might that be locking the tuner, and maybe the
>last time I used that decoder I'd tuned it to COM7.

Maybe type
 fuser  /dev/dvb/adapter0/frontend0

this should display a number, say NUMBER
then type
 ps avx | grep NUMBER
and that should show the process that uses your frontend0 (is the tuner)
If it is not dvbstream, then maybe that is TVHeadend?

Not sure how to stop that TVHeadend
but you could perhaps try
 kill -KILL NUMBER

and then run
 ps avx | grep NUMBER
again to see if it is now gone.

and then try dvbstream again.

If all else fails related to FE_GET_INFO, here is my old version of dvbstream:
 http://panteltje.com/pub/dvbstream-0.5.tar.gz


>What I have established is that the Pi can indeed record a whole T2 mux
>without getting its knickers in a twist.

Cool.

This is how I stream over my LAN (for one channel only).
On the PC with IP address 182.168.178.159 I type:
 while [ 1 ] ; do netcat -l -p 1233 | mplayer -cache 8102 -vf pp=0x20000  - ;
sleep 1 ; done

then do
 ssh -Y pi@192.168.178.75
to my rapy at 192.168.178.75
you will then need to do
 sudo su -
I suppose

and type (well actually it is a script)
 dvbstream  -c 0  -I 2  -qam 64  -gi 4  -cr 1_2  -crlp 1_2  -bw 8  -tm 8  -f
562000  -o 7011 7012 7013 | netcat 192.168.178.159 1233

and see the video / hear the audio in mplayer on the PC.

The 'while' on the receive end is needed to prevent you having to type the
commend every time if you change a channel for example,
control C exits that while.

That way you can record on the PC too (and not on the rapi SDcard), more space,
big harddisk...
 netcat -l -p 1233 > my_recording.ts
then watch timeshifted, in an other terminal:
 mplayer -cache 8102 -vf pp=0x20000  my_recording.ts

or record and play at the same time:
 netcat -l -p 1233 | tee my_recording.ts | mplayer -cache 8102 -vf pp=0x20000 
-

and then play the recording again later:
 mplayer -cache 8102 -vf pp=0x20000  my_recording.ts


Makes raspi into a TV box maybe some place in the window better reception...
I use an old bowty TV antenna in the attic to get very good DVB-T reception
here in the country.

There is a lot possible, netcat is one of the coolest things around,
works worldwide too :-)

Maybe if you have a more modern raspi you can stream the whole transport stream
to the PC?

--- SoupGate-Win32 v1.05