home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
[solved by driver update of PCTV 461e] "Continuity error..." after updating from Windows 10 1909 to 20H2
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1279527" data-attributes="member: 141969"><p>Hmm, I don't think that I would regard that as acceptable <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" />.</p><p></p><p>I don't know what the cause is, but you might be able to avoid it by ensuring that your recording folder and MP installation are not on the same physical disk. For example, I have the Windows OS and MP installation on the "C:" drive (a slow Western Digital 5400 rpm Green disk), but my recording folder is on the "E:" drive (a fast Seagate 7200 rpm disk).</p><p></p><p>Updating the EPG on disk is a disk-intensive activity, and (on my system) typically takes 10-15 minutes. If "TV Server" is also trying to write one or more files to the recording folder, and the disk is not fast, maybe you end up with the behaviour that you have encountered. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" /></p><p></p><p>If you cannot use a physically separate disk, you could perform EPG grabbing/updating at a time when you are not using the system for viewing or recording (e.g. at 04:00 hrs, perhaps).</p><p></p><p></p><p>Is this watching TV/video, or are you playing a computer game? I was under the impression that playing SD and HD content is a relatively trivial task for most graphics adapters, and it is only playing UHD that is problematic for the lower-spec adapters.</p><p></p><p>I don't have an explanation for why 20H2 is worse than 1909. Possibly something related to networking, but that is above my pay grade. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1279527, member: 141969"] Hmm, I don't think that I would regard that as acceptable :(. I don't know what the cause is, but you might be able to avoid it by ensuring that your recording folder and MP installation are not on the same physical disk. For example, I have the Windows OS and MP installation on the "C:" drive (a slow Western Digital 5400 rpm Green disk), but my recording folder is on the "E:" drive (a fast Seagate 7200 rpm disk). Updating the EPG on disk is a disk-intensive activity, and (on my system) typically takes 10-15 minutes. If "TV Server" is also trying to write one or more files to the recording folder, and the disk is not fast, maybe you end up with the behaviour that you have encountered. :confused: If you cannot use a physically separate disk, you could perform EPG grabbing/updating at a time when you are not using the system for viewing or recording (e.g. at 04:00 hrs, perhaps). Is this watching TV/video, or are you playing a computer game? I was under the impression that playing SD and HD content is a relatively trivial task for most graphics adapters, and it is only playing UHD that is problematic for the lower-spec adapters. I don't have an explanation for why 20H2 is worse than 1909. Possibly something related to networking, but that is above my pay grade. :( -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
[solved by driver update of PCTV 461e] "Continuity error..." after updating from Windows 10 1909 to 20H2
Contact us
RSS
Top
Bottom