Paul,

thanks for the excellent product

I've just installed the latest beta from DigiTV and the timer setting no longer works, mostly the first timer will be set, but if another timer is set then no errors, just no timer set

DABDig 2.54b09

Yep - I've had same comment from someone else.

I've also posted in the http://www.digitv-forum.co.uk site.

Problem for me is that the new version does want to work on my machine - in fact I just came back home to find that part way into a recording this evening the machine went into a Windows crash and rebooted. The Windows Online Crash Analyser says that it was in the nVidia video driver ... which is odd given that I was recording the BBC Radio 3 in background and there was no-one using the machine.

Anyway - it looks like DigiTV is not reading the registry after the first read. So ... a nasty temporary workround might be to set

NebulaDigiTVAllowForceExit=1

in dabdig.ini

This will make DABDig try and shutdown DigiTV before adding a new timer entry and then restart it.

DABDig creator

Hopefuly Nebula will resolve this with a new build - it really does look like a bug in the way that they read (or in fact, not read) the registry when busy doing something else.

Hence ... it does not spot the new request.

DABDig creator

Issue still exists in 3.5.10

DABDig creator

According to Nebula "scheduling from Digiguide is not supported in the newer versions as there are now multiple processes and Digiguide does not know which process to communicate with". Hmm. I've had the same problems as described here, I'm using 3.5.21 because I have a slave tuner. But the good news is that last night I gave in to temptation and changed dabdig.ini so that it would schedule with Nebula via the Web interface - and it just worked. OK I had to adjust the baseyear etc, but it just worked. Now the bad news - having got the scheduling to work, I noticed that only one of my tuners appeared to be working. Or more accurately, only my slave tuner seems to work - and almost immediately complains that there's no master unit, and stops working. The master unit doesn't seem to work on it's own either - I think it might have died Typical, just when things are looking up.

Edited by Wilko on Wednesday, August 23, 2006 - 3:53:48 AM

incidentally, I also have a wavefinder, and have to run a machine especially for it - and the whole idea of the slave tuner thing was so that I could pension off the wavefinder and it's machine. *So close* and yet *So far*.

Interesting - I don't know why Nebula support got it into their heads that DABDig cares about multiple tuners.

This is the 2nd time that I have seen that being mentioned - and I know 100% for sure that they have received email from me and from someone else (who quoted my words) that this is not the case.

DABDig does not direct a request to a particular tuner - it is put into the single queue that is picked up by the DigiTV softare ... and DigiTV then determines which tuner to use.

There are a few people who are getting failed recordings - without using DABDig.

Common symptom is that the DigiTV icon shows that it is recording (sometimes showing the programme name and sometimes not) but no file is written to disk. At the scheduled end time the icon goes back to "not recording" - so it clearly finds the event.

Please direct Nebula support to this very long thread on the DigiTV forums - showing non-DABDig users having what appears to be the same problem.

http://www.digitv-forum.co.uk/viewtopic.php?t=1451

DABDig creator

I daren't breathe - DigiTV seems to be recording quite happily using both units via web scheduling and I don't *think* there's any zero length recordings, though I can't be completely sure. Anyway, I'll not be touching the system for as long as I can I'm only not sure because I got one .txt file (generated by dabdig) without a corresponding .mpg file, though I deleted it before I thought to check when it was, and whether I'd simply run out of tuners.

If you didn't queue anything for recording from the DigiTV GUI (by hand) - then you could use the dabdig.txt to work out what recording requests were made by DABDig around the time of the creation of the file that you deleted to see if there were too many conflicts for DigiTV to resolve.

DABDig creator