- Thread starter
- #41
I've no idea, but attached are logs playing the same recording from the beginning for about 30 seconds, one with bias = 1.0 and one with bias = 0.95 (set from my modified TsReader.ax three seconds after 'run' - about 16 seconds later the "Not Enough Data" messages start). In both my tests and (I think) in FreakJ's situation (==24Hz on 60Hz display) there won't be any AdjustClock() calls, but I guess that shouldn't make a difference.
Would you like me to try some different MPAR settings ?
Actually I can rerpoduce the issue, forcing bias 0.5 causes it to appear (not anything TsReader related as it happens with BDReader as well). Last time when I tested I had some logging commented out for other tests