I have this problem too!

It only happens when recording 2 shows after each other on the same channel and let the show record longer via advanced record properties.

If only recording one show with extra time it's all good.

So this seems like a bug to me.

Hope MS will come with a fix soon.

babgvant - I'm having a problem with FixDVRMSDuration.  When I run on my XP Pro SP2 laptop, I get the following error:

Unable to cast COM object of type 'DirectShowLib.StreamBufferConfig' to interface type 'DirectShowLib.SBE.IStreamBufferConfigure3'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{7E2D2A1E-7192-4BD7-80C1-061FD1D10402}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Any thoughts?  The variance evaluation works fine ("Duration is not within allowed variance") - it's during the conversion that it burps.

It's not a big deal - it works fine on my main PC where the actual processing occurs.  I was just trying to test something out on the laptop and got a surprise.

Thanks!

I'm guessing that IStreamBufferConfigure3 is a Vista only interface.  I don't think it actually needs the members provided so I can use 2 or standard.

---

DVRMSToolbox, Recording Broker, LcdWriter, and more software
babgvant.com

Please don't worry about it - I just wanted to make sure it was an XP problem and not something else.  This is not a tool that anyone running MCE 2005 would need, so the fact that it doesn't run on XP is minor at worst.  Thanks, though.

babgVant:

onlydarksets:

Ugh - not what I wanted to hear.  Is there a "next best" choice for SD recording?  I have two 250s - would the PVR-500 suffer the same bug?  Has anyone had the problem with the PVR-500?

Thanks!

I have a Win-TV-PVR-150 MCE and don't have that issue.  I think the 500 is based on the same chip as the 150.

How many do you have?  Just one?

I'm starting to think this is an issue where the driver gets mucked when it has to handle multiple of the same card.

Is anyone with just one SD card having the problem?

onlydarksets:

Please don't worry about it - I just wanted to make sure it was an XP problem and not something else.  This is not a tool that anyone running MCE 2005 would need, so the fact that it doesn't run on XP is minor at worst.  Thanks, though.

Too late.

---

DVRMSToolbox, Recording Broker, LcdWriter, and more software
babgvant.com

onlydarksets:

How many do you have?  Just one?

I'm starting to think this is an issue where the driver gets mucked when it has to handle multiple of the same card.

Is anyone with just one SD card having the problem?

Just one.  I have it and an Avermedia m150 in the same box.

---

DVRMSToolbox, Recording Broker, LcdWriter, and more software
babgvant.com

babgVant:

onlydarksets:

How many do you have?  Just one?

I'm starting to think this is an issue where the driver gets mucked when it has to handle multiple of the same card.

Is anyone with just one SD card having the problem?

Just one.  I have it and an Avermedia m150 in the same box.

Interesting.  Does anyone who is having this problem have two different NTSC tuners in their system?  I'm thinking about taking out one of my PVR-250s and picking up a cheap non-Hauppauge tuner to see if that does the trick.

onlydarksets:

How many do you have?  Just one?

I'm starting to think this is an issue where the driver gets mucked when it has to handle multiple of the same card.

Is anyone with just one SD card having the problem?

We just have one PVR-250 and we definitely have the issue.

I've solved it by using DVRMSToolbox to run FixDVRMSDuration on all shows less than 20 minutes long - right before the commercial checking is done.

Since setting that up about a month ago, I havent seen a screwed up show since.  Prior to that we'd record at least a couple unwatchable shows per week.

I don't think running a repair utility using a custom batch script, a custom process condition in DVRMSToolbox and a customized process is a solution for non-enthusiasts - but at least us enthusiasts can use Media Center.

---

STB w/R5000HD USB I/O, Gigabyte GA-P35-DS4, Quad Q6600, 4.0 GB RAM, ATI HD 3870 512MB, Ultra XVS 600W PSU, 3x SATA 500GB, 2x SATA 300GB, LG GGC-H20L, PVR-250, Toshiba 51H83 (51" HDTV), Yamaha RX-V2400 Amp, 5x Energy Speakers, SVS Sub, Harmony 880 Remote

HT Slider:

I've solved it by using DVRMSToolbox to run FixDVRMSDuration on all shows less than 20 minutes long - right before the commercial checking is done.

Since setting that up about a month ago, I havent seen a screwed up show since.  Prior to that we'd record at least a couple unwatchable shows per week.

How did you do that?

Alex2:

HT Slider:

I've solved it by using DVRMSToolbox to run FixDVRMSDuration on all shows less than 20 minutes long - right before the commercial checking is done.

Since setting that up about a month ago, I havent seen a screwed up show since.  Prior to that we'd record at least a couple unwatchable shows per week.

How did you do that?

I found this for using FixDvrmsDuration with DVRMSToolbox.

I did exactly as beneath but it doesn't do anything at all.

The log says:

InputFile=H:\recorded tv\Totally Spies!_Veronica-Jetix_26_01_2008_10_50_01.dvr-ms
Processing actions, this may take some time!!
Profile = Fixing the Duration Bug

What do I have to change to make it work?

Steps

1. Create a new Profile
2. Add ChangeContextValue Action:
   1. SourceContext = InputFile
   2. TargetContext = OutputFile
   3. FindRegex = ^((.*\\)(.*)\.(.*))\z
   4. ReplaceRegex = E:\$3 (FIXED).$4
      (NOTE: use a path to a temporary location that is outside the Watched Folder but on the same drive)
3. Add RunExternal Action:
   1. ProcessName = C:\Program Files\DVRMSToolbox\FixDVRMSDuration.exe
   2. ArgumentsContext = “%InputFile%” “%OutputFile%”
      (NOTE: you must include the quotes)
4. Add AdjustMetaData Action:
   1. MetaMarker = “DurationFixed: “
      (NOTE: no quotes, but with space at end)
5. Add FileOperation Action:
   1. ContextFile = InputFile
   2. DestinationPath = E:\BAD_DURATION_FILES\
      (NOTE: use a path to a temporary location that is outside the Watched Folder but on the same drive.  You can also just delete the input files if you want.)
   3. WhatOperation = Move
      (NOTE: you could also just delete the input files by setting this to “Delete”)
6. Add FileOperation Action:
   1. ContextFile = OutputFile
   2. DestinationPath = E:\Recorded TV\
      (NOTE: this should be your Recorded TV directory.  Once the file is moved, it will be processed as a new file)

 

Found it here, http://onlydarksets.wordpress.com/

Yeah, that's in process.  Turns out the AdjustMetaData Action is "under construction" (see here), so that won't work.

Try this process instead:
http://thegreenbutton.com/forums/permalink/210597/216113/ShowThread.aspx#216113

When will MS come with a proper solution to this problem?

It's about time now!

I'd like to say that I have this issue too and it is very annoying.  I have a pvr-250 for recording analog cable (not through a set top box) and a HDHomerun for high defintion cable.  I have had this problem with recordings from both sources.

Someone else mentioned that they thought the problem was getting worse and I seem to notice the same problem.  At least half my recordings now show the shortened run time.  I now actually cheer when a show is recorded properly.

This is rediculous that a solution has not been released yet.  Recording TV was what Media Center was designed around.  To have that feature crippled and to not elevate the fix to a stand alone release is asinine.

Can someone explain why Microsoft allows only 4 minutes extra recording time?

In Holland shows almost never start on time and is 4 minutes way to short for extra recording. This timeline problem would be solved if Microsoft would allow choosing more then 4 minutes extra time.

The reg hack for extra recording time doesn't work.

 

I did read somewhere when Cool n Quiet is disabled the problem would be solved but it didn't work for me!