Some problem with the quality of the recording of the same channel in 2.6.2

[sub]

I'm not really sure what to suggest for that one.

Is the recording fine other than this brief people of overlap?

[Kiwi]

I'm not really sure what to suggest for that one.

Is the recording fine other than this brief people of overlap?

Yes the recording is fine other than this, but if there are quite frequent starts of new recordings it could be quite a disturbing experience.

Hopefully you will be able to spot the error.

[Croftie]

I have this issue aswell. I've had it before too, it dissapered when I changed capture card and updated NPVR but now it's back. A quick history..

Using GBPVR with a Compro VideoMate E900F, no issue.
Moved to NPVR and the issue starts, I made a thread here, no conclusion and I put up with it.
Changed capture card to TBS 6280 and updated NPVR, to my joy the issue was gone. That was in january this year.
About a week or two ago the issue returned, I was using 2.5.9 so installed the latest patches but it didn't help, then 2.6.2 came out but didn't resolve either. So Installed a copy of windows 7 on a second drive but still the same issue.

I'm using windows XP and the same TBS drivers since I installed the card in january, I have no idea why this suddenly started again now but I'm very relieved it's not just me and also desperate to resolve it.

Must sleep now but I'll be back troubleshooting in the morn, in the mean time here's another sample. The glitch is 48 seconds into the first clip, the second clip is the second program, as you can see the glitch happens at the exact time the second recording starts.

https://www.rapidshare.com/files/3392095...7301800.ts
https://www.rapidshare.com/files/2525804...8001830.ts

[Kiwi]

I have this issue aswell. I've had it before too, it dissapered when I changed capture card and updated NPVR but now it's back. A quick history..

Using GBPVR with a Compro VideoMate E900F, no issue.
Moved to NPVR and the issue starts, I made a thread here, no conclusion and I put up with it.
Changed capture card to TBS 6280 and updated NPVR, to my joy the issue was gone. That was in january this year.
About a week or two ago the issue returned, I was using 2.5.9 so installed the latest patches but it didn't help, then 2.6.2 came out but didn't resolve either. So Installed a copy of windows 7 on a second drive but still the same issue.

I'm using windows XP and the same TBS drivers since I installed the card in january, I have no idea why this suddenly started again now but I'm very relieved it's not just me and also desperate to resolve it.

Must sleep now but I'll be back troubleshooting in the morn, in the mean time here's another sample. The glitch is 48 seconds into the first clip, the second clip is the second program, as you can see the glitch happens at the exact time the second recording starts.

https://www.rapidshare.com/files/3392095...7301800.ts
https://www.rapidshare.com/files/2525804...8001830.ts

From my experience it's most likely not the card problem, as I face the same issue with my Hauppauge HVR2200 card (recording DVB-T programmes) in another system, in addition to the TBS 6280 (recording DVB-C programmes) in the current system.

[Kiwi]

Croftie, would u kindly upload your glitched video clips onto FileDropper? I would like to see the clips too. My ISP blocked rapidshare. Thanks.

http://www.filedropper.com

[no_entry]

This 2.6.2 bug affects recordings with dual and quad tuners only? Problem free when recording several shows with a single tuner but not when recording several shows with a dual tuner even when it is just using Tuner 1 of the dual tuner.

[Kiwi]

This 2.6.2 bug affects recordings with dual and quad tuners only? Problem free when recording several shows with a single tuner but not when recording several shows with a dual tuner even when it is just using Tuner 1 of the dual tuner.

To test this I will have to use my old Happpauge HVR1300. But your observation seems possible, since both the HVR2200 and the TBS6280 are dual tuners.

But I must say, the glitches didn't happen with the 2.5.9 release, nor the various patch files released in between 2.5.9 and 2.6.2.

[Handy.Man]

I have the same problem here with a dual Tuner Hauppauge WinTV HVR-2250, it happens when TeleJournal started at 20:59:00.373 ndigitalhost-24

Code:

2013-03-25 20:59:00.311    [INFO][298]    DigitalRecorder.StartStream(P:\Utilisateurs\Public\TV enregistrée\19-2\19-2_20130325_21002200.ts)
2013-03-25 20:59:00.311    [INFO][298]    Creating BDA graph
2013-03-25 20:59:00.317    [DEBUG][298]    Using tuner Hauppauge WinTV-7164 BDA ATSC/QAM Tuner (1)
2013-03-25 20:59:00.317    [INFO][298]                [d111520b-511c-49fa-846a165e7be3f3af]-708645e9-00000000
2013-03-25 20:59:00.325    [DEBUG][298]    About to auto detect capture filter...
2013-03-25 20:59:00.327    [DEBUG][298]    Got capture filter: 'Hauppauge WinTV-7164 BDA Digital Capture'
2013-03-25 20:59:00.327    [DEBUG][298]    Added capture filter
2013-03-25 20:59:00.328    [DEBUG][298]    Connected Tuner to Capture
2013-03-25 20:59:00.329    [DEBUG][298]    Activating time machine
2013-03-25 20:59:00.332    [DEBUG][298]    Time machine activated...
2013-03-25 20:59:00.354    [DEBUG][298]    EIT collection started
2013-03-25 20:59:00.354    [DEBUG][298]    Graph filter list:
2013-03-25 20:59:00.354    [DEBUG][298]     - MPEG-2 Sections and Tables
2013-03-25 20:59:00.354    [DEBUG][298]     - BDA MPEG2 Transport Information Filter
2013-03-25 20:59:00.354    [DEBUG][298]     - MPEG-2 Demultiplexer
2013-03-25 20:59:00.354    [DEBUG][298]     - NPVR TS Mon
2013-03-25 20:59:00.354    [DEBUG][298]     - Capture
2013-03-25 20:59:00.354    [DEBUG][298]     - Tuner
2013-03-25 20:59:00.354    [DEBUG][298]     - Network Provider
2013-03-25 20:59:00.354    [INFO][298]    About to start BDA graph
2013-03-25 20:59:00.354    [DEBUG][298]    Starting graph...
2013-03-25 20:59:00.373    [DEBUG][298]    About to tune BDA graph:
<tuning>
  <type>ATSC</type>
  <locator>
    <physical_channel>19</physical_channel>
  </locator>
  <service_id>3</service_id>
  <tsid>17509</tsid>
  <service_type>1</service_type>
</tuning>

2013-03-25 20:59:00.798    [DEBUG][298]    whoosh whoosh
2013-03-25 20:59:00.798    [DEBUG][298]    Calling LockChannel()
2013-03-25 20:59:00.820    [DEBUG][298]    locked=1, present=1, strength=-20, quality=100   (took 16ms to check)
2013-03-25 20:59:00.821    [DEBUG][298]    File size is 0
2013-03-25 20:59:00.821    [INFO][298]    DigitalRecorder.StartStream() allocated handle: 0x5
2013-03-25 20:59:00.821    [DEBUG][298]    Temp at 2013-03-25 20:59:10
2013-03-25 22:00:00.198    [INFO][352]    DigitalRecorder.StartStream(P:\Utilisateurs\Public\TV enregistrée\Le Téléjournal\Le Téléjournal_20130325_22002245.ts)
2013-03-25 22:00:00.223    [DEBUG][352]    File size is 7127080
2013-03-25 22:00:00.223    [INFO][352]    DigitalRecorder.StartStream() allocated handle: 0x6
2013-03-25 22:00:00.223    [DEBUG][352]    Temp at 2013-03-25 22:00:10
2013-03-25 22:00:20.649    [INFO][342]    DigitalRecorder.StopStream() handle: 5

It happens from time to time (2-3 times a week), I can edit these repeat glitchs with VideoRedo. They are about 1sec each.

Code:

2013-03-25 22:07:39 Preparing to send status to: 0 Audio volume changed
2013-03-25 22:07:41 Sending status: 'Audio volume changed' to module: 'Output muxer - 0', Type: Video frame
2013-03-25 22:07:41 Preparing to send status to: 0 Audio volume changed
2013-03-25 22:07:41 Sending status: 'Audio volume changed' to module: 'Audio recoder - 0', Type: Audio frame
2013-03-25 22:07:41 Adding new graph range, Start:    3365279 (00:56:05.19), End: 3658705.06 (01:00:58.39)
2013-03-25 22:07:52 Resync: removed   1 audio frames, at audio 00:42:59.22, original (01:00:53.57), sync changed from 3825.49 to -77.02
2013-03-25 22:07:52 AudioRecoder thread complete. Stream: 0, Audio Frames, In:80743, Out: 80739
2013-03-25 22:07:52 Graph, monitoring thread received terminate signal.
2013-03-25 22:07:52 Output muxer processing thread complete. Video in: 154871, Out: 154871, Buffer: 0
2013-03-25 22:07:52 Graph monitoring thread finished.
2013-03-25 22:07:52 Output muxer processing thread complete. Audio stream 0 In: 80739, Out: 80739, Buffer: 0
2013-03-25 22:07:52 Muxer add / delete audio: stream: 0, add: 0  delete 0, sync:     -77.04

I could be related to the Hauppauge driver as it is more frequent since the CD 2.7 driver release I installed on feb 23. It happened with 2.5.9 too

[sub]

Kiwi, what CPU is in your machine?

[Kiwi]

Kiwi, what CPU is in your machine?

One system is Core i5-2400 (4 cores), the other is G260 (2 cores). Both are Sandy Bridge I think.