[vdr] sourcecaps, vdr-1.3.36, and concurrent recordings
vdrgeorge at gmail.com
Sun Jan 8 01:49:52 CET 2006
Good evening Jeremy,
I don't know if this is true with the sourcecaps patch, but this deals with
recording priorities. It's my understanding that recordings have a default
(lower) priority and occur on secondary tuners.
Look at the vdr MANUAL regarding Primary limit; which states:
The minimum priority a timer must have to be allowed to
use the primary DVB interface, or to force another timer
with higher priority to use the primary DVB interface.
This is mainly useful for recordings that should take
place only when there is nothing else to do, but should
never keep the user from viewing stuff on the primary
interface. On systems with only one DVB card, timers
with a priority below PrimaryLimit will never execute.
Anyhow, I hope the above is relevant to your issue.
Thanks again for the start that you've provided by on occasion through your
id-disc topics and the several private emails over the past few years! I've
been hanging out with Cym and the fellas in #vdr for the past year and have
been enjoying helping others with vdr :)
On 1/6/06, Jeremy Hall <jhall at maoz.com> wrote:
> My sourcecaps looks like this:
> SourceCaps = 1 S1W S2W S3W S4W
> SourceCaps = 2 S1W S2W S3W
> Card1 is a budget card
> Card2 is a FF card and is PrimaryDevice.
> I was watching a channel on S4W, which meant the budget card was feeding
> the stream to the FF card for display. Normally when I record, I am
> watching the FF card directly, and when the recording starts vdr spins up
> the budget and tunes to the recording channel so that both cards are tuned
> to the same channel if I am watching the same chanel I am recording.
> Anything on S4 is unavailable while recording.
> When the event started on S2, I expected vdr to leave card0 alone and tune
> card1 (the ff card) to S2 and start recording from the FF card.
> Instead, my program on S4 was rudely interrupted, vdr switched to the
> recording channel, and refused to let me watch the S4 content.
> I tried a variety of cluges, including two timers, one on S2 and one on
> S4--that yielded about 30 seconds of content showing then vdr just died.
> Does anybody understand what might be going on?
> vdr mailing list
> vdr at linuxtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vdr