Experimental TsReader development (3 Viewers)

[doveman]

I'm still having this very annoying problem with clicks and pops throughout Ch4 News. It also affects the weather straight after, but after that the programmes don't seem to have it!

I recorded it tonight and tried playing it on my other PC (over the network) and it's the same there, so it's not some dodgy setting on the HTPC that's causing it. I can upload a clip if someone tells me where to send it.

The attached TSreader log reflects playing back the recording on the HTPC, when the problem was just the same as when watching live.

 

[mylle]

Looks like a signal problem to me.

18-06-2012 20:46:09.844 Recorder: RECORD Info : Next broadcaster program clock reference rollover : 0 days 16:29:33 0
18-06-2012 20:48:03.595 Recorderid 244 Continuity error... 0 ( prev 7 ) - bad signal?
18-06-2012 20:48:03.595 Recorderid 244 Continuity error... 0 ( prev 7 ) - bad signal?
18-06-2012 20:48:03.596 Recorderid 245 Continuity error... 3 ( prev 9 ) - bad signal?
18-06-2012 20:48:03.597 Recorderid 245 Continuity error... 3 ( prev 9 ) - bad signal?
18-06-2012 20:48:03.597 Recorderid 247 Continuity error... 0 ( prev c ) - bad signal?
18-06-2012 20:48:03.598 Recorderid 247 Continuity error... 0 ( prev c ) - bad signal?
18-06-2012 20:48:09.839 epg: abort grabbing
18-06-2012 20:48:09.841 mhw abort grabbing
18-06-2012 20:48:09.843 epg: do callback
18-06-2012 20:48:09.845 mhw grabber ended
18-06-2012 20:48:09.847 CMhwParser:GetTitleCount:0
18-06-2012 20:48:09.850 EpgScanner::GetMHWTitleCount:0
18-06-2012 20:48:10.331 epg: reset
18-06-2012 20:48:10.332 epg:ResetEPG()
18-06-2012 20:48:10.345 mhw reset
18-06-2012 20:48:10.349 epg: reset
18-06-2012 20:48:10.350 epg:ResetEPG()
18-06-2012 20:48:10.350 mhw reset
18-06-2012 20:56:02.108 Recorderid 244 Continuity error... 2 ( prev 8 ) - bad signal?
18-06-2012 20:56:02.110 Recorderid 244 Continuity error... 2 ( prev 8 ) - bad signal?
18-06-2012 20:56:02.112 Recorderid 245 Continuity error... 0 ( prev 5 ) - bad signal?
18-06-2012 20:56:02.114 Recorderid 245 Continuity error... 0 ( prev 5 ) - bad signal?
18-06-2012 20:57:10.912 Recorder: RECORD Stop 'D:\Media\TV Recordings\Channel 4 News (Channel 4+1 - 18-06-2012).ts'

 

[doveman]

I saw those and I believe there was some probably some graphical corruption at those times. However the pops and clicks are throughout the programme, not just at the times of those errors and only seem to occur during Ch4 News and the Weather afterwards and I doubt the signal is lowered just whilst that is being broadcast.

 

[Bogomil]

pls full logs as described here http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/16_Support/3_Forums/2_Log_Files

Ok, sorry. I have now attached the log files from debug mode. Thanks

 

[HomeY]

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?

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?

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

 

[doveman]

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?

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?

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?

Thanks for taking a look HomeY.

Yes, my Timeshift is on my RAMdisk which is R: and my recording folder is on my HDD partition D:. I do have the debug option to record the Timeshift buffer enabled, which would explain why it's copying it from R: to D: when I start a manual recording.

However, the clicks and pops during Ch4 News occur when I'm not recording and I only started to record so that I could check whether the problems showed up on playback later and in case someone wanted to take a look at a clip. I think someone else mentioned that Continuity errors can be caused by things other than bad signal, so I investigated today whether I had a latency problem by running MP in a window and LatencyMon to catch any spikes. However, I only had one audio glitch (which was reflected by Continuity errors in the log) and LatencyMon didn't show any problems at that time. It did show a problem later, but at that time I didn't have any audio/video problems! I'll work to fix the latency problem of course, but it doesn't seem to be connected to the TV problems.

I will try LAV instead but when I test the recording on my other PC that plays it with MPC-HC using the MPC Audio Decoder, so I'm not that hopeful that it's as simple as a codec problem. What's most strange is that these clicks and pops only seem to appear for one programme

 

[Bogomil]

Thanks HomeY. I will then wait for the expert to look at my logs and I will also try another CI Module, because I am not sure that my actual one doesn´t make any problems.

 

[HomeY]

However, the clicks and pops during Ch4 News occur when I'm not recording and I only started to record so that I could check whether the problems showed up on playback later and in case someone wanted to take a look at a clip. I think someone else mentioned that Continuity errors can be caused by things other than bad signal, so I investigated today whether I had a latency problem by running MP in a window and LatencyMon to catch any spikes. However, I only had one audio glitch (which was reflected by Continuity errors in the log) and LatencyMon didn't show any problems at that time. It did show a problem later, but at that time I didn't have any audio/video problems! I'll work to fix the latency problem of course, but it doesn't seem to be connected to the TV problems.

I'm a bit in the same boat as you are. I also have random 'bad signal errors' in my TsWriter + TsReader logs (running dedicated TV Server). Tested my LAN -> OK, tested latency -> OK, set fixed IP on Server, set network adapter to Gbit Full Duplex and they still occur now and then. I figured out that some CPU load spikes seem to create the problems, which then sometimes result in A/V desync on my client.

In your case your recording also has the clicks/pops, which means it can't be TsReader, since recording is done by TsWriter. It's starting to look like it's a channel issue or something, but i'll leave the final verdict to the experts.

 

[doveman]

I'm a bit in the same boat as you are. I also have random 'bad signal errors' in my TsWriter + TsReader logs (running dedicated TV Server). Tested my LAN -> OK, tested latency -> OK, set fixed IP on Server, set network adapter to Gbit Full Duplex and they still occur now and then. I figured out that some CPU load spikes seem to create the problems, which then sometimes result in A/V desync on my client.

In your case your recording also has the clicks/pops, which means it can't be TsReader, since recording is done by TsWriter. It's starting to look like it's a channel issue or something, but i'll leave the final verdict to the experts.

Sorry to hear you're having problems as well. It's frustrating isn't it! I only have a single-seat system using the Loopback Adapter, so it should be less complex than yours but I still have issues nonetheless.

Thanks for explaining my problem can't be a TsReader issue though. I guess I should start another thread about it somewhere else then. Looks like some component or other (maybe a codec?) has a problem with the way this particular programme is being broadcast.

 

[msj33]

I found a bug in Tsreader when using Server/Client setup - A Bug that occurs with both Original and experimental Tsreader.

Tsreader does in some cases not recover properly from a Continuity error - The Video playback keeps showing "old" frames.

I will later link to 2 videos that show the issues. (Especially see the time counter on top of picture in video 1).
Video 1:

Video 2:

I can resolve the issue by doing a rewind and/or forward back to realtime playback. Also a stop/Start does recover the streaming. (video 2)

I have this issue almost every day.

In the attached logfiles, a freeze occured in playback at 22.04(Caused by either bad signal, wireless connection or cpu/disk usuage?)

For the next 15 minutes the video playback kept being corrupted, untill I did a 15 sec. rewind.

Can someone please have a look at this, and help confirm that this is actually a bug?

Thanks in advance
Morten