> I think 4D is now/next information and that is not used/inserted. > What you should be seeing is descriptors around 50 or 60, i > don't remeber the exact numbers.
Nope, that wasn't the problem; the check for table id 50 is done before even entering ParseDVBEIT (where the debugoutput was generated); > The eit code is still considered experimental. > The full guide data could possibly be transmitted on only one > mux so you probably have to change to different channels and > see if you get it to work. Which EIT Data is available on what transport seems slightly fishy on Astra; on the one hand we get an "all EIT on one transport" flag, on the other EIT is present right on the transport a channel is received on. Turning off the check for LinkageType == 4 gets EIT updates working. It's VERY nice to have since there's a couple of channels xmltv info isn't available for. Being able to fill these from the DVBEIT tables makes these channels much mor usable. Trial and error show that I need to tune to a couple of different transports to get a full complement of EID data for the channels I don't have xmltv info for. I've just set up a couple of manual daily recordings: 5 min each, autoexpire, record new+overwrite old, keep 1 episode. These should keep the guide data uptodate until the greatly anticipated feature: "walk transports and collect EIT data in background with idle receivers" gets implemented :-) Bye, Martin
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
