Logitech Squeezebox Touch on the way

- Squeezebox with touch screen expected by October 2009
First time I came across this was a posting back in May on, of all places, the Sonos forum. Someone (using the fourm name "walera") reported that he had been to a consumer focus event and the device was revealed as a new Squeezebox. I would have expected some form of NDA to have been in place - anyway - word was out.
Then over the last week-end some more info leaked out - including a picture.

It looks like a Squeezebox Classic with the VFD replaced by a 4.3" touchscreen.
But there may well be more - with reports of it also having a USB port and SD slot.
Various implications here - for example - this could allow for local storage of music and photos (show cover art when playing - and photos when idle).
There is also reported to be an infra-red presence detector that makes the screen spring back into life as you walk up to it - always fun when giving a demo.
Smaller updates also likely for the Boom and perhaps Receiver (the player half of the Duet).

Update 28/Jul/2009:
I found more details ... and have highlighted some new findings
Squeezebox Touch, model X-RC4 is countertop or wall-mounted (with included back-plate) music streaming system featuring:
• 4.3” LCD panel with capacitive touch screen
• High quality analog and headphone outputs (24bit/96k)
• Optical and coax S/PDIF outputs
• 802.11g wireless
• 64MB SDRAM & 64MB NAND flash
• SD card slot & USB host connector
• Internal speech-grade microphone and speaker – sound effects and preview
• IR sensor for remote control
• Ambient light sensor for dimming screen at night
• IR proximity sensor for detecting user approaching
• Digital temperature sensor for home automation

Interesting - perhaps there are some mistakes there ... but a microphone, small speaker and thermometer? Maybe for future expansion. Slimdevices have in the past included hardware that is not necessarily used when first released - for example infrared and headphone connector on the Squeezebox Controller.
It may well be running SqueezeOS - the same as in the Squeezebox Controller - since it gets a mention in the FCC report.

Also - an odd part number - "X-RC4". RC usually implies a Remote Control - and is nothing like the part numbers that Logitech Slimdevices folks use
(spotted so far ...
930-000074 - USA
930-000089 - Europe
930-000090 - USA/Canada
930-000091 - Aus/NZ
)

FCC test report
The implication from another document is that this is due for release by the end of September 2009 - my guess ... IFA Berlin is the launch.

Update 15-Aug-2009
It looks like Logitech web site folks made a premature release of information onto the main corporate site. It was spotted first in New Zealand and pulled soon after it was reported. However, that gave time for the details above to be confirmed.
Some more pictures as well ...







Prices:
No official word yet ... however, 3rd-party resellers are listing it around 300 USD, 400 Canadian, 450 New Zealand - implying approximately 220 - 250 Euro.
Plus there are tiny snippets visible on the Logitech site for replacement parts.
For example - a replacement power supply is 19.99 USD (same as Boom but more than Receiver) - which is the same price as a remote control (the smaller Boom remote is 9.99 USD and the bigger backlit one that ships with the Transporter is 29.99). It is not clear yet if a remote is shipped with the device although there are publicity pictures showing them together.

Update: 28/08/2009
First reported home use through a purchase rather than Logitech beta programme.
Nils' Picasa page
Forum post
Looks like a mistaken premature shipment because without a working SqueezeCenter 7.4 (being renamed SqueezeboxServer) it looks like it cannot do much.

Reciva adds native Live365 support

- Live365 from the device menu
It has been possible to play Live365 stations on Reciva devices for a long time - but with some limitations.



The stations had to be submitted to the database (or via the local My Streams) rather than being collected directly from Live365.
While "Professional" Live365 stations could be added easily enough, there had to be work-arounds to get the regular Live365 stations to work - and the VIP "Preferred" stations were more difficult again because Live365 requires the end-user to be a paying subscriber.

Other internet streaming devices, such as Logitech (ex Slimdevices) Squeezebox have had Live365 support for a long time.
Now Reciva has provided a free upgrade (initially for users of Grace Digital versions of the Reciva radios, but presumably with others to come as the brands approve it) to extend the menus to provide native access to Live365 - so that means 6,000+ more stations to try out!

Updated Pandora integration from Reciva

- First Reciva-based radio with dedicated Pandora buttons

Reciva announced their plans for official Pandora support at CES January 2008 - with a limited number of brands initially supported, the first was Grace at end of May 2008.

In April 2009 there was another related set of announcements - one was just to say that there are a few more brands with Pandora support. But I found the other more interesting ... for a couple of reasons.

The press release says "Livio Radio’s sleek features puts Pandora® at your finger tips".


First there are like/dislike buttons on the device and the remote control.
OK - no big thing (love/ban has been on other systems before but I think that this is the first time on a dedicated internet radio).
Second though is that Livio appears to be a sister company of Myine who recently released their Ira device which is using vTuner.
This is not the first time that a brand has gone with more than one supplier - but I don't remember anyone else having 2 suppliers so quickly.

New internet radio from Myine - ira

-

Massimo Baldini of Myine Electronics (Ferndale, Michigan, USA) replied to an email that I sent back in January to ask about this new device. The reply came recently to say that their new internet radio was nearly ready to ship ... and today an official announcement to say it is now available.

The form-factor is somewhat like a Logitech Squeezebox Classic - and like that device, it does not have its own built-in speakers.


So - connect up via RCA to powered speakers or hi-fi amp - set the wi-fi parameters (no Ethernet on this one) and off you go.
I think that the radio database is powered by a customised version of the vTuner system.
It comes with a remote control (and no local controls) - and has a fairly large (for this sort of device) white/blue LCD display.

Listed at 150 USD - with more details over at:
http://www.myine.com/ira.php
(the user guide is in the Help section)

Do you want everyone to know what you record?

- DABDig and Twitter
More for a bit of fun than a serious practical use, I have added some support for posting to Twitter from DABDig.
So - if you are automating your recordings
- e.g. DigiGuide -> DABDig -> Windows TV software
then you can now send info about what you are recording to your Twitter account (or in theory to other web-based services with an equally simple interface).

Maybe it will remind someone to switch to watch the same thing. I think I'll add the facility to hide shows by name though just in case people do not want some of their guilty pleasures highlighted (e.g. "Desperate Housewives" gets timeshifted here).

You can see some examples in Twitter
http://search.twitter.com/search?q=%23DABDig

I have not released this test version of DABDig yet - but if you already have a released version up and running and you have a Twitter account and fancy sharing your recording details with the rest of the Twitter-world (not the shows themselves - just info about them) then contact me (address is at the top of your dabdig.ini).

New internet radios from Grace Digital

- New models for USA buyers from Grace include battery power and iPod dock
Before Christmas, Grace Digital said that they were going to be bringing out some new Reciva-based internet radios in early 2009.
They have now released the details and it looks like products should become available in February/March (update: one of them is not Reciva-based).

One of the radios features an iPod dock (not just an Aux-in socket). Internet radios with iPod docks are an interesting development. There are other manufacturers who have done the same thing, but it does blur the edges between internet radio, digitised music at home and personal media players.
Someone with an iPod that can handle Wi-Fi can achieve something very similar by getting a lower cost iPod speaker dock and using one of the many (free) internet radio players from Apple's AppStore.
Arguably it is not quite as easy to use - but it also brings many other functions.
However, if the person with the iPod sticks it in their pocket and goes out ... then the speaker dock becomes useless - but that is only important if there is still someone around to listen!
For people with their music collection stored on a computer - they can get to it via UPnP and other remote media streaming protocols or possibly over a shared file system and, of course, while sitting at their computer ... so they would probably not need the iPod feature of an internet radio.
Grace have neatly side-stepped the issue by making two versions available - one with and one without the iPod dock. You can pay your money and make your choice - with a 50USD difference in the models.
This option is something that some of the Pure advocates think that should have happened with the Avanti Flow.


So - what have Grace announced? In essence there is an update plus 2 completely new models, including one that is battery-powered.

The update (GDI-IR2000 and IR1000) updates the ITC-IR1000B by using what looks like the same casing and adds 5 more presets (via a new "Shift" button as seen on other Reciva-based radios), software controlled tone settings and, for the IR2000, Aux input plus a small remote control.


To accommodate the "Shift" function within the pre-existing case layout, the buttons go through some renaming and it looks like "Browse" and "Reply" have been replaced by "Retrieve". This will confuse established Grace and Reciva users if they ever need to help newcomers via the forums.



The new models come with some variations.

The GDI-IR3000 has 2 speakers and a variation with an iPod dock (IR3020) - both available with a richer remote control (offering 99 presets).




The remote compounds the "Reply"/"Retrieve" confusion referred to above by adding "Recall".
No indication, as yet, of the power of the speakers, but maybe it is 2 of the old ones - i.e. 2*4.5W

The final new model is the GDI-IRP600 (presumably "P" for portable) and is their first with battery-power.
From the user guide it looks like it is not Reciva-based. The menu structure is different and is presumably using the vTuner bask-end.
There are not many battery-powered Wi-Fi radios.
One big reason being the amount of power that is drawn when trying to run a Wi-Fi connection when a long way away from a wireless access point (for example - down at the end of the garden). Plus, if you are much further away (maybe out on a picnic) you will probably not find any wi-fi to connect to!
However, by including an FM tuner, that draws a lot less power, it does mean that this becomes a portable device that should be able to be taken away from home for the day or longer.


The recent addition of support for the internet versions of the Sirius satellite content via the Reciva platform (although requiring a paid subscription to Sirius) and possibly only available to Grace radio users, will no doubt be of interest to many listeners in USA.
Sonos and Logitech/SlimDevices have had Sirius support for a while - but Grace has the potential to bring it to a new entry-level price.

More at http://www.gracedigitalaudio.com

TEAC internet radio finally reaches the shores

- TEAC internet radio finally reaches the shores
Announced back in August 2008 was the TEAC Reference 380. A mini hi-fi with numerous components. List price around 500GBP. The tuner (T-H380DNT) - available separately for around 240GBP features FM, DAB and internet. The internet part is not mentioned very much - and I still have not seen the manual for it (it was still not on the TEAC UK site in early January). UPDATE: Manual now on-line.

The big brother system - the Reference 600 also has internet radio.

No hints about which internet radio database it is using - but since they usually source their DAB from Frontier Silicon then I presume it will be vTuner like the rest of the FS-based devices. UPDATE: Confirmed from the user manual

Nokia enters the internet radio device market

- Nokia enters the internet radio device market
Nokia has been building a database of radio stations and been heavily pushing "Comes with music" on some of its newest phones. Soon there will be a new device to take advantage of this - "Nokia Home Music".

Features internet radio (wired and wireless), an FM tuner, analogue and digital out, analogue in, USB (to play from external disk), headphone socket - and a 3.5 inch colour display.
Looks like it has a single 10W speaker and comes with a remote control - plus can be controlled via UPnP.
It was announced in early December 2008 and should ship around March 2009.

I have not seen anything about the price yet - nor anything about which audio formats it supports.
To be a success in the UK market in particular ... it will need support for BBC Listen Again. If the work done by BBC/Nokia to get BBC iPlayer support for some of the phones has been learned from in other parts of Nokia ... then this could be a serious contender.
http://europe.nokia.com/homemusic

New multi-function devices on the way

- New multi-function devices on the way

Both Tangent and Pure have new devices that seem to be coming out in time for, what I am sure they hope to be, a Christmas sales rush.
Both have internet radio, plus DAB and FM also with the ability to play from a USB attached disk and support for playing your own music held on the home LAN.

The new Tangent model, NET-200, is another Reciva-based radio - like their Quattro.


This time it looks somewhat like my old Audiotron that I referred to in an earlier posting. It is a component hi-fi sized device - with no speakers. So, you add this into your existing hi-fi (including via a digital-out) or add powered speakers.
More details at the Tangent site.


Pure's second internet radio is the Avanti Flow.

This does have speakers - and an iPod dock.


Both are towards the top-end of the price range for people who are simply looking for internet radio - but they do provide more than that.

BBC socialises radio listening

Back in May BBC showed off Olinda - a quirky internet radio prototype that tells your friends what you are listening to and allows you to tune in to what they are enjoying. People have been using Facebook, MySpace, Twitter and other sites to post updates to tell their friends what they are doing. Last.fm shows what music people are listening to - so why not have something to tell people what radio programmes they are listening to now?

Well - I'm not sure that it is very interesting! But then I wasn't convinced by the facility in Facebook etc. Knowing that Harry has missed the bus may well be important to his employer who was expecting in on time for once or his girlfriend who faces missing the start of the film again but is it really more than a gimmick? If Twitter cannot sustain the cost of sending SMS in Europe will users pay for it?

However, I can see that aggregated information about listening habits could be useful, especially to advertisers, commissioning editors or public service broadcasters wanting their charter renewed - but I doubt that many people will switch over to listen to a programme that they had forgotten about because some of their friends are.

But - now with RadioPOP going live - http://www.radiopop.co.uk - it does mean that there will be data collected and published in full colour.


Right now it is not directly linked to the popular BBC iPlayer - and only provides live streaming (not Listen Again) but it will be interesting to see how much use it gets.

At least two suppliers of the technology underlying many internet radios are based in the UK - and provide access to the BBC live and Listen Again programming. If they add support for this as well then it will give it an extra boost. However, once it gets into BBC iPlayer then the figures really will make interesting reading.

New internet hi-fi devices - Pure and Intempo

- Pure and Intempo with new models

All sorts of product information comes out around the time of IFA in Berlin.
The official announcement of the Squeezebox Boom that I mentioned in the previous blog entry was timed to coincide with IFA opening - and indeed shipping started on the same day.
Other products that were announced around the same time include the Intempo RFI-W and the Pure Evoke Flow.

They are both priced around the same level at the Squeezebox Boom but have a few immediately obvious differences. For example - both Pure and Intempo include regular FM radio.

Pure also include DAB (with promise of availability of future firmware upgrade to DAB+).
The Pure device has a single speaker and, like others in the Evoke range, can have an extra speaker added at additional cost. Another costed option is a ChargePak (rechargeable battery to you and me).
It will be interesting to see where their internet radio database comes from. The front-end to it is at http://thelounge.com but at the time of writing this it is not open. My guess is that the data comes from vTuner but I am less confident about the portal itself. Logic says that it would be a varient on that offered by Frontier-Silicon given the relationships between Pure, their parent, Imagination Technologies and Frontier-Silicon. But perhaps Pure have done their own to differentiate themselves from other brands using FS.

Intempo include an iPod dock and ability to play from SD memory card and USB disk.

Again it will be interesting, to me at least, to see where they are sourcing their internet radio technology from. They used Reciva for their first model, the GX-01, but a few of the early suppliers of badged internet radios are trying things with more than one manufacturer. It is due out at the end of September 2008

Logitech have put a lot of effort into the audio design of their new Squeezebox.


On announcement they published this great document. It contains a lot of technical detail, written in a very easy to read way - Logitech Squeezebox Boom Audio Design White Paper (PDF)
As usual, senior staff from Logitech have been active within the SlimDevices forum to answer questions about the new system. There was a private beta program running since April 2008 with some of the most active community members getting the chance to try things out and give feedback. I think that this approach is one of the big reasons why SlimDevices has both great products and passionate supporters.

It is going to be interesting to see if Logitech can steal a march on the competition by being available a full month earlier.
Will people go for what looks like more ways to listen from Pure and Intempo?
Are the audio qualities of the Squeezebox Boom going to be important?
Will the ability of the Pace device to run on an optional rechargeable battery make it more attractive to the outdoor types?
Will this new activity spur Roku into kicking new life into Soundbridge Radio?
How about Philips - I should really go and have a look at their new model to see how they have moved on since I last tried one a few years ago.

Or - will people seem them as much of a muchness and buy based on what they can find in the shops and which one has the most appealing looks and/or cheapest price?

Digital listening - part 3

- Digital listening - part 3

Having achieved a stable and working set-up, with local media files and internet radio playing at home, including the ability to synchronise between 2 rooms, we really had all that we needed.
However, I still wanted a bit more - internet radio in the bathroom. There were two different drivers. One was to cover the long relaxing soak in a warm bath and the other was to have news (from France) in the morning while getting ready for work. Putting electrical equipment in the bathroom is not something to undertake lightly because of the hazards of mixing power and water or steam and electronics - but trying to use the wifi-enabled PDA with wet hands or steamed-up glasses was not going to work!

So it would be used a relatively small amount of time per week and would have to be easy to operate. For the small amount of use that was expected, I could not justify putting an extra Logitech Squeezebox, plus powered speakers, in there. The user community had been calling for an all-in-1 box for quite a long time ...
but there was no word (not even a rumour ... until on 6th August 2008 - when unofficial news of the Squeezebox Boom leaked out).

I was interested in trying out an "internet radio". One of my brothers had already seen my home set-up and wanted to do something similar. He has very poor FM reception in his bedroom and wanted to be able to listen to BBC Radio 4 last thing at night and on waking up. There were a number of potential solutions (for example - add an external FM antenna, or try and get it via longwave). In the end he bought a Logik IR100 - from memory it was about 130GBP at the time.

It was up and running very quickly. The built-in support for RealAudio plus Reciva maintaining an updated list of the BBC Listen Again programmes meant that it easily meet my brother's needs. (Reciva provides the engine inside the box and is the provider of the station list).
Not to be outdone ... another brother went a slightly different route - and bought the Roku Soundbridge Radio. This device also features a conventional FM and AM receiver as well as internet streaming - so looks very attractive to a radio fan.
He is pretty pleased with it but has a few usability issues plus recently the power supply failed (just after the warranty expired).

Reciva already had a few other brands using their technology - but all were priced higher than I was prepared to pay for a 3rd device ... then the Logik IR100 went through some price drops. PC World was selling them for 60GBP and eventually 50GBP. My resistance was broken one week-end as I was buying some ink and paper ... within minutes of getting it back home I was listening live to stations from around the world.
It is not wrinkle free - but more than adequate for the way we are using it.
The firmware for the Reciva-based radios is upgradable over the internet, but the process is controlled so that firmware upgrades (officially at least) are only available for particular models once the brand agrees. This does mean that there are all sorts of different versions of the firmware on different models - which can lead to some frustration when a bug fix or new facility is available to some radios but not others.
There were a few bugs that affected the Logik IR100 but the assumption was that DSG would not be interested in agreeing to an update because they were probably trying to clear the stock by dropping the price. In the end, I made contact with one of the senior members of DSG to ask if anything could be done. I had a reply pretty quickly (over a week-end) saying that it would be researched. After a few weeks there was an update to say that it looked pretty likely and then a few weeks later I had confirmation that a new firmware release would be available very soon. An excellent outcome and confirmation to me that a simple request expressed clearly, logically and without emotion ... really can work.
The Logik IR100 has moved up in price since then - but I think it is still worth looking out for good deals.

The Reciva platform has continued to spark my interest in other ways. Reciva asked if any users would be willing to help process the queue of station add/modify requests. I volunteered and was soon involved in working out the right stream URL for attempted add requests. I am not sure how many I have fixed but I expect it is well over 1000. I find it a good way to stimulate the mind in the morning before breakfast!

This is a fast moving area - so I do suggest that you do your own investigation before buying. Models that I referred to might no longer be available or issues that I had may well be resolved. Feel free to ask questions via the Comments area.

28-Aug-2008 - Updated to include official link to Squeezebox Boom

Digital listening - part 2

- Digital listening - part 2
Having converted some of the family to the pleasure of using a stand-alone device to play internet radio and local music files, the next step was expansion. Putting another device in an area that was not really suited to having a regular computer.
There were a few candidates that seemed to be offering something similar. They are some subtle and not so subtle differences between them (such as whether or an additional application needs to be installed, learned and run to handle core functionality, functionality of the remote control and support for many different formats/protocols for streaming - including the ability to play back material from the BBC Listen Again library).

I had seen a few at CES in 2004 and 2005 and had already been researching.

In general, I discounted devices that could not be controlled from the device (plus its remote control) itself (i.e. if it needed a TV to be on, or if the only way from from a computer).
My shortlist had come down to Sonos, Philips, RokuLabs and SlimDevices (now Logitech).

Sonos
I decided that although it looked great, it was too expensive for me and did not seem open enough for what I had in mind.
However, I have subsequently recommended it for closer inspection to friends who had both more spare cash than me and less desire to get into the technicalities.

Philips
They seemed to have the only device that really was a conventional mini hi-fi system, with CD-player, regular radio and built-in speakers but it was taking forever to come to market in Europe.
When I tried it out at CES I found the menu system too cumbersome and unresponsive - plus the internet radio function seems to only support a "walled garden" approach with no ability for me to enter my own stream URLs, plus there was no support for Microsoft WMA which would have been needed for many internet radio stations. I'm sure that either I was wrong or things have improved since then, but since I could not get my hands on one to experiment with in the UK at that time - I gave it a miss.


RokuLabs
I did like the fact that, like the Audiotron, it has a built in filesystem client so that it can play locally held music files without necessarily having to run an extra application.

However, it had no native support for RealAudio format - which meant that I would not have an easy way to listen to the BBC Listen Again material.
Running a connection through a local transcoding proxy could have been one way to do this - i.e. run a local server that can handle RealAudio format and have it translate the data, in real-time to something else. The loss in quality after going through such a translation could be grating, but given the relatively lo-fi that is used for most internet radio then I decided that this need not be a big issue - but I wanted to experiment.
Back then ... the RokuLabs devices included the ability to work with the then current SlimDevices SlimServer. SlimServer was (and still is - but is known as SqueezeCenter nowadays) free to download and use. So I decided to try it out since I would be able to evaluate the free software for use with either vendor.

SlimDevices (now Logitech)
As I read more about SlimDevices I was impressed with the approach they were taking.
The user forum was busy and supportive with active engagement by the manufacturer - it was clear that new functions were being added based on user requests. They seem to have put a lot of effort into the audio qualities of the box and had a good looking screen and menu system.
However, it did look like an old-fashioned bedside clock radio (the subsequent SB3 updated the looks, and the later Receiver plus Controller i.e. Duet goes a step further).

But, there was a free download available of a software-only emulation of the Squeezebox.
So - I downloaded the Slimserver and Softsqueeze. I had both up and running in minutes.
It was easy and extend. Softsqueeze allowed me to try out a lot of things, including putting some add-ins in place. It all worked really well.
So - I placed my order for the newly announced SB2 and it arrived direct from USA at the end of March 2005.
It proved so popular at home - that a 2nd followed not long afterwards. Sometimes we set them to synchonise playback so that we can set-up a playlist from the kitchen in the evening and then continue without a break when we eventually arrive in the bedroom.

So I had decided to go with something that seemed to have good basic functions and an active user community who were developing, with the support of the manufacturer, all sorts of interesting add-ons. I did not expect to use many of them (for example showing the scores for sports that I am not interested in) but there were some that looked promising (for example providing the BBC Listen Again content).
It could be argued that having something that seemed to require additional 3rd-party software to achieve what would lead to an overly complex solution and would need a computer to be left on to run it.
Well - I do not have a big concern over something being complex under the covers - provided there is sufficient information and support for those that are willing and able to dabble. If new functions can be added that can then seamlessly appear in the menu at the device so that everyone in the family can quickly understand how to use it if they need it then I'm all for it.
As for running a computer all of the time - although it is not strictly necessary to do this with the Squeezebox (SqueezeNetwork provides access to internet streams without need of a local server and the device also supports broadcasting a Wake-On-Lan packet to try to restart a slumbering server) ... I already run a PC all day so that it can easily generate the TV and radio listings that I upload for other users of DigiGuide (I generate programme schedule information for end-users to import into DigiGuide of over 100 stations - maybe that could be the subject of another blog entry).

---

Next steps
All of the manufactures featured above have released new models since I was doing my research - and there are other players in the market.
I still had an itch ... I wanted internet radio in the bathroom so that I could listen in while having a long soak. There were numerous possibilities - and apart from kicking myself for not putting some speakers in the ceiling when we had the bathroom refitted ... I was happy to start searching again. Slimdevices/Logitech were steadfastly not making any noise about producing a transportable device with built-in speakers. RokuLabs had finally shipped their SoundBridge Radio and there were other small devices that looked a bit like regular radios that could be interesting. More on this later ...

Digital listening

- Digital listening

As DABDig, the application, has needed less of my attention over the last couple of years (partly because it already handles most of the recording possibilities with stacks of TV and radio kit - but mainly, I think, because there are much more sophisticated applications being shipped with modern computers that, for most people, obviate the desire to go and and find extra tooling such as DABDig plus the basic TV listings available in Microsoft Media Center and other similar applications mean that they are unlikely to find DigiGuide) I have spent some time getting involved with the technicalities behind internet radio - and indeed I even help run one.

I decided to post a few words about it here to see if it sparks any interest - and if it does, then I may well add more detail in the future.

How it started for me:
I have listened to radio via the internet for a long time - I don't remember when it started, but I suspect that extended hours of listening coincided with my first broadband connection at home back in 2002 (I was on the free trial being run by my cable TV company to provide broadband wirelessly, that ran for about 18 months I think - which sounds somewhat odd, but their old cable infrastructure in my area was not able to provide internet and I didn't want to have to add an extra line from a different telcoms company to get ADSL).
In January 2003 I released an update to DABDig to drive Total Recorder - so that it would be possible to schedule recording of internet radio streams from DigiGuide - because back then there was very little "Listen Again" or "On Demand" functionality on radio stations around the world.

Over the years I have had, and still have, various internet radio devices. In general, these look like regular radios or a hi-fi component (so get put in places that normal home PCs don't go - such as kitchen, dining room and bathroom) and are very easy to use for all of the family. I have taken an active technical interest in the technology and the communities built around them.
The first that I went for was the TurtleBeach Audiotron.
Sadly no longer available to buy new - but even now, some years after all support ended, it still stands up well against today's offerings.
This device can play audio files from your home computers or NAS but, via a facility called TurtleRadio, it could also play thousands of internet radio stations. This was playing most nights after we had the family dinner (music during dinner tended to be Jazz FM (when it was still just about a jazz station) or PlanetRock dependng on whose turn it was to control the DAB radio in the dining area).
After a few months of twiddling the dial to pick up different genres and countries from around the world - we ended up with a staple diet in the presets - FIP and FranceInter were always popular and remain so now, the world music station on RadioIO (RadioIO is still going but that station and compiler has long gone).

We were very happy with internet radio - and wanted (well I did anyway) to buy another one to put downstairs to augment or even replace the DAB receiver. TurtleBeach were rumoured to be making something new ... so I held off for many months to see what would arrive. In the end they announced the some updated models plus the MediaTron (same idea as the AudioTron) but could be controlled via a TV interface, including showing cover art. I was one of the few that managed to get my hands on one and have a play - on their booth at CES in Las Vegas in January 2004.

However, the device never made its way to the stores. Eventually TurtleBeach pulled the plug on the whole thing, not just the new models. So something else had to be done! I had already been researching a few other devices and had used the CES show in 2004 and 2005 to have a look at them in more detail (it was a happy co-incidence that I had to be in Las Vegas at the same time as CES for 2 years in a row).

So - what did I go for? More about that in the next blog posting.

DABDig 259b26 release coming soon

- DABDig 259b26 release coming soon

I decided to make a release - bundling up all of the updates from the last few months.
Some of this is experimental since there were not many people who tried it some of the requested features so get in touch if something new does not do what you expected.

- For ATiMMC there is a digital-only device which has different registry settings - start to adapt.
- For ChrisTV the date field follows local Windows settings so make it configurable.
- For WinTVPVR - set default recording windows style back to Restore (WinTVPVRRecWinStyle=1) because running it maximised prevents recording with some versions of Win2K.
- Add experimental support for Microsoft Media Center Edition (MSMCE).
- Add substitutions for GMT start and end date/time.
- For GBPVR - Added optional Priority field because it looks like new versions of GBPVR require it.
- For GBPVR - Added conversion_profile.
- For GBPVR - Added call to new function to force recording schedule to reload because recent GBPVR versions no longer use a timer to poll database.
- Add a general ability to mess around with the timezone when working on UTC date times.
- Added support for automatic detection of WinTV background recorder (BGRecorder).
- Apply InternalWebSend to Nebula DigiTV to provide more control when web-based scheduling is used.
- For Topfield - Add support for substitutions in file names to make it easier to use MyStuff TAP.
- Add support for DVBDream.
- For DVBViewer - add support for parameter passing on record requests.

This also includes the features from 2.58 that I made available to some people but did not announce - namely:
Add new substitutions - for Tab ($HT) and Null ($NU).
- For TiVoWeb - allow parameter substitution so that extra fields can be inserted.
- Put leading zero in the end date/time fields - for people using the substitution facility.
- Note - this might have an unexpected effect on some devices that take textual date/time fields.
- but initial checks of them look OK. If recordings used to work and now do not with this version then this might be the reason so let me know quickly!
- For TwinHan VisionDTV - new field mechanism to add/replace fields in schedule file to support new in VisionDTV 2.65 ProgarmName (sic).
- Add parameter substitution D2 and E2 for 2 digit start and end year.
- Start to add Compro Videomate

Vista SP1 and XP SP3

- Vista SP1 and XP SP3
There is a reported bug introduced by the recent service packs from Microsoft.
It is to do with the way that VBScript processes dates.
It is possible that this will have an effect on some of the scheduling performed by DABDig.
It is related to the date handling routines. In general, DABDig handles the date in a non-locale specific form so that the same code runs everywhere, but this newly introduced bug might cause some problems.
If it proves to be a problem for end-users and if Microsoft do not release an update soon then I will put in a generic workaround.

More about this here: http://support.microsoft.com/kb/951978/en-us

Let me know via Comments to this post if this affects you (in more than simple presentation ways).

DVB Dream

- DVB Dream
I have had a request to add support for DVB Dream.
After a quick look at the documentation, it looks feasible - so starting on it now.

Various updates

- GBPVR
Added call to new function to force recording schedule to reload because recent GBPVR versions no longer use a timer to poll database

- General
Add a general ability to mess around with the timezone when working on UTC date times

- WinTVAdded support for automatic detection of WinTV background recorder (BGRecorder)

- Nebula DigiTV
Apply InternalWebSend to Nebula DigiTV to provide more control when web-based scheduling is used

- DVBviewer
Add a 2nd instance of DVBViewer

(259b19)

GBPVR

- GBPVR
Looks like GBPVR has added a new field - priority - and made it mandatory. Also a new optional field conversion_profile.
So added ability to enable them in DABDig but with the default that both are turned off so that it does not cause problems for existing users with older versions of GBPVR.
(259b08)

Breaking in a new domain name ...

- Breaking in a new domain name ...
I finally decided to register a DABDig domain name.
I am still leaving the original site in place for now but will probably switch over on the next official release.
Nothing new to see - but you can try it at http://www.dabdig.co.uk

Microsoft Media Center Edition (MCE)

- Microsoft Media Center Edition (MCE)
DId some more work on direct scheduling into MCE via click-to-record. Looks promising but since I do not have MCE then I need someone to test it.

(259b02)

ChrisTV

- ChrisTV
Had a report that the time format in ChrisTV was different. Rather than dd/mm/yy it was yy.mm.dd
There was already code to handle USA format (mm/dd/yy).
Took the opportunity to make it completely comfigurable by adding a new field - ChrisTVDateSyntax. Default syntax is now $DD/$DM/$DY but can be easily changed in dabdig.ini
Solution here is to set it to $DY.$DM.$DD

(259b01)

GBPVR

- GBPVR
Recent versions of GB-PVR default to using SQLite as the underlying database, rather than the "Access" mdb format.
This causes a problem for DABDig because I do not yet have a way to read/write the SQLite data.
Therefore, to use DABDig with GB-PVR you will need to configure GBPVR to work the old way.

TwinHan VisionDTV

- TwinHan VisionDTV
TwinHan have changed the format of their channel listings file in version 2.6.5 of their software (might have been done slightly earlier, but the first report I had of problems was with this version).
So, if you have upgraded your TwinHan software from a previously working DABDig/VisionDTV installtion or you are a first time user with new TwinHan software then modify your dabdig.ini as follows:
VISIONDTVFILEFREQUENCYPOSITION=105
VISIONDTVFILESYMBOLRATEPOSITION=109
VISIONDTVFILEPOLARIZATIONPOSITION=113
VISIONDTVFILEAPIDPOSITION=169

(note - newer versions of VisionDTV might need different numbers)

Also - TwinHan added a new optional) field into their schedule. Called ProgarmName (sic). So - I have added support for this and potentially other new fields in the future by a new configuration item in dabdig.ini - called VisionDTVExtraFields

(258b03)

Parameter Substitution

- Parameter Substitution
Added leading zero for single digit end date/time fields so that it is consistent with start date/time and makes better looking fields when used in file names.
This could potentially affect some devices that take the textual end date/time as a parameter, butI have reviewed them and I think it is OK because they seem to accept 2 digit fields in the start date/time.

(258b02)

TiVoWeb

- TiVoWeb
Added parameter substitution to TiVoWeb.
Although the parameter list in the TiVoWeb interface is pretty much hard-coded because of the messing around with date/time fields, I had documented a possible way to hard-code extra parameters.
This was by adding new fields to the start of the variable part of the URL in the dabdig.ini
This works well - but requires the parameters to be fixed. By now making them use the substitution mechanism it means that other fields can be calculated dynamically - for example, a version of manrec supports the episode name being passed in, so this could be handled in DABDig by adding Episodestr=$EP& to the end of the URL in the ini file.

(258b01)

257b12 is now available

Decided to make a release of the various changes.

So - 257b12 is now available.

- General - Allow time-delayed retries on failed internal send of URL.
- Nebula - add the new (3.5.21) PostTime/PreTime fields just in case future versions of their software rely on it being present.
- WebScheduler - switch from using the programme name to FileNamePartial.
- GBPVR - add more flexibility in handling channel name.
- OnlineTVRecorder - Add support for OnlineTVRecorder.
- General - Allow double-quote in synopsis to be converted because it can break external systems when passed as a parameter.
- TiVoWeb - allow configuration of length of synopsis sent to TiVoWeb.
- Nebula - make the executable name configurable to support the HD version (and also version 3.7 of DigiTV).
- WinTVPVR - add mechanism to minimise an already open window via AutoItX.
- General - Add more generic flexibility in recorded file name so that all devices can benefit from the Substitution facility.

TiVoWeb

- TiVoWeb
The manrec application that DABDig calls has been updated a few times by various people since the DABDig support for it was introduced long ago.
Once of the new features means that it can be called with a textual date rather than seconds since 1970. Does not really matter for DABDig since it already does the calculation using absolute time but allowing this new field could make the URL more configurable from the dabdig.ini
A second new field is space for episode information, e.g. title or series/episide number. Incorporating this is easy enough (at least the series/episode numbers) but the problem is doing it in a way that does not send meaningless stuff when there is no series/episode information to pass - but again - possible to do.

Not started on this yet - so this is here as a memory jogger.

TiVoWeb

- TiVoWeb
The manrec application that works with TiVoWeb has maximum sizes for textual fields - e.g. description and title are set to 40 characters.

This can mean that these fields get truncated by DABDig before sent over.
One user wants to correlate information from TiVoWeb/manrec with the post-processing function in DABDig. However, because of generic descriptions, it is possible that two different shows will have the same first 40 characters in the description.
So - the user has made a modification to manrec (or some other PHP script) to be able to accept more than 40 characters but then to truncate later in the process for the TiVo.
So -I changed DABDig so that the maximum length that DABDig sends to TiVoWeb/manrec can be configured.
Note - it is possible that a very long description could fail to be sent over via the HTTP Post operation.
Anyway - change made
(257b08)

Build 256b07

- OnlineTVRecorder
I came across http://www.onlinetvrecorder.com - a site that allows you to request a personal recording of a programme from a (German for now) TV station.
Seemed easy enough to support so added it in. Still some issues to be resolved with timezone handling and perhaps a bit more flexibility with channel naming - but the basics worked.
(256b06)

- PostProcessing
Double-quotes can appear in programme synopsis - which can cause problems if trying to substitute via a command line.
Added new (default but configurable) ability to replace double-quote with single-quote in synopsis.
(256b07)

GBPVR

- GBPVR
Had a forum posting from someone trying to get this to work.
It was giving database access problems (GB-PVR stores its data in a database).
The real reason behind this was that the channel numbers that DABDig was being passed did not correspond with the numbers in GB-PVR. Perhaps I need to change the code to lookup against a different field. Anyway, in an attempt to work around this the savvy user had a go at using dabdig.map thinking that the problem was with the channel names.
This confused things further since it meant that DABDig was trying to use a text string to compare against an integer value in the database and hence the database lookup errors.
So - worked out a way around this by simply removing the channel numbers from the DigiGuide display and renaming the channel in DigiGuide to match the names in GB-PVR.
This worked because DABDig tries to match the channel name against the name in GB-PVR if there is no channel number present.
Meanwhile, I changed the code to make the look-ups more controllable and also for a name look-up if the "number" has non-numeric characters. This means that a simple dabdig.map entry can be used to change the name - i.e. no need to modify anything in the DigiGuide GUI and map entries only required for channels that have different names.
Will probably make another change to make configurable the field that DABDig tries to match when performing a channel number lookup which then might make it all work automatically for new users with no extra configuration required.

256b29 available

- General
I decided to upload a version of the latest beta of 2.56.
Many of you already have earlier builds of this version. Your current version number is shown at the top of the dabdig.ini

DigiGuide 8.3 is still in Beta - so I have kept back some of the changes (to the marker) that I have been making in preparation for it. The marker in this build of DABDig works will all version of DigiGuide back to 6.x including the 8.3 beta.
However, the next release of the marker will only work with 8.3 and includes some new features that will mean that users no longer have to customise their DABDig.dgmarker if they want to enable the main hidden features. I do not plan to release it until DigiGuide migrates all users from DigiGuide 6.x and 8.2 to 8.3

Note - customised DABDig.dgmarker users (DigiGuide only) - there is a new marker file in this release.
If you have never changed yours (or never had a special release of the marker directly from me) then do not worry. Otherwise - compare with what you already have before you overwrite.
The changes remain backward compatible (back to 6.0)

Special thanks to Oliver and Aaron

- 2.56b29 - 19-Apr-2006
- Reinstate broken support for Matrox eTV - but only for beta builds.
- For TwinHan VisionDTV - most new users should be using the 2.6 version of the TwinHan software so change defaults to match.
- For TwinHan VisionDTV - move the registry path check to be after the INI file setting is checked.
- For WinTVPVR and WinTVCap - allow a command line override for people who always record from same channel source - e.g. a Sky box
- Make configurable the set of allowed characters in file name - so that extended European characters can be used by those that want to.
- Add channel name into list of simple file name substitution fields (FileName fields in dabdig.ini).
- Allow the divider in the title/filename to be specified.
- Allow diagnostic messages to be written to file without going to screen.
- For WinTVCap - allow a wait for exit because when GBRecord is being used as a WinTVCap replacement there is a problem if 2 copies are trying to record at the same time from a single board.
- For Leadtek Winfast - there is a new digital TV device available. Very similar schedule format and new registry key to use.
- For DVBViewer - version 3.2 changed the schedule file format and also added a COM interface including ability to notify On-Screen-Display.
- Make sure that all calls to create objects using SET have previously had the variable DIM'd because it might be the cause of an obscure ActiveX scripting problem when not running as Admin on XP.
- Add parameter substitution for Streaming and Streaming2 via CmdOverride facility.
- Implement the previously documented (but skipped) WebSchedulerURLRadio.
- Add a simple remote execution mechanism.
- Include native HTTP GET operation so that local browser can be avoided (initially for WebScheduler).
- For DVBViewer - add some different handling for when software already running.
- Add EpisodeName as substitutable parameter and optional 13th command line parameter.
- For ProgDVB, make the request to Exit configurable and hence optional.
- For ExternalChannelChanger, make configuration easier for simple installations by adding a base channel number definition and default source.
- For Leadtek - looks like another version of their software does not use registry at all so try to make the use optional by adding configurable path.
- For GBPVR - if specified, then use capture source

ExternalChannelChanger

- ExternalChannelChanger
Added some extra code to make it possible for configuration of a mixed device set-up with ExternalChannelChanger (typically an IR sender of some sort) to by-pass having a dabdig.map by simply specifying which channel number the changer starts from and the default recording device channel.
(256b25)

TopfieldViaJag

- TopfieldViaJag
Aborigine was kind enough to send me a note about his success with using DABDig and version 3.0 beta of Jag's EPG in LCN mode.

If anyone else wants to run it this way then it just needs 4 simple changes to the dabdig.ini file.

The potential benefit for an existing user is that new channels coming to the platform or any more channel renumbering have an even better chance of working without further update.
For new users - setting this waay should lead to getting up and running more quickly because it by-passes the issue of channel names in DigiGuide not always being the same as used over-the-air by the broadcasters.

The changes to the dabdig.ini are:
TopfieldViaJagFindChanName from 1 to 0
TopfieldViaJagChanLength from 4 to 6

TopfieldViaJagSyntaxRec from
Command.AddTimer:$CP,$DY-$DM-$DD,$DH:$DN,$LH:$LN,$MO,OT,Rec;$TI
to
Command.AddTimerEXT:LCN$CP|$DY-$DM-$DD,$DH:$DN,$LH:$LN,def,def,def,OT,Rec;$TI

TopfieldViaJagSyntaxPlay from
Command.AddTimer:$CP,$DY-$DM-$DD,$DH:$DN,$LH:$LN,$MO,OT,-P-;$TI
to
Command.AddTimerEXT:LCN$CP|$DY-$DM-$DD,$DH:$DN,$LH:$LN,def,def,def,OT,-P-;$TI

The thread about the new version of Jag's EPG is over on the UK Toppy forum.

ProgDVB

- ProgDVB
Had a report that ProgDVB (in conjunction with a DVB-T set-up) is prompting for something every time it starts up.
So - as a temporary workaround while the ProgDVB users works out how to stop this happening ... I have made the sending of "/Exit" to ProgDVB optional. This means that it can be configured so that it will only prompt when run the very first time (e.g. put it in the Windows startup group).
My guess is that there is a progdvb.ini setting that could be used to prevent this prompting.
(256b24)

256b23 available

- General
Had a request to make the Episode Name available as a parameter. Easy enough to do but needs a modern version of DigiGuide.
(256b23)

256b22 available

- General
Add a simple remote execution mechanism.
Initially requires a shared folder (with the remote system where the recording is to be done).
Simply drops a file into the share containing the parameters of the request.
A batch file running in a loop can then easily find the file and get a local DABDig to action it.

Also added an "All" function for multi-device installations - example from requestor was to record the same channel from both DAB and Digital TV - i.e. belt and braces solution.
One day ... should be extended to "Any" and then let DABDig pick the one that appears to be free (and has highest priority).

(256b22)

256b20 available

- Streaming
Added parameter substitution to Streaming and Streaming2 (via CmdOverride).

- WebScheduler
Added support for "radio" indicator in channel assignment (or channel name) so that it can trigger different URL. This allows a different capture type to be set because WebScheduler seems to have problems with automatic recording of audio only DVB-T stations.

(256b20)

Leadtek and DVBViewer - part 2

- Leadtek Winfast
The Leadtek Winfast DTV1000 looks like it is now close to working. There were about 5 fields in the record that have either changed meaning or needed to be set-up.
Now need to parse their channel list file to perform lookups - this will be a bit complicated as the file format is a bit convoluted - but at least it is all in plain text.

- DVBViewer
DVBViewr Pro 3.2.6 is now working. I went the COM route in the end. Turned out to be quite easy. However, they take the date using the local settings of the PC. For now I have made the syntax configurable but really should do it automatically and allow an override.
Handling the new text format does not seem so important for now because the free Technisat version still seems to use the old format.

Leadtek and DVBViewer

- Leadtek Winfast
Some progress on the revised file format.
Spent some time over last couple of evenings and after a few file exchanges via email I am pretty sure that I have worked out what they have done with their new structure. It is pretty well the same as before but they have done some horrible things - e.g. storing data about the offset of the channel within a Mux and the Mux number - and then storing somewhere else an identifier for the mux and the channel.
Ultimately it will require some automatic parsing of one of their configuration file - but the stupid thing is that on a rescan the file gets re-written and part-time channels that are not broadcasting are lost from the file.

- DVBViewer
I have not had any requests from users for the DVBviewer interface since I first wrote it for someone. My guess is that there are very few users of it - perhaps only one. But a new request has come through from someone else because he could not get it to work. What has happened is that DVBViewer Pro 3.2 has a different interface. The data is pretty much the same as in the old Technisat version but is now in an XML file and has a couple of extra fields. They have also added a COM interface.
So question is - which way to go. Handle the new file format or go with COM.
Initially I thought I would stay file based but since the COM mechanism allows updates to the schedule without having to stop/start DVBViewer then it is probably the best way to go.

Leadtek WinFast queries

- Leadtek WinFast
Two requests came through today.

One from another developer who wants to see how the schedule file works so that he can build his own application. I'll have a look to see how easy it is to extract the relevant parts of my code and send it over to him.

The second was from an existing user who bought himself the new WinFast DTV1000 for Christmas ... and has found that they are using a different mechanism for scheduling to their DTV card. I've asked for some samples and will see what I can do.

WinTVCap

- WinTVCap
If using GBRecord as a direct replacement for WinTVCap then there is a potential issue with recording consecutive or overlapping programmes.
With WinTVCap it seems to close the current file and start the new one without a problem.
With GBRecord it looks like if there is a slight overlap then the 2nd programme gets cut at the end of the scheduled recording of the 1st programme. Not 100% sure that this is the cause - but put some code in place to wait for GBRecord to exit before issuing the new command.
(256b08)

- WinTVPVR
Allow a command line override for people who always record from same channel source - e.g. a Sky box

- General
Make configurable the set of allowed characters in file name - so that extended European characters can be used by those that want to.
Add channel name into list of simple file name substution fields (FileName fields in dabdig.ini)
Allow the divider in the title/filename to be specified - default to a minus-sign as before.

(256b06)

- TwinHan VisionDTV
Changed the installation defaults to match a TwinHan 2.6 software release since new installations are likely to be running that. Modified the documentation to help users with old TwinHan versions to change the settings back.
This will not change existing settings for someone that is upgrading - i.e. it remains backwards compatible.

(256b01)

- General
Decided to release 2.55 version.
Took curent 255b18, removed most of the non-supported pieces that are still in development/testing and made a new 255b19.

- FusionHDTV
Just had a new query on this one - again from Australia. The database record formats appear to be the same - so sent over the pre-existing test version to see how it goes.
First reaction is that it appears to work so a few more things to investigate that were left over from before.
e.g. how is the channel number really calculated
Also stuffed the programme title into the file name field - checked for overlength and truncated first.

(255b18)

- WebScheduler
Had a couple of queries about interfacing with WebScheduler.
Both have similar work-arounds.
One was that recordings of some channels were not working.
The failing ones were where the channel name from the EPG (DigiGuide in this case) did not match the channel name in WebScheduler (e.g. BBC 3 and BBC Three).
This sort of thing could potentially happen with other software that DABDig schedules into. Often it is cirumvented by DABDig performing matching on "3" and "Three" or by using the channel number rather than the channel name.
If the automated ways to get around this do not work - then the user has to do something.
There are essentially 3 routes:
a) tackle the problem at source - and change the name in the EPG (in DigiGuide you can right-click on the channel icon and change the channel detaild)
b) modfy the name in the target - but this might be based on data in receives over the broadcast network and could change back on the next scan that it performs
c) using a mapping facility in DABDig

In this case - the mapping in DABDig was used.
However, there is one extra twist. The mapping facility in DABDig (via the optional dabdig.map file) is really for generating a channel number from a channel name.
So - although this might appear to change BBC 3 to BBC THREE ... that resulting conversion is stored as the "Channel Assignment" (think of it as channel number).
So - you then have to make a small configuration change in DABDig (via dabdig.ini) to tell DABDig to use the channel number when controlling WebScheduler rather than the channel name. The result is that DABDig then sends "BBC THREE" ... exactly as required.
But - there is now an additional problem. Namely, for channels that do not have a name map, the real channel number will be sent rather than the required original channel name. So - while I think of a simple way to resolve it via a change to DABDig - the simple work-around is to put all of the channels into the dabdig.map and for those where the name is the same ... simply put the same value on each side of the mapping.
e.g.
BBC 3=BBC THREE
five=five

The second problem reported was that a feature of WebScheduler is that if it is asked to record an audio only DVB channel (often called radio) using using capture type that it usually uses to record TV (video and audio) then it appears to record but the end result is not saved properly.
Therefore, until WebScheduler is changed, it is necessary to be able to specify a different capture type for audio-only stations.
In theory - this should be easy - especially if a dabdig.map has already been created from the steps above.
Simply hide the capture type in the output map.
e.g.
BBC Radio Four=BBC Radio 4&captype=5
(It might also be necessary to remove the captype=2 from dabdig.ini and add &captype=2 to each of the TV stations if WebScheduler can not handle 2 captypes in the request)

- GBPVR
Looks like recording requests are not (always) picked up ... so added ability to stop/start the GBPVR Recording Service. Need to find the real reason though.
(255b16)

- DigiGuide
Had a request to be able to set the time range in DigiGuide - e.g. to help avoid repeats on BBC 7 when using an Anytime marker.
A more comprehensive solution would check to see if the show was already recorded and skip it - but ... for now at least ... added time range to the DABDig.dgmarker.
Has to be enabled by modifying default marker and changing intRanged = 0 to intRanged = 1 (or some other number).

- Topfield
If the Toppy is used in conjunction with a (slugged) Linksys NSLU2 then it is possible to FTP direct to the Toppy. This can be enabled in DABDig by make 2 one-line edits to the dabdig.ini and creating 2 small text files (that contain the FTP commands). More details are in the next update to the DABDig "manual".

- AVerTVDVB
Looks like they have a totally different setup nowadays - at least when using BDA drivers. Will require rewrite within DABDig. Trying to get their software to install locally to try a few things out.

- DABBar
Had a request to be able to use substitutable parameters within OutputTarget when scheduling to DABBar (so that the show name can be used in the directory name).
This did not work because parameter substitution was not used when writing DABBar schedule.
Made a new version that does. It now means that there are some anomolies - i.e. USADateSyntax and ForceRetune. Plus SupportSecondary just results in a fixed string being appended.
You can force the old way of working by setting the new DABBarSchedLine to an empty string - i.e.
DABBarSchedLine=

(255b13)

- Topfield
I should have added this entry about a week ago - quick summary now.
A few new beta builds have been made. Some of the changes for the Topfield support have been done in a fairly general way so that, for exmaple

• - there is a new substitutable parameter for the duration in hours and minutes (i.e. a 90 minutes programme can be shown as something like 01:30)


• - some number to name mapping can be applied e.g. to match "BBC 1" with "BBC ONE". This will not work for all devices though.

- General
If more than one DABDig is running at once there can be a reported problem with not getting write access to the log file. This is handled in the code by reporting the issue to the screen and continuing without logging for that run.
I have now enabled the retry code so that it will try a few times to write to the file because there are a few more configurations where people are increasing the alert look-ahead time to being longer than 1 day. Plus a new function to request an immediate action (rather than waiting for the marker to fire) is exposed in DigiGuide 8.2 (Beta) which I have used to help people who want to record on devices that are not always connected to the PC where DABDig is installed.

---

A problem has been found in command line handling when there is more than one word enclosed in quotes - e.g. "this is a "Programme Description" with quotes in it"
It is more of a feature of how commmand line parsing works in Windows (DOS).
This results in a mess!
This next one will work - although the internal quotes will be stripped - "this is a programme description with "one" quoted word"

There are numerous possible solutions - but I went for one that allows the parameters on the command line to be encoded in the same way as a URL. I then modified the command line parser to decode the data before before "echoing" the command line to the log file. This is to make things look the same to anyone who parses the log file (bad idea) and also to keep the log file easily readable. This additional parsing will only happen if the parameter is prefixed by a special marker - which is currently set to "DABDigURI:" but I might change that before release. Therefore - this new code will not be activated unless that calling program does something special. For DigiGuide it needs a new DABDig.dgmarker - a very simple change. I am holding off making this the default way of working though because DigiGuide 8.2 (beta) will include a new function that allows the marker to modify the command line just before sending it to DABDig ... so I could then replace double-quote with single-quote.

(255b12)

- Topfield PVR
Added initial support for Topfield PVR via Jag's EPG.
(255b06 and 255b07)
Need to do some automatic channel look-up - but have not got definitive sample channel file yet.

- Fly2000TV
Added support for Fly2000TV - for both TV and radio with record and play.
(255b05)

- WinTV
Added channel name look-up for WinTVPVR (and WinTV Nova-T USB2) users.

Earlier versions of the Nova-T devices used the Technotrend front-end but the Nova-T USB2 uses an updated version of WinTV2K.
If users do not renumber their channels then they might be confused when the wrong channel gets recorded. Unusually the WinTV2K software, when driving the Nova-T USB2 device, does not use the LCN to sort the channels or to use as an index for recording hence the typical channel numbers do not match.
Made this a configurable option because users who have renumbered within WinTV have no problem.

Thanks to AMacdonald for highlighting this facility.
(255b04)

- DABBar
Some users of DABBar have reported that recording from a different mux to the last used does not always work.
So - added option to request a 1 minute recording from the same channel just before the real recording. This could cause problems for back-to-back recordings from different mux but that is relatively unlikely.
(255b03)

- MyHD
Started some work on MyHD from Macro Image Technology. It can be driven already by using DABDig's support for TVPI-mode. However, this will not work if DABDig is being run as a background task. Plus - TVPI-mode sometimes requires keyboard strokes to be sent which can get blocked by anti-virus tools (AVG in particular).
The underlying mechanism appears to be very similar to FusionHDTV - i.e. holding the recording schedule in a combination of registry and a database. Have worked out most of the fields and have someone willing to test.

- DigiGuide
Initial beta of DigiGuide 8.2 was made available today.
The new XML parser that is embedded within it does not like come of the constructs in many existing markers - including DABDig.
So - worked out the differences and managed to re-write parts so that it works with DigiGudie 8.2 while remaining backward compatible.
Made a new 2.54 releasse to get this out quickly.
Since this does change the marker - then anyone who has made their own customisations of the marker will have to make the same changes again.
(254b09)

- TwinHan VisionDTV
A real bug found - if there is no channel number specified then it could result in a crash. Looks like a problem introduced in 2.53.
No-one had hit it in production because channel numbers were always present ... however, it tripped up one user while trying to do something else.
Decided to fix it and make a full release of the current 2.54 with this fixed.
(254b08 released)

- Archos 400 Series PVR
Saw a request to drive this from DigiGuide - based on appending simple text to a file.
Looked easy enough so done it.
(254b05)

- WebScheduler
Added ability to use channel name rather than number.
(254b03)

- WebScheduler
Looks like default port number has changed from 8080 to 8429.
Also, looks like the channel "number" can be a channel name - so need to ensure that spaces (etc) are encoded within the URL. It might also be better to include ability to use channel name rather than number via config. First 2 items done.
(254b02)

- TwinHan VisionDTV
Looks like 2.6 has been released again - now as 2.602
They appear to have changed the recording schedule format again - and now allows the APID to be added. Made a change to generate it - this marks the first limited release of version of 2.54
(254b01)

- ATiMMC
For ATi MMC handling - added code to look up TV and FM radio channel names when no channel number (or FM frequency) is given.

- Nebula DigiTV
Modified code that checks for timer key being in registry so that it does not wait for user input. The old code waited because it was treated as a fatal error and needed to be sure that the user saw the message. However, in 2.51 code was added to crate the key if not present - so it is no longer fatal.
People re-installing their Nebula DigiTV software because of major updates from Nebula would hit the issue if they had not done a quick test timer recording after the upgrade.

(254b01)

- General
Made an external release - 2.53 build 17.
This is basically 253b16 with some experimental devices removed.

- WinTVCap
Extended the previous change so that the OutputTarget field can take the substitution parameters (with simple check for recursion). At the same time - added ability to request that the output directory should be created if not already present.
Done this because WinTVCap (unlike WinTV2k) does not auto-create the output directory chosen for a recording.
(253b14)

- WinTVPVR
Had a request to be able to pass the Category of the recording so that it could be used as a directory name for the recording.
A quick test by the requestor showed that WinTV2K created the requested directory if it was not present ... so looked safe enough to include the field in DABDig and not have to worry about checking to see if the directory exists etc.
Included code and updated DABDig.dgmarker to pass the parameter (as parameter number 12). While there - added Description to the Play command for consistency.
Made WinTVPVR command line processing perform substitutions and added new substitutable parameter - $CT (Category).
Added command line substitution to WinTVCap at the same time since some WinTVPVR users use that utility instead as it is less CPU intensive.
(253b12)

- ExternalChannelChanger
(RedRat3 in particular)
One new user wants the commands for the RedRat3 to be sent individually so made it possible - including an initial and trailing command.
(253b11)

- GBPVR
Been contacted by someone who would like to see this working - so another chance to work on it (things stalled first time round back in September 2004 because that requestor moved to WebScheduler instead of GB-PVR).
Looks like entries that I add into the schedule database while the GB-PVR service is running are not being picked up - but they do work if you stop/start the service. Implies that the format is right but I need to do something else to wake it up if it is already running.

- TwinHan VisionDTV
First version for the TwinHan 2.6 software now ready to test.
(253b01)

- TwinHan VisionDTV
Had a detailed report from a user that the new TwinHan software completely changes the way that the schedule data is maintained. So - for now - TwinHan VisionDTV version 2.6 is not supported. Will be working on it over next day or so.

- General
Reported by one of the users -the main web page has become too big for ChangeDetect - so broke into two parts and re-uploaded.

- General
Added "day of week" as an available parameter substitution keyword.
Made a public release of 2.52 now that the Christmas recording frenzy is largely over.
(252b23)

- Replay Radio
Odd - 2 mentions in a few days. When I first looked I could not see an easy way in.
No obvious command line parameters and binary file that was a pain to create (but possible).
Good news though - the second requestor had spotted that they have documented a way in by passing it a formatted file. Similar idea to TVPI.
Implemented it. But - it shows up something interesting.
To get it to close a dialogue box I had to send a keystroke to it - but ZoneAlarm firewall seems to be blocking keyboard stuffing. I can understand why, but it does not seem to be configurable. This will cause a few problems for other devices so will have to do some digging around.
(252b22)

- TotalRecorder
Had a comment which lead to including a new substitution field - OutputTarget ($OT).
Then modified TotalRecorder to allow substitution to be called. Utimately all devices will have this support when invoked from command line but doing it as other changes happen in similar area. Did it in a way that will not affect existing installations - but would prefer to remove the "old" method.
The person who wanted it has written a useful page showing how he configured things.
(252b20)

- TwinHan VisionDTV
One user is finding that the recording is sometimes from the wrong broadcast type (e.g. radio rather than TV). I cannot see anything wrong with what I am doing - but looking.

- Radiator
Someone wanted to drive Radiator (radio handling software). He was able to get it working by simply using one of the existing device types and simply modifying the paths and command line. Works - but could be better.
So - put in some native support.
(252b18)

- Intervideo WinDVR3
Had a request to support WinDVR3 today. In theory it shouldn't be needed because it supports TVPI and acceptes plaintext version of the file. However, the requestor wants to record from the Composite input and it looks like WinDVR3 does not allow the source to be specified in the TVPI file - it assumes that it is the tuner.
Could write to their somewhat complicated Scheduler.xml file - requires inserting a record-set in the right place since it is organised by internal Windows user id.
Looks like the proper way to do it would be to call their Server Proxy DLL - which is what their TitanTV (TVPI) integration module does.

- ChrisTV
Had first input from someone trying to use this new support.
Two issues reported.

• His PC was set for Chinese language and the software failed to run completely.
  
• The Date/Time syntax on the PC affects the way that ChrisTV processes the schedule data
  

My suspicion is that the MS VBScript processor can not handle .vbe files when machine is set to Chinese. Have suggested some things to try to test that.
The date/time syntax is a bit annoying - but made a quick change to allow specification of dd/mm/yy or mm/dd/yy in the output file for ChrisTV. Proper way to do it is to examine and use what is configured for the PC - but will have to wait a bit before I get round to doing that. Looks like it also wants AM/PM for start time if PC configured that way. Backburner stuff for now as user can easily reconfigure the PC for 24-hour clock.

(252b16)
- DVBViewer
First feedback from tester of DVBViewer interface. Largely works - but seems a bit hit and miss. Not sure if it is me, the way it was tested or the DVBViewer software.
Made some suggestions to narrow it down.
Saw the GUI of the commercial version. Basically the same interface for scheduling (including file format) but a few extra options. One is that it can be configured re-encode radio stations (audio) to MP3 so made that configurable by station type.
For now the station type is specified to DABDig on its command line - but ultimately should work out the format of the DVBViewer channels database and determine station type automatically.
Added code to handle the timer group missing from the DVBViewer config file - it looks like it can be removed by DVBViewer on exit if no scheduled events remain.
(252b15)

- DVBViewer
Started to add support for DVBViewer. Using the free one that ships with the Technisat software. Only schedules recording for now. Might not work with the commercial version of their software.
(252b13)

- ATi MMC
Did some more work on supporting alternate recording source. Looks like some versions of the ATi software require that the tuner channel is set to 0 when recoprding from S-Video (and perhaps Composite). Odd because the registry dump that I had of one working had a non-zero number. Anyway - sent it out to test.

- ATi MMC
Had a request to support the ATi card with built-in FM radio.
Made a quick version to prove the principle. Waiting for feedback.
Co-incidently also had a request to be able to schedule recording from S-Video input.
Will be easy once I get to see how it is specified (have done similar thing for another device).
(252b06)

- TwinHan VisionDTV
Follow-up from posting of a few days ago ... have now made a new version that tries to calculate the record size and name offset. Setting the INI fields to 0 (or -ve) will invoke the new code.
(252b02)

- Leadtek
Had a request, via the new support forum, to allow control of the Standby field when scheduling. I did not put it in before because it only really makes sense to use if all future (at least until PC next turned on) scheduled recordings/viewings are already entered into the Leadtek scheduler. In this case this is how the user is doing it.
So added code and defaulted to old way of working.
(252b01)

- TwinHan VisionDTV
It looks like the upgrade by TwinHan to their 2.43 has changed the structure of the channel list file.
If you are having a problem since upgrading then try editing dabdig.ini as follows:
VISIONDTVFILERECORDSIZE=104
VISIONDTVFILENAMEPOSITION=69

If your problem is with the Twin Han software rather than DABDig then perhaps try a total rescan to get the new format file written by their software (and then change the dabdig.ini settings).
Thanks to Bob and Laurie for the info.
I will probably make a new DABDig that tries to adapt itself to the changing structure.

- Nebula DigiTV
I now have a Nebula DigiTV installation (i.e. with hardware) ... and I discovered that the 3.12 beta3 from Nebula does not like the combination of channel specifier and full-screen mode selection on command line at the same time.
Unfortunately I made this the default way of working.
So - when requesting DABDig is initiate live viewing, either renfigure DABDig to go back to the old stop/start method or configure for non-full-screen mode.
i.e. either set
PlayWinStyle=1
or
ViewViaCommandLine=0

- General
Made an external release - 251b20.
Removed the parts that were still in development.
If you were testing/using an earlier 2.51 release and want to keep using it then send me a note and you can have a 2.52 beta with the functionality enabled again.

- ChrisTV
Had a request to add support for ChrisTV.
I looked at this back in December 2003. Back then there was a plan for a future version to include a command line interface, but it looks like it did not happen.
However, there is now a ChrisTV scheduling agent that works of a text file - so made a new version that can write to that file. In theory it should also be possible to support live viewing that way - but it is a bit clumsy. Needs more investigation to improve it. Anyway - first version of DABDig made and passed to requestor to test.
(251b18)

- GB-PVR
Another PVR solution that has UK users suffering from the outage of the XMLTV Radio Times grabber is GB-PVR (from New Zealand).
A user posted a query which I replied to - and as a result I had a look at the database tables that it uses for scheduling recording. Didn't look very hard to add new entries into it ... so added in the basics.
Have hard-coded a few things for now - but fundamentally it looks right.
As always - now need some users to give some feedback to see if what I have done really works in their configuration.
Have also posted a note in the GB-PVR forums - just in case the developer is not happy with such an approach (for example - there could be cleaner and more supportable ways to do it.)
(251b16)

- WebScheduler
There is a problem (short-term) with the XMLTV grabber for the UK (from the Radio Times site). This lead to a user of that to ask if DigiGuide could drive WebScheduler.
WebScheduler is a utility that can drive some DVB cards - some of which are already supported by DABDig but everyone can choose whatever they want of course!
A had a quick look at it and could see that it was pretty likely that it could be driven by DigiGuide directly by using a conventional Marker Alert. Worked out the probable syntax but it turns out that WebScheduler counts months from 0 - so made a quick update to DABDig so that it could fire a modified URL at it.
Yet another hack - but will basically work. Just waiting for the requester to make direct contact so that I can send a copy to try.
(251b15)

- WinTVCap
Had a request for a few things:

• Support multi-board installations
  
• Be able to override recording quality settings per programme
  
• Do not insist on stopping WinTVCap if already running

The last one is now the default operation for DABDig because modern versions of WinTVCap can handle being run twice (for same board) - by closing first recording and starting the new one.
All done (251b12 and 251b13)

- Nebula DigiTV
New facility coming in DigiTV 3.12 which should make switching channels easier.
Available in 2 ways - added the easier one for now (command line)

- General
Had a request to allow an override of the duration of a show while adding a marker.
Could have done it all in the DGMarker file - but decided to make the duration field a simple piece of run-time maths which makes it more flexible.

(2.51b11)

- RitzDVB
Just come across some more DVB software based on DVBCore.
It has a SendMessage interface and more recently, a command line tool to use the SendMessage interface. Add to the background list of things to look at.

- VirtualVCR
Had a request to be able to suppress the "stop" of VirtualVCR if it is already running. This request comes because of a variant of VirtualVCR called "VirtualVCR Max". This stays running as a task in the task bar plus adds a basic scheduling interface (that simply puts events into Windows Scheduler) and interesting has a GUI to allow configuration of scheduled runs of XMLTV.
Done as 251b09