Hello,
I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no clue how to accomblish this...
Regards, Ingo
Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices.
Cheers Brian
-----Original-Nachricht----- Von: Ingo Prochaska nvertigo@gmx.de An: VDR Mailing List vdr@linuxtv.org Betreff: [vdr] Reserve device for Live-Tv Datum: Wed, 19 Dec 2012 09:54:21 +0100
Hello,
I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no clue how to accomblish this...
Regards, Ingo
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Am 19.12.2012 10:30, schrieb Brian_Dorling@t-online.de:
Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices.
And how can he use this DVB-C-Device then for Live-TV? He can only view the signal from one of the DVB-S-Devices that are locked to the transponder they are recording. Additionally for streamdev it is totally useless.
Gerald
!DSPAM:50d19286143496329019569!
On 19.12.2012 11:10, Gerald Dachs wrote:
Am 19.12.2012 10:30, schrieb Brian_Dorling@t-online.de:
Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices.
And how can he use this DVB-C-Device then for Live-TV? He can only view the signal from one of the DVB-S-Devices that are locked to the transponder they are recording. Additionally for streamdev it is totally useless.
Gerald
!DSPAM:50d19286143496329019569!
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi, I haven't tested this yet. But this solution was the one favoured by CT to solve the problem of the FF cards not having enough bandwidth to handle live viewing and recording at the same time.
The DVB-C FF card will never record in a DVB-S system. I assumed that you could view live TV via transfer mode from a DVB-S card.
I have a DVB-C FF card laid around here. Guess I need to try it.
I've never been in the situation that there was no DVB device left for live TV. But I do regularly miss bits of recordings, especially when they overlap.
Cheers
I ran into the same problem. My solution was to add another dvb card. When I hit that wall again, I added another. This is the easiest fix imo and doesn't require any patching. :)
Am 19.12.2012 16:51, schrieb VDR User:
I ran into the same problem. My solution was to add another dvb card. When I hit that wall again, I added another. This is the easiest fix imo and doesn't require any patching. :)
This is always the way to go.
Gerald
!DSPAM:50d1f3d8162281845871878!
Am 19.12.2012 15:11, schrieb Brian-Imap:
On 19.12.2012 11:10, Gerald Dachs wrote:
Am 19.12.2012 10:30, schrieb Brian_Dorling@t-online.de:
Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices.
And how can he use this DVB-C-Device then for Live-TV? He can only view the signal from one of the DVB-S-Devices that are locked to the transponder they are recording. Additionally for streamdev it is totally useless.
Gerald
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi, I haven't tested this yet. But this solution was the one favoured by CT to solve the problem of the FF cards not having enough bandwidth to handle live viewing and recording at the same time.
The DVB-C FF card will never record in a DVB-S system. I assumed that you could view live TV via transfer mode from a DVB-S card.
You didn't understand the problem. If this used DVB-S-Card will be needed by an recording it will again switch away from the live channel. And again, to use a FF-Card will not help with streamdev.
Gerald
!DSPAM:50d1f3b2162182740914572!
On 19.12.2012 18:04, Gerald Dachs wrote:
Am 19.12.2012 15:11, schrieb Brian-Imap:
On 19.12.2012 11:10, Gerald Dachs wrote:
Am 19.12.2012 10:30, schrieb Brian_Dorling@t-online.de:
Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices.
And how can he use this DVB-C-Device then for Live-TV? He can only view the signal from one of the DVB-S-Devices that are locked to the transponder they are recording. Additionally for streamdev it is totally useless.
Gerald
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi, I haven't tested this yet. But this solution was the one favoured by CT to solve the problem of the FF cards not having enough bandwidth to handle live viewing and recording at the same time.
The DVB-C FF card will never record in a DVB-S system. I assumed that you could view live TV via transfer mode from a DVB-S card.
You didn't understand the problem. If this used DVB-S-Card will be needed by an recording it will again switch away from the live channel. And again, to use a FF-Card will not help with streamdev.
Gerald
!DSPAM:50d1f3b2162182740914572!
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi, correct. Meaning, I didn't understand it properly.
Hello!
I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no 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
Am 19.12.2012 10:36, schrieb EikeSauer@t-online.de:
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
On 19.12.2012 13:52, Ingo Prochaska wrote:
Am 19.12.2012 10:36, schrieb EikeSauer@t-online.de:
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.
Well, since I won't adopt any such change (mainly because it makes things more complex than they already are) I'm afraid you're on your own here. You might want to look at
if (!cRecordControls::Start(Timer)) Timer->SetPending(true); else LastTimerChannel = Timer->Channel()->Number(); }
in vdr.c, where SetPending() is called. If you want to issue a message whenever a timer can't start, that might be a place to dig in.
Klaus
Hello,
Am 19.12.2012 14:02, schrieb Klaus Schmidinger:
Well, since I won't adopt any such change (mainly because it makes things more complex than they already are) I'm afraid you're on your own here. You might want to look at
if (!cRecordControls::Start(Timer)) Timer->SetPending(true); else LastTimerChannel = Timer->Channel()->Number(); }in vdr.c, where SetPending() is called. If you want to issue a message whenever a timer can't start, that might be a place to dig in.
yes, a first test shows it that works here. Then I've tried to check the code and the interaction between epgsearch (timerconflict) and vdr to implement a timerconflict warning on 2 different transponders (with 3 cards available) and stumbled over code I did not have a clue, what it does...
To come to an end (remember it's December, the 21st in 2012!), I decided to believe in "keep it simple", and just push the priority for live recordings and use the pausebutton for important broadcastings.
Thanx Klaus and thanx to everybody for the suggestions - if I decide to dig deeper in the "premature" timerconfict warning I will report.
Regards, Ingo
You should try the Primary DVB interface parameter. From the wiki : Defines the primary DVB interface (i.e. the one that will display the menus and will react on input through the remote control). Valid values range from '1' to the number of installed DVB cards.* If more than one DVB card is installed and a recording is to be started, the program will try to use a free DVB card that is different from the primary DVB interface, so that the viewer will be disturbed as little as possible. *
Marc.
On 19/12/2012 09:54, Ingo Prochaska wrote:
Hello,
I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no clue how to accomblish this...
Regards, Ingo
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 19.12.2012 09:54, Ingo Prochaska wrote:
Hello,
I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no clue how to accomblish this...
Why would you want that? It would deprive you of possible recording opportunities!
Klaus
Hello!
Why would you want that? It would deprive you of possible recording opportunities!
Some time ago, my girlfriend wondered why our box was switching to another programme and she couldn't switch back. A second recording had been started and both tuners where occupied.
I don't know how VDR handles this situation, but I liked what my old box, Gigaset M740AV, did: It asked the user for advice (not start the recording, stop one of the running recordings or switch live channel), and if he didn't react (so obviously no-one cared to watch live TV), it switched so it could do the recording.
Ciao, Eike
On 19.12.2012 11:22, EikeSauer@t-online.de wrote:
Hello!
Why would you want that? It would deprive you of possible recording opportunities!
Some time ago, my girlfriend wondered why our box was switching to another programme and she couldn't switch back. A second recording had been started and both tuners where occupied.
If you program that many timers, you obviously want them to be recorded. So you should let VDR make the most use of its available resources. Otherwise just don't set that many timers ;-)
I don't know how VDR handles this situation, but I liked what my old box, Gigaset M740AV, did: It asked the user for advice (not start the recording, stop one of the running recordings or switch live channel), and if he didn't react (so obviously no-one cared to watch live TV), it switched so it could do the recording.
"stop one of the running recordings" - yea right! Which one? Typical dialog:
He: "I wonder why that damned VDR recorded only half of the game last night?! Honey, did you mess with it?" She: "Well, I wanted to watch my soap opera and that thing asked me which recording it should interrupt. The choices were 'My other soap opera' and 'Some game'. Since I didn't care about the 'game', I chose that one." He: "!@@&%?#^@@@!!&%!!!"
You just can't win them all... ;-)
Klaus
Am 19.12.2012 11:37, schrieb Klaus Schmidinger:
If you program that many timers, you obviously want them to be recorded. So you should let VDR make the most use of its available resources. Otherwise just don't set that many timers ;-)
...only true, thats all single never rebroadcasted timers.
"stop one of the running recordings" - yea right! Which one? Typical dialog:
He: "I wonder why that damned VDR recorded only half of the game last night?! Honey, did you mess with it?" She: "Well, I wanted to watch my soap opera and that thing asked me which recording it should interrupt. The choices were 'My other soap opera' and 'Some game'. Since I didn't care about the 'game', I chose that one." He: "!@@&%?#^@@@!!&%!!!"
You just can't win them all... ;-)
Yes, you can... ;) Because secound soapopera is rescheduled later that night, you could have planed your timers mor socialcompatible and therefore you have made more out of your vdr-resources...
Regards, Ingo
Am 19.12.2012 11:11, schrieb Klaus Schmidinger:
Why would you want that? It would deprive you of possible recording opportunities!
Klaus
Eike pointed out one of the usecases. The other one: when I want to watch my favorite soccer-team live, I clean up the recording schedule and go for the game. While watching the game a searchtimer kicks in finding the deleted episode on another channel. My live view drops. While killing the newly generated timer Murphy accomplishes not only the one and only match-winning goal but also make me switch back after all replays had gone...
On the first view it deprive possible recordings, but in a world of repeated broadcastings, it give me the opportunity to better plan my recordings.
Regards, Ingo
On 19.12.2012 11:39, Ingo Prochaska wrote:
Am 19.12.2012 11:11, schrieb Klaus Schmidinger:
Why would you want that? It would deprive you of possible recording opportunities!
Klaus
Eike pointed out one of the usecases. The other one: when I want to watch my favorite soccer-team live, I clean up the recording schedule and go for the game. While watching the game a searchtimer kicks in finding the deleted episode on another channel. My live view drops. While killing the newly generated timer Murphy accomplishes not only the one and only match-winning goal but also make me switch back after all replays had gone...
If the game is so important to you, and you allow automated timers to be set at any time, you'd better set a timer for your game as well. This has the additional advantage of being prepared for any other interrupts, like phone calls, door bells etc.
Klaus
-
Brian-Imap -
Brian_Dorling＠t-online.de
-
EikeSauer＠t-online.de -
Gerald Dachs -
Ingo Prochaska -
Klaus Schmidinger -
Marc -
VDR User