Not really as such. The new rewriter doesn't operate the same way as the old one, so skipped= and unhandled_packets= aren't a thing that is meaningful in the new system.
I can look at adding back highest_pts=, but the meaning in the new system is somewhat different from what it was before...
Thanks. Mainly useful for interrupted recordings so I can quickly locate the spot in my video editor where Channels DVR stitched the stream back together.
Day one 4 hrs of back-back recordings, all good
Day two 3 hrs of back-back recordings, all good
Day three 3 hrs of back-back recordings, all good
Day four 3 hrs of back-back recordings, all good
Day five 3 hrs of back-back recordings, all good
And after recording, updated to
and
just to make sure I'm testing w/latest version
Day six 3 hrs of back-back recordings, all good
Day seven 2 hrs of back-back recordings, all good
After upgrading to v2023.07.27.2357 with the MPEG-TS Rewriter enabled, Newsmax (channel 6764) is now unwatchable as it stutters terribly. It was smooth as butter in the prior beta version…
After investigating further I was able to figure out how wire up the rewriter statistics for the new rewriter. Some of the values will always be 0 with the new system (skipped, unhandled_packets, invalid_pts, invalid_dts), but the other ones that sounded like the most important ones will be working.
Yes, we're adding a synthetic PCR if one hasn't been seen in 100ms to conform to the MPEG-TS spec. That saw_pcr=false is indicating that we did not see one in the original stream.