Hi,

Have just been playing around with DABDig as I upgraded the software for my Hauppauge Nova-T PCI (909) from 2.17g to the latest Technotrend 2.19. However, DTVRecord won't recognise the software and DABDig is not working correctly.

After much tweaking, I have arrived at the situation where channels are being recognised correctly but the parameter passed to DVB-TV is wrong.

The .ini file looks like this: (cut out non-relevant sections)

...

OUTPUTTARGET=d:\tv

OUTPUTTARGETCREATE=0

PLAYIN=1

PLAYOUT=4

NOWOFFSET=0

DATEDIVIDER=/

FILENAMEDATE=1

FILENAMETIME=1

FILENAMESERIES=0

FILENAMEORDER=NDTS

FILENAMEDIVIDER=-

FILENAMESTATIONINPATH=1

SAVEDESCRIPTION=0

SAVEDESCRIPTIONPATH=

DEFAULTEXTENSION=mpg

SUPPORTDGSCRIPT=0

DEFAULTCATEGORY=Default

CATEGORYKEEP=

DEFAULTDEVICE=DVB

WRITELOG=1

CHECKLOCALTIMEOFFSET=1

INIFORMAT=0

SCHEDULER=0

SCHEDULERMAXLTH=258

POSTPROCESSRECORD=

POSTPROCESSRECORDPARAM=

POSTPROCESSRECORDDELAY=60

POSTPROCESSMSGBOX=1

REGUNABLE=Unable,Registrierungsschlüssel,Impossible d'ouvrir la clé de Registre

AUTOITX=0

ALLOWKEYSSUBSTITUTION=0

WILDCHANNELMAP=1

DETECTCONFLICT=0

CONFLICTGAP=0

CONFLICTDEVICES=

DAYSOFWEEK=Sun,Mon,Tue,Wed,Thu,Fri,Sat

NUMTOTEXT=Zero,One,Two,Three,Four,Five,Six,Seven,Eight,Nine

ALLOWEDINFILENAME=- _

REPLACEQUOTES='

MSGBOXTOSCREEN=0

INTERNALWEBSEND=0

INTERNALWEBSENDRETRY=1

INTERNALWEBSENDRETRYDELAY=5

TRACEFLAGS=4

...

TECHNOTRENDDVBDEVNAME=DVB

TECHNOTRENDDVBTYPE=PCI

TECHNOTRENDDVBPATH=C:\Program Files\TechnoTrend\TT-budget

TECHNOTRENDDVBCHANLISTFILE=DigitalTV-t.lst

TECHNOTRENDDVBCMD=DVB-TV.exe

TECHNOTRENDDVBCMDP1=/1

TECHNOTRENDDVBCMDP2=MPG

TECHNOTRENDDVBCMDP3=Stop 4000MB

TECHNOTRENDDVBPLAYCMDP1=

TECHNOTRENDDVBPLAYCMDP2=

TECHNOTRENDDVBPLAYWINSTYLE=3

TECHNOTRENDDVBSWITCHTOWINDOW=DigitalTV-t - skyDSL/PCI

TECHNOTRENDDVBSENDKEYSDELAY=10000

TECHNOTRENDDVBSENDKEYSTOWINDOW=F

TECHNOTRENDDVBMATCHNUM=3

TECHNOTRENDDVBFIELDNAME=1

TECHNOTRENDDVBFIELDKEY=26

TECHNOTRENDDVBFIELD3KEY=26

...

(note that I've had to tweak some of the technotrend lines)

The trace log shows, when trying to watch Five:

30/12/2006 16:52:44 - 2.57b12 - Trace:1 - "PLAY" "five" "05" "Jason and The Argonauts" "2006" "12" "30" "15" "35" "120" "Action adventure saga set in Ancient Greece. Jason encounters many a mortal foe in his search for the magical Golden Fleece, which will restore his father's throne to its rightful owner. Along the way, he wrestles with a multitude of monsters, including a giant living statue and seven sword-wielding skeletons. Director: Don Chaffey Starring: Todd Armstrong, Nancy Kovack, Gary Raymond, Laurence Naismith, Niall MacGinnis (1963, U, 3 Star)" "Film" ""

30/12/2006 16:52:44 - 2.57b12 - Trace:4 - Set device 0VB: Channel:05:

30/12/2006 16:52:44 - 2.57b12 - Trace:1 - Programme started 78 minutes ago

30/12/2006 16:52:44 - 2.57b12 - Trace:1 - Start time is now: 30/12/2006 16:53

30/12/2006 16:52:44 - 2.57b12 - Trace:4 - on:TechnotrendDVB - Original channel assignment:05

30/12/2006 16:52:44 - 2.57b12 - Trace:4 - on:TechnotrendDVB - Reset channel assignment to:05

30/12/2006 16:52:44 - 2.57b12 - Trace:4 - on:TechnotrendDVB - Checking field:26

30/12/2006 16:52:44 - 2.57b12 - Trace:4 - on:TechnotrendDVB - Matched:Five taken:233A3002324217810000

30/12/2006 16:52:44 - 2.57b12 - Trace:4 - on:TechnotrendDVB - No match on channel name or no number found

30/12/2006 16:53:44 - 2.57b12 - Trace:1 - on:TechnotrendDVB - Full command line: "C:\Program Files\TechnoTrend\TT-budget\DVB-TV.exe" 05

30/12/2006 16:53:54 - 2.57b12 - Trace:2 - on:TechnotrendDVB - About to switch to WindowigitalTV-t - skyDSL/PCI

Note that the channel number is being translated into the correct hex code, but then fails, leaving the original channel number in the command line. I can of course supply full copies of the relevant files if this will help, and do some debugging if I can see the source code.

Thanks,

Arnie

...in answer to my own problem, setting TechnotrendDVBMatchNum = 2 instead of 3 seems to do the trick, even though I have a DVB-T card and the documentation says this option will not work for DVB-T!

Thanks.

I have updated for documentation for the next release to say that it might not owrk for DVB-T (etc).

Since 2 is the default then I suspect that other users have been lucky that it worked for them without having to check the documentation and hence would not have changed it to what I had (incorrectly) recommended.

I have was a bit surprised to see this combination of messages:

---

Matched:Five taken:233A3002324217810000

No match on channel name or no number found

---

but the reason is that the entry that I found was not numeric ... there is an "A" in it.

So - I will change the code to check to see if the field is valid in Hexadecimal.

I think that if you can find an all numeric channel number in the Technotrend list then it might have worked when TakeNum was set to 3.

DABDig creator

Edited by Paul Webster on Sunday, December 31, 2006 - 6:27:58 AM

UPDATE:

Please send me your DigitalTV-t.lst file (plus dabdig.ini and dabdig.txt).

The reason is ... things seem to have changed.

In the old days, the number returned when using TakeNum=3 was a relatively short sequence - which I then converted to Hex to pass to their software. Now it looks like the hex number is coming back directly. So somehting appears to have changed with their 2.19 software.

Hopefully your dabdig.txt also contains some TraceFlags=4 output that covers your final experimentation when you got it working with TakeNum=2.

DABDig creator

...email has been sent with requested files. I think part ofthe problem was to do with matching the Digiguide name to the TT name.

Thanks for the file.

What I think has happened is that I had already allowed for the revised format of the file - but ... I didn't know that the more recent Technotrend softwrae for DVB-T was now using the same "key" as the DVB-S software that I had seen before.

Therefore - it is only the DABDig set-up page that needed revising. The defaults were fine for new installations but people with the older DVB-T software that did the Technotrend upgrade would hit this problem (which they can fix by simply returning the DABDig fields mentioned above to the their current default values).

DABDig creator

Edited by Paul Webster on Tuesday, January 02, 2007 - 5:01:46 AM