Hauppauge HVR1600

[zaphod7501]

O.k. so I figured out that it's not the players per se. I read that article and there was something that I wasn't using by ATI. The 3:2 Pulldown by ATI instead of the arbitrary program. Granted the playback is not perfect it still does play much smoother. So two more channels are much more viewable. I also had to roll back to the 3.2a drivers.

-Anthony

If you noticed, there is a part 2 planned on the article relating to HD playback, which seems to be long overdue. That's the one I want to read. I'm wondering if it's delayed because the author can't get it to work as advertised. Rolling back ATI drivers seems to be a common need.

The Mainconcept decoder is called "HCW MPEG-2 Video Decoder" if you want to use it in Media Player Classic.

[Cahill84]

Is it possible to use a different third party mux with Gb-pvr. Essentially what I'm asking is that I want mpeg files from my ATSC so that I can compress them to save space, but still have good quality. I can record moderatly well with DVR-MS and a little better with TS through gb-pvr. The conversion process of these files always gets hung around 28 Mb of the temp mpeg, but never make it to converting to a avi file. Unfortunately though, wintv2000 still records the best with their mpeg mux. Everything else SUCKS about the program, but the background records always have good quality and no stuttering. I'm assuming I could then convert them. I've tried the cyberlink, ati, ss muxes as well, but no success.

[sub]

Is it possible to use a different third party mux with Gb-pvr.

In theory, yes, there are other mux filters out there that we could use in GB-PVR. Unfortunately there isnt really a standard for how mux filters work, so those that exist tend to do things in different ways. To add support for a new one, I'd need to install the mux on my machine and write code to explicitly enable support for it in GB-PVR, and I am willing to do this if people can identify and supply me the mux.

That said, last time I checked the Hauppauge Mux filter it was hardcoded to only work with their software, so wasnt usable from third party apps like GB-PVR.

[Cahill84]

I'll do some research on that and find out. :-) Thanks sub.

[Cahill84]

Obviously it will take like 2 years... I mean weeks for Hauppauge to reply. I've will start internet research sometime this week, but I ran a random search for *.ax and I ran across these files in C:\windows\system32\hauppauge\SMD07\sys ... It is likely just a stab in the dark, but I figured that you might know right off hand if these were the mpeg muxes for the ATSC side or not. Thanks for taking a look.

-Anthony

PS-Assuming for some random chance of luck these are the muxes. Then I am using 3.2a of wintv2000 easily downloaded off of Hauppauges site for the HVR-1600.

Scratch that the file won't attach... Thoughts sub? Here's a pic of what's in it. Is it too big, does it have something it shouldn't have in it?

[sub]

I'm pretty sure the Hauppauge mux will still not work with any third party apps (it certainly didnt in the past), but if you email hcw_mcmux.ax to me at support@devnz.com, then I'll double check.

[Cahill84]

You should have them now :-)

[sub]

I've looked into the filter you sent, and the news is not good.

This mux filter is developed by MainConcept, which Hauppauge have licensed. Unfortunately this mux defaults to producing transport stream output (.ts files), and cannot be changed to program stream (.mpg files) without calling private interfaces, which are not publically documented. Without a description of these interfaces (and .h header file), there is no way for me to force this mux to record .mpg files.

[Cahill84]

Thanks for taking a look at it. I am waiting on some responses from other areas in the forum to see about other ways to conver the dvr-ms or ts files as well. What I don't quite understand is why Hauppauge would have it receive it as a ts file, but then save it as an mpeg. Oh well I guess, it's just over my head.

[sub]

What I don't quite understand is why Hauppauge would have it receive it as a ts file, but then save it as an mpeg.

All DVB and ATSC arrives as transport stream data, so its sensible that the MainConcept mux just defaults to leaving the data in it's original transport stream form. Hauppauge probably doesnt use it this way, I'm sure they set lots of parameters to setup the mux (stream type = program stream, mux rate, clock pin etc). Unfortunately I dont have access to such interfaces, and have to rely on the defaults being set the right way - and in this case they arent...