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
MediaPortal 1 Talk
Calling all MP New Zealanders (Both of you!!)
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="mm1352000" data-source="post: 1133772" data-attributes="member: 82144"><p>Don't assume that the tuner signal statistics are trustworthy. They're unlikely to show transient bursty problems. Also, tuner drivers are inconsistent in the way they calculate/report their statistics. In other words, there's no guarantee that 0 is the lowest value and 100 is highest value.</p><p></p><p>If you're confident that your signal is okay then consider all the other possible causes of continuity errors (which is almost certainly what we'd find in the TsWriter log for the recordings, if you posted them). For example:</p><ul> <li data-xf-list-type="ul">do you have HDDs spinning up or down</li> <li data-xf-list-type="ul">do you have other software that would be using the HDD that you're recording to</li> <li data-xf-list-type="ul">are you recording to a NAS or network share</li> </ul><p>etc.</p><p></p><p></p><p>Codecs have nothing to do with the duration calculation. Duration is entirely in the hands of TsReader. Having said that, just thinking now... I wonder if the durations shown in [for example] the recording list are from MediaInfo. In any case, when you actually play/pause a recording, TsReader is definitely responsible for that handling.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1133772, member: 82144"] Don't assume that the tuner signal statistics are trustworthy. They're unlikely to show transient bursty problems. Also, tuner drivers are inconsistent in the way they calculate/report their statistics. In other words, there's no guarantee that 0 is the lowest value and 100 is highest value. If you're confident that your signal is okay then consider all the other possible causes of continuity errors (which is almost certainly what we'd find in the TsWriter log for the recordings, if you posted them). For example: [LIST] [*]do you have HDDs spinning up or down [*]do you have other software that would be using the HDD that you're recording to [*]are you recording to a NAS or network share [/LIST] etc. Codecs have nothing to do with the duration calculation. Duration is entirely in the hands of TsReader. Having said that, just thinking now... I wonder if the durations shown in [for example] the recording list are from MediaInfo. In any case, when you actually play/pause a recording, TsReader is definitely responsible for that handling. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Calling all MP New Zealanders (Both of you!!)
Contact us
RSS
Top
Bottom