Update: HD PVR for Windows Media Center

Minor update, Hauppauge added another registry key so the version being released will be 1.0.28190. The only change is that the FlushOnChannelChange registry was split into two settings, FlushOnChannelChange and PauseOnChannelChange.


We were lucky enough to get early access to a forthcoming updated beta driver, 1.0.28188, from Hauppauge for their HD PVR support for Windows Media Center. Normally we would update our original Preview: HD PVR for Windows Media Center and leave a comment or two about what was new—that would not do it justice.

So what is new?  Honestly not much.  Before you question my sanity let me explain. The currently available beta driver, 1.0.28171, is fairly stable and works as intended. For those that are already using the beta, there simply isn’t much to add.

What they did add is huge for those hesitant to try the beta, in particular they have 1- added support for external blaster applications; 2- added the ability to toggle whether channel changing stops the encoder and flushes the internal queues or not to.

I am a 64-bit fanboy, but for those using 32-bit versions of Windows 7 this means you can continue using firewire channel changing via Tim M. Moore’s FireSTB or any command line based channel changing method you currently use with DVBLink.

For those sticking with the internal HD PVR blaster, you can optionally choose to continuing using it in addition to an external blaster application.  This can help troubleshoot any channel changing issues that may occur by logging channel change requests.

For existing beta users there are a couple of fixes and new options.  The most prominent being the ability to toggle whether channel changing stops the encoder and flushes the internal queues or not to.  What does this mean?  By default the drivers will stop encoding when changing channels, this can cause a delay in Windows Media Center and consequently the dreaded low signal error.  You now have the option to turn that off. 

On a negative note, the external blaster application is currently only available via manually editing the various registry settings.  If that isn’t improved by the public release I will provide an easy tool to configure the various settings.

There are a few other settings available so I urge you to read the upcoming release notes in detail.  If you have any questions please let me know.

A big kudos to the Hauppauge team working on the HD PVR for Windows Media Center support.  It is clear that they are listening to feedback and making progress towards an official Windows Media Center driver.


I’ve gotten the OK from Hauppauge to share the change log.  Please note that it is subject to change.

1.0.28190 Change Log

– Include latest WHQL’d HDPVR analog driver. 

– Include latest IR support for compatibility with other Hauppauge products. 

– Added “Blaster” registry key 




And several values to control blaster operation (defaults shown): 


• "ActiveBlaster"=dword:00000001  

0 – no blaster 

1 – use HDPVR blaster 

2 – launch external blaster application 


Used to select the active blaster.  This is a bitwise value so multiple bits can be set.  

When set to “external” the application specified by "ExtAppName" will be launched with 

the command line parameters specified by "ExtAppArgs". 


• "FlushOnChannelChange"=dword:00000001 

0 – internal queues are not flushed after blasting 

1 – flush internal queues after blasting


• "PauseOnChannelChange"=dword:00000001 

0 – encoder is not paused before blasting 

1 – pause encoder before blasting 


• "IntOpenMode"=dword:00000000 

 0 – internal blaster port is opened once and handle saved for subsequent use. 

 1 – internal blaster port is opened/closed on each use


Opening the blaster once provides faster operation but the saved handle will be 

invalidated if any other application accesses the blaster hardware. Once the handle is 

invalid the MCE software will not be able to blast. For example, if you test the blaster 

operation using BlastCfg.exe you must reboot the PC (or restart the service) or the 

blaster will fail when MCE next tries to change the channel. 


• "ExtAppName"="D:\MyTests\blast.exe" 

Used to specify the full path and name of an external blaster application.  External blaster 

mode must be enabled in "ActiveBlaster" for the application to be executed.  Do not 

include opening and closing quotes in the value you specify. 


• "ExtAppArgs"="-c%c" 

Use to specify the command line parameters passed to the application specified in 

"ExtAppName".  The MCE software will replace the first occurrence of %c in the 

command line with the channel number to be blasted.