Remote access to ATSC machine needed

[bigbus01]

Firefox didn't help.

Just tried a scheduled recording and it worked again (using the original setup--no patches).

I will keep trying to get the patches.

Bigbus

[elite]

Firefox didn't help.

Just tried a scheduled recording and it worked again (using the original setup--no patches).

I will keep trying to get the patches.

Bigbus

Looks like the gbpvr.com server is down (forums are on a different server) - try back a bit later

[unsword]

Do you know if you have any tools that will show you what the PIDs are? Maybe the software that came with your card? I'd be interested to compare with the PIDs that GB-PVR found for those problem channels.

Sub

I've done some research and in the process run across a really useful stream viewer utility at http://www.coolstf.com/tsreader - this allows you to tune a BDA source ATSC tuner card and view all the information about the stream you are receiving.

Using this I can confirm the problems I was having with channels 2 and 17 as being attributable to the wrong PID selections.

Example - CH2, the main program of interest (the HD feed) is Program #1 with a Video PID of 49 (0xx31) and an audio PID of 52 (0x0034), but the recording log shows the PIDs being selected as 65 and 68 - which correspond to Program #2 in the stream. I know from channel surfing (and confirmed by the stream viewer) that this station rarely has any video on their second program - hence the reason I recorded black and silence.

Looking at CH17 I find that the log shows PIDs 49 and 53 were selected, these correspond to the correct video, but 53 is the second AC3 audio channel, the correct PID should have been 52

The recording CH36 I haven't yet explained - the only odd thing I have found is that they only have one Program but it's defined as Program 3. This may be a different problem (and I haven't seen it since).

I was able to export a lot of data for each of the above channels, see the attached files.

I went back and ran Config and noted that the PIDs shown in the channel mapping corresponded to those above, I manually edited the PIDs to the correct values and was able to successfully record the desired channels and programs and audio.

I then went back and looked at the channel mapping and experimented with the different instances of WSB-DT (CH2) which were listed in the drop-down and they all appeared to result in the same PID selection. So it looks like this is where the error is arising. They all show "T:39,2,2" and obviously the minor number 2 is the second program. Also, if I step down through the list of channels found during the scan, they correspond to the second program for WSB-DT and the secondardy audio for CH-17. This looks like the data you are saving during a scan is the last active PIDs found for any particular channel and not the actual V/A PIDs for EACH program found in that channel.

Moving on to testing for failed recordings - I've made a number of two min recordings and had a couple of problems where I still see manifestations of the 6KB failed recording problem - note the 4:09PM recording on CH17 WTBSDT where there is a '-1.dvr-ms' recording of correct nominal length but the original filename is only 710kB.

Logs, recordings directory listing and stream info attached

Hope this helps - feels like we are very close on this now.

[sub]

Cheers, thats good info. I'll work through it a little later today - cutting hedges, mowing lawns at the moment..

Do you still have the config.exe.log from after the last scan? it'll be the largest one. Can you post it? rescan if you need to. It'll tell me what PIDs etc GB-PVR found during the scan.

[-stattik-]

Sub,

I removed the recording source and readded it. The first scan found 3 stations. he second scan found one station. The third scan found no stations. I then tried DVICO's built-in scanner and it couldn't find any stations either. I rebooted and ran another scan and it found all stations. I scheduled a few recordings and they all worked but the audio was completely garbled.

Hardware was a DVICO fusion 3 gold.

[-stattik-]

Sub,

I removed the recording source and readded it. The first scan found 3 stations. he second scan found one station. The third scan found no stations. I then tried DVICO's built-in scanner and it couldn't find any stations either. I rebooted and ran another scan and it found all stations. I scheduled a few recordings and they all worked but the audio was completely garbled.

Hardware was a DVICO fusion 3 gold.

[unsword]

Looks like the previous config logs had rolled so I rescaned - logs attached.

BTW - I can see how the confusion could arise with WSB-DT since they appear to use the same name for both programs (not helpful..). However for WTBS it looks like config reported the second audio PID of 53 instead of the primary PID of 52

[ATTACHMENT NOT FOUND]

[sub]

Sub,

I removed the recording source and readded it. The first scan found 3 stations. he second scan found one station. The third scan found no stations. I then tried DVICO's built-in scanner and it couldn't find any stations either. I rebooted and ran another scan and it found all stations. I scheduled a few recordings and they all worked but the audio was completely garbled.

Hardware was a DVICO fusion 3 gold.

Did you apply that second patch I mentioned above? It resolved a sound issue. Before this it was treating the AC3 audio as MPEG1 layer 2 audio, which would give the garbled sounds.

[sub]

Does TSReader let you record a transport stream file? If so, I wouldnt mind a sample file so I can run the scan here in the debugger. Do you have access to a web server, or some other way to transfer a large file?

[sub]

I then went back and looked at the channel mapping and experimented with the different instances of WSB-DT (CH2) which were listed in the drop-down and they all appeared to result in the same PID selection. So it looks like this is where the error is arising. They all show "T:39,2,2" and obviously the minor number 2 is the second program. Also, if I step down through the list of channels found during the scan, they correspond to the second program for WSB-DT and the secondardy audio for CH-17. This looks like the data you are saving during a scan is the last active PIDs found for any particular channel and not the actual V/A PIDs for EACH program found in that channel.

Ah, I see...

Good info by the way.