Am 19.12.2012 10:36, schrieb EikeSauer@xxxxxxxxxxx:
clue how to accomblish this...
There's a define LIVEPRIORITY somewhere in the code. If you would
set it to MAXPRIORITY and recompile, you might get what you need.
Recorders couldn't claim the device used for live viewing becausethey
would have lower priority. Disclaimer: I didn't try it.
Ciao,
Eike
After a first test: it works. I have three devices - I started two
live-recordings and generated a timer within the next 3 minutes watching
a fourth transponder. When the timer should kick in nothing happens. So
far - so great.
But really nothing happens: no channelswitch - but also no conflict
warning or any info about not serving the timer. So this might be the
first step in direction to solve this (social ;) ) problem. Perhaps a
LIVEPRIORITY of 98 makes sense here, so that you can configure timers
that are more important then viewing live TV.
Klaus, I understand that you do not want to introduce more features
before 2.0 and I understand that this is a very marginal issue. But if
you have an idea, how to get vdr to spill a message about this
situation, I would be very glad if you could help us people with too
many timers out.
Regards, Ingo
diff --git a/config.h b/config.h
index 65e85bc..5d32d11 100644
--- a/config.h
+++ b/config.h
@@ -45,7 +45,9 @@
#define MAXPRIORITY 99
#define MINPRIORITY (-MAXPRIORITY)
-#define LIVEPRIORITY 0 // priority used when
selecting a device for live viewing
+//try to rserve 1 Device for live-TV exclusivly
+#define LIVEPRIORITY MAXPRIORITY // priority used
when selecting a device for live viewing
+//#define LIVEPRIORITY 0 // priority used when
selecting a device for live viewing
#define TRANSFERPRIORITY (LIVEPRIORITY - 1) // priority used for
actual local Transfer Mode
#define IDLEPRIORITY (MINPRIORITY - 1) // priority of an idle device
#define MAXLIFETIME 99
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
