The attached patch allows a VDR system with multiple cards to attach each card to an individual dish pointing at a different satellite.
I have 3 DVB cards in my VDR system:
1) FF card connected to one output of LNB at a dish pointed at Astra 19.2E.
2) budget card connected to another output of LNB at a dish pointed at Astra 19.2E.
3) budget card connected to output of LNB at a dish pointed at Eutelsat 13.0E.
I am using the following entries for that in my setup.conf:
SourceCaps = 1 S19.2E SourceCaps = 2 S19.2E SourceCaps = 3 S13.0E
On Sun, 04 Sep 2005 13:08:41 +0200, Carsten Koch wrote:
The attached patch allows a VDR system with multiple cards to attach each card to an individual dish pointing at a different satellite.
I have 3 DVB cards in my VDR system:
FF card connected to one output of LNB at a dish pointed at Astra 19.2E.
budget card connected to another output of LNB at a dish pointed at Astra 19.2E.
budget card connected to output of LNB at a dish pointed at Eutelsat 13.0E.
I am using the following entries for that in my setup.conf:
SourceCaps = 1 S19.2E SourceCaps = 2 S19.2E SourceCaps = 3 S13.0E
Can this be used with Diseqc? I have three DVB cards, distrbuted as follows
1) FF card connected to a Diseqc switch switching between S19.2E and S13.0E 2) budget card connected to LNB pointed at S28.2E/S28.5E 3) budget DVB-T card
So would this config work:
SourceCaps = 1 S19.2E S13.0E SourceCaps = 2 S28.2E S28.5E SourceCaps = 3 T
Aside from the SourceCaps approach, wouldn't a more logical system for VDR be to modify the sources.conf so that you had to indicate which card(s) was/were used for each source, e.g. ... S10.0E S13.0E 1 S19.2E 1 S28.2E 2 S28.5E 2 T 3
or in Carsten's case
S13.0 3 S19.2 1,2
That would then allow the CA field in channels.conf to be used correctly, since the assignment between the source and the cards available for that source would be defined in sources.conf. It would also mean that changing the allocation of channels to particular cards (e.g. after adding new cards that then changes the order in which cards are detected) would be a lot simpler than at present (where you have to edit every single channel in channels.conf).
Iwan
Iwan Davies wrote: ...
So would this config work:
SourceCaps = 1 S19.2E S13.0E SourceCaps = 2 S28.2E S28.5E SourceCaps = 3 T
I guess it should. Just give it a try and report back what happened. I am not the author of the patch, though. I have just made a few changes that Klaus requested and I ported the patch to the latest vdr.
Aside from the SourceCaps approach, wouldn't a more logical system for VDR be to modify the sources.conf so that you had to indicate which card(s) was/were used for each source, e.g. ... S10.0E S13.0E 1 S19.2E 1 S28.2E 2 S28.5E 2 T 3
or in Carsten's case
S13.0 3 S19.2 1,2
That would then allow the CA field in channels.conf to be used correctly, since the assignment between the source and the cards available for that source would be defined in sources.conf. It would also mean that changing the allocation of channels to particular cards (e.g. after adding new cards that then changes the order in which cards are detected) would be a lot simpler than at present (where you have to edit every single channel in channels.conf).
I had to make *no* changes in channels.conf to use the SourceCaps feature. The CA field could remain as it is.
Carsten.
Hi,
On Wednesday 07 September 2005 09:11, Carsten Koch wrote:
Iwan Davies wrote:
SourceCaps = 1 S19.2E S13.0E SourceCaps = 2 S28.2E S28.5E
This would be enough. SourceCaps are only valid for DVB-S at this time.
Aside from the SourceCaps approach, wouldn't a more logical system for VDR be to modify the sources.conf so that you had to indicate which card(s) was/were used for each source, e.g. ... S10.0E S13.0E 1 S19.2E 1 S28.2E 2 S28.5E 2 T 3
or in Carsten's case
S13.0 3 S19.2 1,2
This would have the same effect but just uses another syntax ;-) Lets Klaus decide how to implement this permanently.
That would then allow the CA field in channels.conf to be used correctly, since the assignment between the source and the cards available for that source would be defined in sources.conf. It would also mean that changing the allocation of channels to particular cards (e.g. after adding new cards that then changes the order in which cards are detected) would be a lot simpler than at present (where you have to edit every single channel in channels.conf).
I had to make *no* changes in channels.conf to use the SourceCaps feature. The CA field could remain as it is.
Exactly, I implemented the SourceCaps functionality at avoid any fiddeling with a CA field.
Carsten.
btw: Carsten, thanks for maintenance :-) I do not have much time for this at the moment.
On Thu, 8 Sep 2005 19:40:05 +0200, Christian Schuld wrote:
Hi,
On Wednesday 07 September 2005 09:11, Carsten Koch wrote:
Iwan Davies wrote:
SourceCaps = 1 S19.2E S13.0E SourceCaps = 2 S28.2E S28.5E
This would be enough. SourceCaps are only valid for DVB-S at this time.
S13.0 3 S19.2 1,2
This would have the same effect but just uses another syntax ;-) Lets Klaus decide how to implement this permanently.
I had to make *no* changes in channels.conf to use the SourceCaps feature. The CA field could remain as it is.
Exactly, I implemented the SourceCaps functionality at avoid any fiddeling with a CA field.
Carsten.
btw: Carsten, thanks for maintenance :-) I do not have much time for this at the moment.
Ah, ok - now I understand the idea of SourceCaps better - of course, my solution really amounts to the same as yours. I'd still vote for coupling the sources to resources in sources.conf rather than setup.conf though; it just seems more appropriate to me.
My thanks to Carsten and Christian for their efforts. Unfortunately having fairly limited experience in Linux I have to rely on others to do the complicated bits for me (viz. lirc, etc.), so I'm currently using the debian packages from e-tobi.net, in which the SourceCaps patch is not currently included. That's why I had to change the CA field when I added my DVB-T card.
I'll have to try to start configuring and compiling my own systems, but at the moment, my 3-year old and 1-year old seem more interested in grabbing the keyboard off me, and those Balamory recordings need to be accessible at all times, just in case.
Iwan