[mythtv] mythcommflag gets mpeg2video errors not seen in playback

[Ken Mandelberg]

mythcommflag gives a large number of

[mpeg2video @ 0xb73ddb68]current_picture not initalized
2007-09-03 11:09:32.693 AFD Error: Unknown decoding error

on firewire streams captured on a comcast cable box. The commerical 
marking on these streams are very unreliable, clearly the time offsets 
generated are out of sync with the video playback. These particular 
streams are from extended basic sd digital channels (fx,usa, comedy 
central, ..) which are encrypted. However, the firewire captured mpeg 
transport streams play perfectly well in myth. OTA streams captured in 
the same way don't seem to have this problem.

My thought is that mythcommflag is not using the same codec as the myth 
native player. Here is some comparative output

 From mythfrontend

2007-09-03 11:19:50.195 AFD: Stream #0, has id 0x2240 codec id 
MPEG2VIDEO, type Video, bitrate 15000000 at 0x0x884a910
2007-09-03 11:19:50.196 detectInterlace(Detect Scan, Interlaced Scan, 
29.97, 480) ->Interlaced Scan
2007-09-03 11:19:50.196 AFD: Looking for decoder for MPEG2VIDEO
2007-09-03 11:19:50.196 AFD: Opened codec 0x8b24860, id(MPEG2VIDEO) 
type(Video)

 From mythcommflag
2007-09-03 11:09:32.035 AFD: Stream #0, has id 0x2240 codec id 
MPEG2VIDEO, type Video, bitrate 15000000 at 0x0x81ff890
2007-09-03 11:09:32.037 detectInterlace(Detect Scan, Interlaced Scan, 
29.97, 480) ->Interlaced Scan
2007-09-03 11:09:32.037 AFD: Looking for decoder for MPEG2VIDEO
2007-09-03 11:09:32.037 AFD: Opened codec 0x81ff990, id(MPEG2VIDEO) 
type(Video)

What strikes me is that mythfrontend sees 0x0x884a910 and opens codec 
0x8b24860.

mythcommflag  sees 0x0x81ff890 and opens codec 0x81ff990.

I have to admit I don't understand the hex values. Are they just memory 
addresses where the codecs are loaded, or are they absolute id numbers?

Is it significant that mythfrontend has two different hex values, and 
mythcommflag has the same on detect and open?