Gidday DM Team!

Thanks for a great machine.

One of my frequent activities is to review the EPG content and decide what to record. It is very convenient to use the 'Add Timer' key to select what to record, but it could be even better! This key could be 'Add/Edit Timer' so that it can edit a timer that already exists if this is appropriate. (otherwise, one has to check the timer entries to make sure there are no duplicates, overlaps or stale timers).

At the moment, it is possible to create a duplicate identical timer entry which could cause two simulataneous recordings if left without correction!

Do you think this is a good idea?

It would be fairly straight forward if the time bracket and channel were identical, but it may be more difficult to determine the appropriate action if there was an existing timer on the same channel that overlapped rather than being identical?

cheers from Oz

Ouch!

If the error was understood and a fix for the microcode was developed... how could this be inserted in an existing 7025?

Would this involve replacing demux hardware?

Ambrosa has written a python routine (e2_loadepg.py) that successfully converts SKY Italy XMLTV data to the E2 epg.dat format. I have adapted this routine to convert OzTivo (Australia) XMLTV data ... so I now have my DM7025 starting to work almost as intended.

PROBLEM: Several of the channels on the Aurora (OPTUS C1 156E) service have non programme specific info instead of programme data which is displayed as 'now' and 'next' programmes. For example the channel named 'SBS WA' shows 'SBS National Television' with a duration of 1440 minutes as the 'now' programme and the 'next' programme contains the same description! So these two programmes obiterate two whole days of the detailed programme data downloaded and imported into epg.dat.

I would like to be able to disable the display of any of this DVB 'now' / 'next' data in favour of displaying the data available from the downloads.

This might be a simple option to provide within Enigma2 (just turning something off)?

Or maybe it is something I should be able to do with some hint from knowledgeable ones? (though I'm not a programmer...)

Any advice on this issue would be appreciated.

regards

Please provide some information about the hard- and software used.

Box type: 7025
GUI (enigma1/enigma2):Enigma2
Firmware version: Official, OoZooN 20061214

Recent versions of Firmware fail to correctly initialise the sound when using the RF Modulator.

This is evident after a restart of Enigma or after a reboot. The picture returns using the correct RF Modulator channel, but the sound is loud white noise.

To clear this you have to go into Setup, System, RF Modulator and first disable RF Mod then re-enable it.

The problem can also be created by turning sound off then on from the same dialog window. Then if you disable RF Mod and re-enable, the problem is once again cleared.

From these symptoms, perhaps the fix is simple... just need to enable RF Modulator after the sound is set on?

Hope this helps[/b]