HDHomeRun Mux Question

[UncleJohnsBand]

On the PCH? Thats not something I'd expect.

Yes on the PCH....it was almost as though the recorded file may have been hosed....but I am not sure yet.

I have 95-99% signal strength on both HDHomerun tuners....maybe it is time for a higher performance HD....

Edit....actually the 95-99% is signal quality.....strength is 78% on one tuner and 83% on the other.

[sub]

I'd try a couple more .ts files to see if its consistent.

Are you wired or wireless?

Are those files also choppy if you try playing on the PC?

[UncleJohnsBand]

I'd try a couple more .ts files to see if its consistent.

Are you wired or wireless?

Are those files also choppy if you try playing on the PC?

Wired....GB...although the HDHimeRun is only 100mb

Yes they were choppy on the PC as well.

My one recording (only 10 minutes) just completed using the 5.0.0.1307 mux and it is the best that I have seen....no hickups and the other hd recording is still recording.

Do I want to use the mux called TS Mux or the mux called Full TS?

[sub]

Use the TS Mux option, not Full TS.

Did the HDHomeRun come with any utilities to record a transport stream? I wonder how well one of those would play.

How fast is the network link between the PC and the HDHomeRun? Wired or wireless?

[UncleJohnsBand]

Use the TS Mux option, not Full TS.

Did the HDHomeRun come with any utilities to record a transport stream? I wonder how well one of those would play.

Good question....I just dug in and fired it up on GBPVR and PCH....why would anyone need anything else.... I'll have to see what it has nativley.

How fast is the network link between the PC and the HDHomeRun? Wired or wireless?

Wired....PC to switch is GB and the HDHomeRun connects to the same switch...but it is only 100mbs....the switch itself is GB.

[sub]

Are you using it for QAM or OTA ATSC?

[UncleJohnsBand]

are you using it for qam or ota atsc?

qam

[sub]

I'm wondering if it related to a change that Nick from HDHomeRun made a while back, where the entire transport stream is now sent to the client for processing. This is about 30mbps on QAM. A sustained rate of 30mbps is pretty hard to achieve with packet overheads, other networking on the same interface. (ie, if you were recording+playing at the same time, sending out to the PCH etc).

Earlier drivers used to do quite a bit of channel mapping at the HDHomeRun end, and only the data related to channel, maybe 5mbps or even less.

They do have a driver interface where an app can tell the HDHomeRun the list of PIDs its interested in to do device side filtering, but GB-PVR doesnt support that yet. I'm waiting for the same DVB-T device they indicated they'd supply.

[UncleJohnsBand]

I'm wondering if it related to a change that Nick from HDHomeRun made a while back, where the entire transport stream is now sent to the client for processing. This is about 30mbps on QAM. A sustained rate of 30mbps is pretty hard to achieve with packet overheads, other networking on the same interface. (ie, if you were recording+playing at the same time, sending out to the PCH etc).

Earlier drivers used to do quite a bit of channel mapping at the HDHomeRun end, and only the data related to channel, maybe 5mbps or even less.

They do have a driver interface where an app can tell the HDHomeRun the list of PIDs its interested in to do device side filtering, but GB-PVR doesnt support that yet. I'm waiting for the same DVB-T device they indicated they'd supply.

Actually whurlston created a wrapper that you can set as an .exe channel tuner in GBPVR and it limits the stream to just that channel....very effective....streaming without the add-on uses about 25% of my available bandwidth when recording two hd shows while with the add-on the network usage is only about 6%.

I am thinking the whurlston may be using the interface you mentioned to do this.

[sub]

Ok.

I'd still try playing a .ts recording created with some other HDHomeRun software to check if .ts playback is a problem or not.