Never mind. All it needed was a simple update of drivers!
Rather than just close the thread unceremoniously, hows about I describe
how to play and record simultaneously with dual DVB cards?
Right. Assuming your DVB is working and you know how to watch with one
card in freevo, do the following in the TV section of local_conf.py;
VIDEO_GROUPS = [
#VideoGroup[0]
VideoGroup(
vdev='/dev/video0', #For the benefit of lockfiles
adev=None,
input_type='tuner',
input_num=1,
desc='DVB Viewer',
group_type='dvb',
record_group=1),
#VideoGroup[1]
VideoGroup(
vdev='/dev/null', #For the benefit of lockfiles
adev=None,
input_type='tuner',
input_num=2,
desc='DVB Recording',
group_type='dvb',
record_group=None)
]
VCR_CMD = CONF.mplayer + ' -dumpstream -dumpfile %(filename)s
"dvb://[EMAIL PROTECTED](channel)s" '
This will use the second head to record (designated as dvb://[EMAIL PROTECTED]
) and
viewing will use the default head (being the first one). This is a much
better way to do this than I have previously, as it does not require
laborious modification to tv.guide.py or recordserver.py. The wiki
doesnt really have a good description of multituner support for dvb,
hopefully the above helps. I am looking forward to a smarter recordserver
that will allow simultaneous recording, and booting you off watching if a
recording is about to start on the last available tuner.
Please note that the above was done with a DVICO dual DVB-T. Unfortunate
side-effect of simltaneous use of the tuners is that signal quality
decreases significantly when both tuners are in use.
-Stygen
On Fri, 01 Jun 2007 08:12:09 +0800, Stygen <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> This may be slightly OT as it is not directly a Freevo problem. Hoping
> some experience on the list will provide the answer.
>
> I have setup many systems with the DVICO dual head DVB-T card, and they
> 'just worked'. The most recent one though, is behaving strangely. I
> suspect there is a permissions or a udev problem behind it, but cannot be
> sure. DMESG shows both heads as loading up nicely, and /dev/dvb is
> populated with both adapters. However, to illustrate the problem with
> tzap;
>
> scan -a /dev/dvb/adapter0 config --- works for the first head (PCI)
> scan -a 0 config --- also works for the first head (PCI)
>
> scan -a /dev/dvb/adapter1 config --- works for the second head (USB)
> scan -a 1 config --- does not work for the second heah (USB) !!!
>
> I suspect that whatever allows you to use the -a option with the device
> number rather than /dev/ location is what my problem is. When involking
> the individual cards you would do it as such : mplayer
> dvb://[EMAIL PROTECTED] and clearly this will work for the first
> adapter, but not the second (dvb_streaming_read, attempt N. 6 failed with
> errno 0 when reading 2048 bytes ... etc).
>
> If this rings a bell to anyone that can suggest how to fix it, I would
> most appreciative. Otherwise Freevo 1.7.2 appears to be using the dual
> head setup very effectively without having to modify tvguide.py or
> recordserver.py as I have had to do in the past.
>
>
> Many thanks,
>
> Justin
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Freevo-users mailing list
> Freevo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freevo-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
