Narflex
commented
8 years ago This should likely be OK...all the CaptureDeviceManager implementations just need to be sure they don't replace the objects each time, but from looking at the code now it appears they are all doing this correctly.
On Mon, Aug 22, 2016 at 6:47 AM, Christopher Piper <notifications@github.com
wrote:
Currently, capture devices are only looked for during MMC's init, so if sage starts up faster than a network encoder, sage might not see the device. This is fine for already detected encoders that are in the sage.properties and configured, as those will be retried, but if it's a new encoder that has not been configured, it will not. There is a MMC.redetectCaptureDevices that was added at some time, but there is no API link to it. I'm looking for input on potential issues of adding an API function for this, and calling it when entering the source configuration screen in the STV.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/sagetv/issues/165, or mute the thread https://github.com/notifications/unsubscribe-auth/ANEIDEPq9rgWgsYm6LIK0hw-2qBauRYwks5qiaiMgaJpZM4Jp4mk .
Jeffrey Kardatzke jkardatzke@google.com Google, Inc.
Currently, capture devices are only looked for during MMC's init, so if sage starts up faster than a network encoder, sage might not see the device. This is fine for already detected encoders that are in the sage.properties and configured, as those will be retried, but if it's a new encoder that has not been configured, it will not. There is a MMC.redetectCaptureDevices that was added at some time, but there is no API link to it. I'm looking for input on potential issues of adding an API function for this, and calling it when entering the source configuration screen in the STV.