Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 1035930" data-attributes="member: 83973">The problem with the streams is that sometimes there are quite large skews between the video and audio - from your 'LAV' logs after each zap :[CODE][2013-10-25 09:06:27,453] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 2.575 sec of extra video comp to start now !...[2013-10-25 09:06:50,875] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 3.530 sec of extra video comp to start now !...[2013-10-25 09:07:05,484] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 1.311 sec of extra video comp to start now !...[2013-10-25 09:07:17,343] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 3.938 sec of extra video comp to start now !...[2013-10-25 09:07:44,562] [1f870048] [ db4] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 0.812 sec of extra video comp to start now !...[2013-10-25 09:07:54,375] [1f870048] [ 9d4] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 2.285 sec of extra video comp to start now !...[/CODE]The 'extra video comp' values are basically the V/A skew - note it's over 3.5 seconds sometimes, which was creating the playback problem because the old 'compensation' limit was 2 sec - I raised it to 5 sec in the test version. (It's limited to avoid corrupted streams etc.&nbsp; from possibly producing silly values).Re. the 'slow motion zapping option' - it's always been that way (and I quite like it, but I know some people don't) - personally I think all the 'debug' settings should be visible, or at least 'debug' mode should be a tick box in TV server config itself, not a 'launch' command line option.</blockquote>

[QUOTE="Owlsroost, post: 1035930, member: 83973"] The problem with the streams is that sometimes there are quite large skews between the video and audio - from your 'LAV' logs after each zap : [CODE][2013-10-25 09:06:27,453] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 2.575 sec of extra video comp to start now !... [2013-10-25 09:06:50,875] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 3.530 sec of extra video comp to start now !... [2013-10-25 09:07:05,484] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 1.311 sec of extra video comp to start now !... [2013-10-25 09:07:17,343] [1f870048] [ 9d8] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 3.938 sec of extra video comp to start now !... [2013-10-25 09:07:44,562] [1f870048] [ db4] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 0.812 sec of extra video comp to start now !... [2013-10-25 09:07:54,375] [1f870048] [ 9d4] - Compensation : ( Rnd : 0 mS ) Audio pts ahead Video pts . Add 2.285 sec of extra video comp to start now !... [/CODE] The 'extra video comp' values are basically the V/A skew - note it's over 3.5 seconds sometimes, which was creating the playback problem because the old 'compensation' limit was 2 sec - I raised it to 5 sec in the test version. (It's limited to avoid corrupted streams etc. from possibly producing silly values). Re. the 'slow motion zapping option' - it's always been that way (and I quite like it, but I know some people don't) - personally I think all the 'debug' settings should be visible, or at least 'debug' mode should be a tick box in TV server config itself, not a 'launch' command line option. [/QUOTE]

Verification