demux's anyone?

[wannabepvr]

All this has got me looking into filters again.

When I checked my logs to see what was actually in use I saw this


2007-12-02 10:32:15.921 VERBOSE video resolution is 720 x 576
2007-12-02 10:32:15.921 VERBOSE source is 16:9
2007-12-02 10:32:15.921 VERBOSE getSetting(HorizontalZoom)
2007-12-02 10:32:15.921 VERBOSE getSetting(VerticalZoom)
2007-12-02 10:32:15.984 VERBOSE Allocator shutdown...
2007-12-02 10:32:15.984 VERBOSE DeleteSurfaces
2007-12-02 10:32:16.046 VERBOSE DeleteSurfaces
2007-12-02 10:32:16.046 VERBOSE Creating video texture: 1934x1088

The last line 1934x1088 has me scratching my head. Is this REALLY trying to create a full HD image?

[sub]

What resolution are you running your desktop?

[wannabepvr]

desktop is 800x600!!

No point having any higher with a CRT output.

[sub]

Are you playing a high def channel?

[wannabepvr]

It isn't supposed to be a HD channel, although it has the ac3 audio usually associated with Australian HD.

The source is 720x576. not sure if that is interlaced or progressive. Some of the networks here call 576p high definition - but this is a bit of a stretch.

The log file is now attached.

[sub]

I dont know. Thats what size directshow reported the frame was, so thats what size texture GB-PVR used.

[pBS]

yea, what he said...
that sounds like a regular 1920x1080p format with overscan padding..

the other day i had a show switch resolution in the middle!
late show with Conan Obrien started out 720p with bars on all sides, and halfway thru the monolog, it changed to full 1080p 16/9..!? and the HD logo appeared on the side..lol
I checked and it was a single file..1920x1080
just odd i thought..

[wannabepvr]

Thanks anyway - I didn't mean to hijack the thread.

Getting back on topic - Sub, What are you thought on the MS splitter being very CPU hungry?

[sub]

Sub, What are you thought on the MS splitter being very CPU hungry?

I dont know - I've never had any problems with it. We dont have HD here though, so I'm probably not the best person to ask.

[pBS]

seems like it's bandwidth hungry, not cpu hungry...seems to make network accesses much easier...tho also made a difference on local content..

just seems like the splitting ability is limited, like it can't split too high of a bitrate...so only HD is affected...like anything over dvd spec is too much to handle comfortably..

also i notice all of the splitters are 'mpg1' so i think the container is identical for both mpg1 and 2..[or at least the way they're accessed] so that may be the source of the problem... just don't think std. MS one was built for such high bitrates....would think newer ones would be fixed but u know MS, they only care about their dvr-ms splits.....mpg is 'legacy' to them..lol