Hi! Consider the scenario: - 2 devices, 1 used in transfer mode on transponder A - a new recording / streamdev session starts on transponder A
Now, IMO the correct thing to do is start the new receiver in the transfer-moded device, so that the second device is left free. However, the usual "use-already-tuned-devices" check in GetDevice() only checks for device->Receiving(), which does not report transfer-moded device, resulting in the new receiver being started on second device, thus both devices being reserved for receiving data from the same transponder. Attached is a patch for GetDevice() to check for transfer-moded devices as well. -- Anssi Hannula
diff -Nurp -x '*~' vdr-1.4.6/device.c vdr-1.4.6-f2/device.c --- vdr-1.4.6/device.c 2006-09-03 13:13:25.000000000 +0300 +++ vdr-1.4.6-f2/device.c 2007-04-21 05:58:38.000000000 +0300 @@ -292,7 +292,7 @@ cDevice *cDevice::GetDevice(const cChann // to their individual severity, where the one listed first will make the most // difference, because it results in the most significant bit of the result. uint imp = 0; - imp <<= 1; imp |= !device[i]->Receiving() || ndr; // use receiving devices if we don't need to detach existing receivers + imp <<= 1; imp |= !device[i]->Receiving() && device[i] != cTransferControl::ReceiverDevice() || ndr; // use receiving devices if we don't need to detach existing receivers imp <<= 1; imp |= device[i]->Receiving(); // avoid devices that are receiving imp <<= 1; imp |= device[i] == cTransferControl::ReceiverDevice(); // avoid the Transfer Mode receiver device imp <<= 8; imp |= min(max(device[i]->Priority() + MAXPRIORITY, 0), 0xFF); // use the device with the lowest priority (+MAXPRIORITY to assure that values -99..99 can be used)
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr