Reply to thread

Message

You're too kind! <blushes>

I don't think so. As far as I remember, I've seen that message in the logs for everyone using an ATSC/QAM tuner.

The logs are interesting. Both of those channels that you tested with seem to be on the same physical channel or frequency, and yet TV Server decides it needs to use both tuners. That is clearly not optimal. The indiscriminate continuity errors (suggesting recording errors) start during the second recording as suggested.

I think we covered this in the thread discussing the other problem, but to give a quick summary continuity errors are most often seen with:
- low signal strength/quality
- incorrect tuning parameters
- hard drive stress due to background scanning or OS and other apps also using the drive
- overheating hardware

Do you think any of these are likely/possible here?

Putting that aside for a moment, could you please try the attached patch. It should result in TV Server using the first tuner for both recordings. Haven't quite worked through in my head what this might tell us about the issue if it solves the problem, however it will be extra information regardless.
1. Stop the TV service in the "manual control" section of TV Server configuration.
2. Close TV Server configuration.
3. Take a backup of the TvLibrary.Interfaces.dll in your TV Server install folder (typically C:\Program Files\Team MediaPortal\MediaPortal TV Server on XP).
4. Download and extract the attached DLL into that same folder.
5. Open TV Server configuration again (you'll get a prompt that the service is not running - click yes to start the service) then try the test again.

mm

<blockquote data-quote="mm1352000" data-source="post: 888368" data-attributes="member: 82144">You're too kind! &lt;blushes&gt;&nbsp;I don't think so. As far as I remember, I've seen that message in the logs for everyone using an ATSC/QAM tuner.&nbsp;The logs are interesting. Both of those channels that you tested with seem to be on the same physical channel or frequency, and yet TV Server decides it needs to use both tuners. That is clearly not optimal. The indiscriminate continuity errors (suggesting recording errors) start during the second recording as suggested.&nbsp;I think we covered this in the thread discussing the other problem, but to give a quick summary continuity errors are most often seen with:- low signal strength/quality- incorrect tuning parameters- hard drive stress due to background scanning or OS and other apps also using the drive- overheating hardware&nbsp;Do you think any of these are likely/possible here?&nbsp;Putting that aside for a moment, could you please try the attached patch. It should result in TV Server using the first tuner for both recordings. Haven't quite worked through in my head what this might tell us about the issue if it solves the problem, however it will be extra information regardless.1. Stop the TV service in the &quot;manual control&quot; section of TV Server configuration.2. Close TV Server configuration.3. Take a backup of the TvLibrary.Interfaces.dll in your TV Server install folder (typically C:\Program Files\Team MediaPortal\MediaPortal TV Server on XP).4. Download and extract the attached DLL into that same folder.5. Open TV Server configuration again (you'll get a prompt that the service is not running - click yes to start the service) then try the test again.&nbsp;mm</blockquote>

[QUOTE="mm1352000, post: 888368, member: 82144"] You're too kind! <blushes> I don't think so. As far as I remember, I've seen that message in the logs for everyone using an ATSC/QAM tuner. The logs are interesting. Both of those channels that you tested with seem to be on the same physical channel or frequency, and yet TV Server decides it needs to use both tuners. That is clearly not optimal. The indiscriminate continuity errors (suggesting recording errors) start during the second recording as suggested. I think we covered this in the thread discussing the other problem, but to give a quick summary continuity errors are most often seen with: - low signal strength/quality - incorrect tuning parameters - hard drive stress due to background scanning or OS and other apps also using the drive - overheating hardware Do you think any of these are likely/possible here? Putting that aside for a moment, could you please try the attached patch. It should result in TV Server using the first tuner for both recordings. Haven't quite worked through in my head what this might tell us about the issue if it solves the problem, however it will be extra information regardless. 1. Stop the TV service in the "manual control" section of TV Server configuration. 2. Close TV Server configuration. 3. Take a backup of the TvLibrary.Interfaces.dll in your TV Server install folder (typically C:\Program Files\Team MediaPortal\MediaPortal TV Server on XP). 4. Download and extract the attached DLL into that same folder. 5. Open TV Server configuration again (you'll get a prompt that the service is not running - click yes to start the service) then try the test again. mm [/QUOTE]