United Kingdom
- Thread starter
- #901
The TV Server will work without it,
As I explained in another post you need to place it in the TVServer folder for the TBS CI and quick tuning to work.
Custom Data Grabber including Sky UK Channel/EPG Grabber (4 Viewers)
- Thread starter DJBlu
- Start date
The TV Server will work without it,
As I explained in another post you need to place it in the TVServer folder for the TBS CI and quick tuning to work.
- Thread starter
- #903
I need the TSWriter and TV Logs
- Thread starter
- #905
288 Continuity error... 6 ( prev c ) - bad signal?
08-02-2012 19:53:33.727 CDiskRecorder::Flush() - Throttle to 1880 bytes (max)
08-02-2012 19:53:33.836 !!! CSectionDecoder::OnTsPacket Entered infinite loop. pid: 43 start: 20 BufferPos: 7 SectionLength: 4 - Discarding section and moving to next packet
08-02-2012 19:53:34.555 cagrabber: got ca version:1 -1
08-02-2012 19:53:34.555 cagrabber: do callback
08-02-2012 19:53:36.195 Recorder
id 288 Continuity error... 8 ( prev 4 ) - bad signal?08-02-2012 19:53:36.227 Recorder
id 288 Continuity error... a ( prev 8 ) - bad signal?08-02-2012 19:53:36.273 Recorder
id 288 Continuity error... c ( prev a ) - bad signal?08-02-2012 19:53:36.305 !!! CSectionDecoder::OnTsPacket Entered infinite loop. pid: 11 start: 14 BufferPos: 7 SectionLength: 4 - Discarding section and moving to next packet
08-02-2012 19:53:36.320 Recorder
id 288 Continuity error... 0 ( prev c ) - bad signal?08-02-2012 19:53:36.383 Recorder
id 288 Continuity error... 3 ( prev 0 ) - bad signal?08-02-2012 19:53:36.414 Recorder
id 288 Continuity error... 6 ( prev 3 ) - bad signal?08-02-2012 19:53:36.492 !!! CSectionDecoder::OnTsPacket Entered infinite loop. pid: 31 start: 22 BufferPos: 7 SectionLength: 4 - Discarding section and moving to next packet
08-02-2012 19:53:36.492 !!! CSectionDecoder::OnTsPacket Entered infinite loop. pid: 37 start: 18 BufferPos: 7 SectionLength: 4 - Discarding section and moving to next packet
08-02-2012 19:53:36.586 Recorder
id 288 Continuity error... e ( prev 7 ) - bad signal?08-02-2012 19:53:36.648 Recorder
id 288 Continuity error... 1 ( prev f ) - bad signal?08-02-2012 19:53:36.711 Recorder
id 288 Continuity error... 5 ( prev 1 ) - bad signal?08-02-2012 19:53:36.867 Recorder
id 288 Continuity error... e ( prev 5 ) - bad signal?08-02-2012 19:53:36.914 Recorder
id 288 Continuity error... 2 ( prev e ) - bad signal?08-02-2012 19:53:36.977 Recorder
id 288 Continuity error... 5 ( prev 2 ) - bad signal?08-02-2012 19:53:37.23 Recorder
id 288 Continuity error... 9 ( prev 5 ) - bad signal?08-02-2012 19:53:37.39 !!! CSectionDecoder::OnTsPacket Entered infinite loop. pid: 11 start: 11 BufferPos: 4 SectionLength: 1 - Discarding section and moving to next packet
08-02-2012 19:53:37.55 Recorder
id 288 Continuity error... d ( prev 9 ) - bad signal?08-02-2012 19:53:37.86 Recorder
id 288 Continuity error... f ( prev d ) - bad signal?08-02-2012 19:53:37.117 Recorder
id 288 Continuity error... 1 ( prev f ) - bad signal?08-02-2012 19:53:37.133 Recorder
id 288 Continuity error... 3 ( prev 1 ) - bad signal?08-02-2012 19:53:37.258 !!! CSectionDecoder::OnTsPacket Entered infinite loop. pid: 34 start: 20 BufferPos: 7 SectionLength: 4 - Discarding section and moving to next packet
08-02-2012 19:53:37.273 Recorder
id 288 Continuity error... c ( prev 3 ) - bad signal?08-02-2012 19:53:37.305 Recorder
id 288 Continuity error... e ( prev c ) - bad signal?08-02-2012 19:53:37.336 Recorder
id 288 Continuity error... 0 ( prev e ) - bad signal?08-02-2012 19:53:37.383 Recorder
id 288 Continuity error... 3 ( prev 1 ) - bad signal?08-02-2012 19:53:37.445 Recorder
id 288 Continuity error... 7 ( prev 4 ) - bad signal?08-02-2012 19:53:37.523 Recorder
id 288 Continuity error... b ( prev 8 ) - bad signal?08-02-2012 19:53:37.570 Recorder
id 288 Continuity error... e ( prev b ) - bad signal?08-02-2012 19:53:37.602 Recorder
id 288 Continuity error... 0 ( prev e ) - bad signal?08-02-2012 19:53:37.633 Recorder
id 288 Continuity error... 2 ( prev 0 ) - bad signal?08-02-2012 19:53:37.742 Recorder
id 288 Continuity error... 8 ( prev 2 ) - bad signal?08-02-2012 19:53:37.805 Recorder
id 288 Continuity error... c ( prev 9 ) - bad signal?There lies the issue.
Check the F Connectors to the TBS Card and LNB.
Thanks for looking at that. Really odd. I'll have to look into it more. It was grabbing fine in the past with the same setup, and I don't get any glitches watching TV. I've just switched the inputs around and the same thing has happened. What's even stranger is that the same thing happened on a totally different computer in a different house (admittedly in the same street). I did have a dodgy engineer put my dish up originally. He used insulating tape instead of a screw to hold the LNB to the dish! This has been fixed though.
I'll keep trying...
I'll keep trying...
Yeah, I understand where I need to put it, just wondered what it did and how it relates to the driver.. Has there been some sort of support built into the driver to support the dll?
I've not seen that dll mentioned in mm1352000's thread.. I'm just being curious!
EDIT : never mind, I just re-read the thread again properly and it is indeed discussed!
One other thing I notice (which may already be mentioned) is that no matter what I set the grabber time to, it always says 'grabbing 60 seconds'. Not sure if this affects anything. Also, playing about with my timeshift settings seems to make a difference to what is grabbed.
Ok more testing with regards to recordings ~ no one else having this problem???
Every series link recording this week fails to wake the machine, programs set to record in evening (when machine is awake) record just fine.
Record once programs have all been recorded.
Looking into series link recordings - they get added as a schedule (under the tv configuration - schedule), when the recording starts it's added as a record once entry in addition to the schedule. Shouldn't this record once entry be added each time in order for power scheduler to know when to wake machine?
If you think this is a power scheduler fault let me know and I'll post in the power scheduler forum.
I'll switch to debug and setup some recordings.
Every series link recording this week fails to wake the machine, programs set to record in evening (when machine is awake) record just fine.
Record once programs have all been recorded.
Looking into series link recordings - they get added as a schedule (under the tv configuration - schedule), when the recording starts it's added as a record once entry in addition to the schedule. Shouldn't this record once entry be added each time in order for power scheduler to know when to wake machine?
If you think this is a power scheduler fault let me know and I'll post in the power scheduler forum.
I'll switch to debug and setup some recordings.
It could well be the power Scheduler as i've noticed that after 1.2.1 when my pc returns from sleep mode if i stop the tvservice and restart it i get a an error saying that its unable to connect to tvservice. However saying that both the build in scheduler and the A++ version both do it. I've tryed to trace the fault all i know is after a sleep the service fails to close down one of the ports its using port (31457) and this is causing issues and could well be causing recordings to be missed. This is nothing to do with DJBlu's coding as it happends even with the stock 1.2.2 (and 1.2.1 come to think of it) i've got some free time this weekend so i'll try to dig deeper.