An early beta of DigiGuide 8.2 came out in June 2005 and the full release became available at the end of September 2005.

That build does not work DABDig older than 2.54b09.

The onyl significant difference between 2.54b08 and 2.54b09 is in the DABDig.dgmarker.

Just put the files into your DigiGuide directory and restart DigiGuide.

If you have customised your marker - then you will have to re-implement your changes before your restart DigiGuide... which were probably just changing some "false" to "true".

DABDig creator

Edited by Paul Webster on Friday, September 30, 2005 - 3:55:39 PM

It's tough to suggest improvements to DABDig -- Paul seems to be well ahead of the game on most issues... But I do have a niggle about the DABDig record marker icon as it appears in the DigiGuide interface. Actually, it's not a niggle, I think it's fundamental.

The record marker shouldn't disappear during recording. Worst case: you use Right-Click/Use DABDig to Record/Once on a program that has already started. The record icon flashes up and then instantly disappears. In fact you are recording. As DigiGuide, not (in my case) Nebula, is now your current sole interface to the recording mechanism it should be reflecting this change of state. In other words, there should be a "I'm recording now" icon that replaces the "Let's record this" icon.

Whaddyah think?

--

Chris

Unfortunately it is one of the built-in facilities of DigiGuide ... it removes the icon for one-off markers when they fire.

However, the good news is that in DigiGuide 8.3 (beta started this week) there is a new facility that allows a marker script to invoke a new marker ... I was planning to use this to add a new icon to show that this has been actioned.

I probably won't release this as an official change before Christmas - but the break around then should give me some time to play with the 8.3 beta and then include it.

I will try to remember to update this thread when/if done.

DABDig creator

I realised after I'd written this that I was probably being a bit preemptory calling the idea "fundamental". On reflection, the way it works currently is probably more fundamentally correct. DABDig has no business setting a marker saying "I'm recording now", because all it knows is that it's passed this instruction on to DigiTV, and _hopes_ the instruction is being carried out. I don't think DABDig has a way of monitoring the state of the Nebula stuff, does it?

If you're planning to have the post-Yule version of DABDig actually update the marker, it might be, er, fundamental to do something like checking that the recorded file is actually being created.

--

Chris

I agree with the principle - but in reality ... the marker handling is done by a combination of DigiGuide and a component of DABDig called dabdig.dgmarker.

The .dgmarker files are specially constructed Javascript modules built to a DG interface specification.

When they run - they only have access to the outside world within the constraints of the Javascript language and the extensions offered by DG.

So - checking to see if a file somewhere on the file systems actually exists is not that easy.

In my case it is even harder because the .dgmarker file has no idea what file name should be created and even less idea where the recording software will be putting it.

However, most recording that is initiated through DigiGuide is unattended because over time users tend to build up a set of repeating markers that capture what they usually want to see - if the marker turned blue and shouted it would probably still go unnoticed. Does not mean that I will not try to incorporate something - but might not be as high up the list as you would hope.

(Having DABDig itself, as opposed to the marker, check the recording progress and do something about ones that seem not to be working is a possibility and is already a bit higher up the list).

DABDig creator

Since 13 Feb 2006, all my radio recordings, using Digiguide (8.2, build 1026) / DabBar/ DabDig, have been empty files of 0 bytes! What's changed?

Edited by Alf Asprey on Monday, February 20, 2006 - 6:45:34 PM

Looks more like a DABBar/DAB-Device issue.

My reasons for saying that are:

The fact that recordings were requested at all shows that DigiGuide was working.

If you check the dabdig.txt, I expect you will see that the command line to DABDig does have the correct duration specified.

If you check the recording schedule in DABBar (e.g. via the Timers screen in DABBar [but do not let it remove old entries] or via the DABBar schedule.csv file) you will see that the entries are correct.

Stopping/restarting you DAB device (e.g. a reboot) might cure things.

If a Wavefinder - then perhaps unplug and replug from USB.

If you choose to listen/record from the native interface in DABBar ... does it work?

DABDig creator

Phew! A reboot seems to have fixed it. I was panicking, there! That's what you get for trusting the technology to get on with it's stuff, and not checking it.