Reply to thread

Message

Doveman: I've checked the logs and 1 thing i noticed: you have your Timeshift folder set @ R:\ and your recording folder set @ D:\. As soon as the recording of Channel 4 started, the system started to copy the timeshiftfile to D:\ which means HDD activity. Have you tried setting the timeshift + recording folder to the same drive to see if that helps?
[code]18-06-2012 20:48:03.595 Recorder:pid 244 Continuity error... 0 ( prev 7 ) - bad signal?
18-06-2012 20:48:03.595 Recorder:pid 244 Continuity error... 0 ( prev 7 ) - bad signal?
18-06-2012 20:48:03.596 Recorder:pid 245 Continuity error... 3 ( prev 9 ) - bad signal?[/code]
The above errors can also be created on HDD activity, (high) CPU load, etc. It doesn't always mean it's a bad signal.
Have you also tried (to test the click/pop sound) to set TV Audio Decoder to LAV instead of ffdshow?

Bogomil: i don't see much in your logs, but i'm no TV log expert.

Tony is on vacation but expected to be back before the end of the month, so give him some time to read up when he's back and then i'm sure he'll take a look, unless someone else has a solution sooner

<blockquote data-quote="HomeY" data-source="post: 875902" data-attributes="member: 68365">Doveman: I've checked the logs and 1 thing i noticed: you have your Timeshift folder set @ R:\ and your recording folder set @ D:\. As soon as the recording of Channel 4 started, the system started to copy the timeshiftfile to D:\ which means HDD activity. Have you tried setting the timeshift + recording folder to the same drive to see if that helps?[code]18-06-2012 20:48:03.595 Recorder:pid 244 Continuity error... 0 ( prev 7 ) - bad signal?18-06-2012 20:48:03.595 Recorder:pid 244 Continuity error... 0 ( prev 7 ) - bad signal?18-06-2012 20:48:03.596 Recorder:pid 245 Continuity error... 3 ( prev 9 ) - bad signal?[/code]The above errors can also be created on HDD activity, (high) CPU load, etc. It doesn't always mean it's a bad signal.Have you also tried (to test the click/pop sound) to set TV Audio Decoder to LAV instead of ffdshow?&nbsp;&nbsp;Bogomil: i don't see much in your logs, but i'm no TV log expert.&nbsp;Tony is on vacation but expected to be back before the end of the month, so give him some time to read up when he's back and then i'm sure he'll take a look, unless someone else has a solution sooner <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="HomeY, post: 875902, member: 68365"] Doveman: I've checked the logs and 1 thing i noticed: you have your Timeshift folder set @ R:\ and your recording folder set @ D:\. As soon as the recording of Channel 4 started, the system started to copy the timeshiftfile to D:\ which means HDD activity. Have you tried setting the timeshift + recording folder to the same drive to see if that helps? [code]18-06-2012 20:48:03.595 Recorder:pid 244 Continuity error... 0 ( prev 7 ) - bad signal? 18-06-2012 20:48:03.595 Recorder:pid 244 Continuity error... 0 ( prev 7 ) - bad signal? 18-06-2012 20:48:03.596 Recorder:pid 245 Continuity error... 3 ( prev 9 ) - bad signal?[/code] The above errors can also be created on HDD activity, (high) CPU load, etc. It doesn't always mean it's a bad signal. Have you also tried (to test the click/pop sound) to set TV Audio Decoder to LAV instead of ffdshow? Bogomil: i don't see much in your logs, but i'm no TV log expert. Tony is on vacation but expected to be back before the end of the month, so give him some time to read up when he's back and then i'm sure he'll take a look, unless someone else has a solution sooner ;) [/QUOTE]