Normal
No sure I can say much - I can see things happening in the logs (like blocks of very late samples being dropped in evr.log) but there's nothing really to explain what might have happened (other than there might have been a timestamp or clock glitch - which caused samples to get 'stuck' in the pipeline for a few seconds). I haven't changed much in the core stream handling in v50 (and this version plays through my collection of badly corrupted recordings with no problems). Is the problem repeatable if you play that part of the recording again i.e. skip back to a few minutes before the 'problem' time ? Tony
No sure I can say much - I can see things happening in the logs (like blocks of very late samples being dropped in evr.log) but there's nothing really to explain what might have happened (other than there might have been a timestamp or clock glitch - which caused samples to get 'stuck' in the pipeline for a few seconds).
I haven't changed much in the core stream handling in v50 (and this version plays through my collection of badly corrupted recordings with no problems).
Is the problem repeatable if you play that part of the recording again i.e. skip back to a few minutes before the 'problem' time ?
Tony
