No need to apologise - my comment was intended to mean "please do be nitpicky" [not that your comments were too nitpicky]. With this new TV engine that we're working on, having the new features etc. will be cool... however if we don't make it easy to use and configure then basically nothing else matters. So again, I welcome your specific comments because this is what we need going forwards.Maybe this instruction could be re-worded?
Done. Better? (Please feel free to be nitpicky. )
Sorry for seeming 'nitpicky,'...
Yeah, setting up a capture device with MP has always been a difficult task. With the new TV engine I'm hoping to attempt to improve this in a couple of ways:This is amazing, after struggling with the HD-PVR to get high-def cable channels, this CableCard just blows it away.
I only list the files that you need to backup (from the base MP 1.x installation).There are more files in the ZIP for 1.4 than listed.
These logs are really strange. It is like all the fixes I applied from your previous testing are not included.OTA scan, Completed but did not grab the channel names
Pass. If the tuner says it is locked then that is what TV Server will report.Wow_Cable, Durring the scan I watched 84 thru 91 come up as Locked. Never seen that before.
I've seen this before in your previous logs. I think they must be VOD/PPV placeholders that share video and/or audio streams, or something like that.Freq 505250 found 48 channels... Somehow I dont think so.
The scan also did not find any of the channel names it normally finds.
If using the new code posted from last week on Post #1 was bad, let me know.
No problem! Thanks for taking the time to try the patch.Thank you so much mm for your work on this. It is great to be able to use CableCards with MP.
Excellent.Everything seemed to go well with installing, scanning for channels and even when I tested time-shifting and recording in the client.
I'm sorry, I don't understand what you mean by "releasing"... which means that you most likely haven't done anything wrong - more likely this can be explained by me not knowing exactly what I'm doing!I am having one issue though, in that the TV Server is not releasing the tuner when I stop time-shifting or even if it is recording and the recording concludes. The tuner is still going. It is not having the same behavior with Media Center. I am wondering if I did something wrong in the install or config process?
Thanks for explaining the terminology. It looks like what I really mean is the "stop" command.I'm sorry, I don't understand what you mean by "releasing"... which means that you most likely haven't done anything wrong - more likely this can be explained by me not knowing exactly what I'm doing!
From the code I can say that we create a connection with the tuner when it is first loaded, and we don't close that connection until the tuner is unloaded (usually when the TV service is stopped). When you timeshift and record, we send "play" and "stop" commands to the tuner as necessary. So maybe this connection that we don't close is what you're referring to.
Could you please clarify:
- What exactly do you mean by releasing?
The tuner light is still on and it can't be used by other clients. The tuner behaves as though it were still recording even though the recording has completed.
- How do you determine whether the tuner has been released or not?
- What effect does it have when TV Server doesn't release the tuner?
I'm far from certain that my terminology is correct. It is just the only way I know how to describe the code behaviour.Thanks for explaining the terminology. It looks like what I really mean is the "stop" command.
Right, okay.The tuner light is still on and it can't be used by other clients. The tuner behaves as though it were still recording even though the recording has completed.
- How do you determine whether the tuner has been released or not?
- What effect does it have when TV Server doesn't release the tuner?
Right, okay.The tuner light is still on and it can't be used by other clients. The tuner behaves as though it were still recording even though the recording has completed.
- How do you determine whether the tuner has been released or not?
- What effect does it have when TV Server doesn't release the tuner?
If we're locking the tuner like that it is not intended. It seems strange to me that keeping a connection open would prevent other apps from streaming... because we might just want to monitor the status of the tuner, and from memory I don't think we were able to do that unless we were connected.
I think I'm going to contact Silicondust and ask about this so I'm absolutely clear. In the meantime I've had a quick search and I found this comment:
http://www.silicondust.com/forum2/viewtopic.php?t=13754
So Jason is suggesting that is that the tuner is meant to remain locked for awhile by design. Are you able to perform the test that he suggested to confirm the tuner really is locked?