NextPVR Forums

NextPVR Forums > Public > NextPVR Support > Legacy (v4.x and earlier) > Differences in PTS logging
Full Version: Differences in PTS logging
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

bgowland

2011-09-10, 11:20 PM
Trying to track down an issue with skipping on my PCH A-110 (long story, I'll post a proper support request when I have more info).

Along the way, I notice things such as the following in the MVP.log...

Code:
2011-09-10 23:09:30.878    [DEBUG][3]    Raw PTS received:204391800
2011-09-10 23:09:30.878    [DEBUG][3]    Reported PTS now:204377400  time: 4541.72
Is it relevant that 'RAW PTS received' and 'Reported PTS Now' are different?

Cheers,
Brian

mvallevand

2011-09-10, 11:55 PM
Because of the nature of PTS in transport streams they often don't start at zero and what you are seeing is the corrected value from the first reported PTS.

Technically the corrected value is wrong too because mpvmcx2 has to adjust to a major bug in GBPVR not working with int64's so mvpmcx2's value is not raw it is normalized before it is sent.

Martin
NextPVR Forums > Public > NextPVR Support > Legacy (v4.x and earlier) > Differences in PTS logging