HDHomeRun (HDHR) Prime + SageDCT

[nyplayer]

Thers is definitely something wrong in SAGEDCT. I tried it on my Core i3 and it worked ok for a while then it started getting high CPU and eating up tons of memory. Over 1 gig is this normal? The 2nd screenshot shows over 2 gig.

[babgvant]

Originally Posted by Sparhawk6

Sorry, what you do mean "repro"?

reproduce the issue.

the picture shows the sage demux failing to find the a/v streams in the file, where lab is able to

[Sparhawk6]

Originally Posted by babgvant

reproduce the issue.

the picture shows the sage demux failing to find the a/v streams in the file, where lab is able to

Oh, ok. Thanks.

[Sparhawk6]

Originally Posted by Sparhawk6

Oh, ok. Thanks.

Is there any way that this is the Prime's fault? Or SageDCT's fault? In other words, do either of those affect the format of the output file? Or do they just record the stream directly as it comes from Comcast?

[babgvant]

Originally Posted by Sparhawk6

Is there any way that this is the Prime's fault? Or SageDCT's fault? In other words, do either of those affect the format of the output file? Or do they just record the stream directly as it comes from Comcast?

The files are dumped as-is. The problem is with the SageTV demux filter's stream identification logic.

[phelme]

Originally Posted by nyplayer

Thers is definitely something wrong in SAGEDCT. I tried it on my Core i3 and it worked ok for a while then it started getting high CPU and eating up tons of memory. Over 1 gig is this normal?

Well, could be normal... . What NIC do you have? Are you writing your recordings to UNC paths?

[nyplayer]

Originally Posted by phelme

Well, could be normal... . What NIC do you have? Are you writing your recordings to UNC paths?

Yes I am using UNC paths I tried both Intel and realtek both PCI and PCI express. I am streaming to 4 separate Drives all housed in the server. I have no problem using WMC recording on all tuners 1080i and watching. All Windows ultimate 7 PC's 1 64 bit 1 32 bit. Same problem on both.

I really appreciate what everyone has done ... but I think Sage has just about reached the end of the road for me ... just do not want to invest anymore money for Nics etc... to get a product to work that is on life support.... when with the same equipment WMC works just fine. Rather look at other options... and look forward.

[babgvant]

Originally Posted by nyplayer

Thers is definitely something wrong in SAGEDCT. I tried it on my Core i3 and it worked ok for a while then it started getting high CPU and eating up tons of memory. Over 1 gig is this normal? The 2nd screenshot shows over 2 gig.

Usually what that means is that SageDCT can't write to the target fast enough. If you're using an UNC path the data hits the NIC 2x so that could be the bottleneck.

[phelme]

Originally Posted by nyplayer

Yes I am using UNC paths I tried both Intel and realtek both PCI and PCI express. I am streaming to 4 separate Drives all housed in the server. I have no problem using WMC recording on all tuners 1080i and watching. All Windows ultimate 7 PC's 1 64 bit 1 32 bit. Same problem on both.

I really appreciate what everyone has done ... but I think Sage has just about reached the end of the road for me ... just do not want to invest anymore money for Nics etc... to get a product to work that is on life support.... when with the same equipment WMC works just fine. Rather look at other options... and look forward.

i went from RealTek adapters to an Intel CT Gigabit PCI-e NIC and my CPU load plummeted from 35-40% to 2%, so hang in there. I do have halt/capture failure problems when more than one Prime tuner is going on occasion and am trying to work that out with SiliconDust and Andy using logs and Wireshark captures. (SD actually found in the latest capture some oddly delayed packet responses that are either caused by my XP server's hardware and drivers, Sage or SageDCT... at least this behavior is usually repeatable so hopefully we'll track it down. Could be some kind of race condition.)

I'm going to eliminate SageDCT's use of UNC path's at Andy's suggestion (by using "Replace Path") and see if that makes a difference. This will at least remove the MS Loopback adapter from the chain, which gets heavy use when all tuners are recording.

[nyplayer]

I am going to try 2 Nics one dedicated just for the Prime and the other to the switch for the users and my other HD Homeruns. I have clients so to eliminate UNC I would have to go to mapped drives in all my clients to use comskip etc...

If I do not use mapped drives then the server would have to stream HD to all my clients and that just adds to the load... on the server.

[babgvant]

Originally Posted by nyplayer

If I do not use mapped drives then the server would have to stream HD to all my clients and that just adds to the load... on the server.

I use mapped drives.

[nyplayer]

Originally Posted by babgvant

I use mapped drives.

Yeah I am going that route eliminating UNC and use mapped drives slow period in TV watching anyway so gives me ample time to tinker.

[babgvant]

Originally Posted by nyplayer

Yeah I am going that route eliminating UNC and use mapped drives slow period in TV watching anyway so gives me ample time to tinker.

FWIW, I find that assigning a drive letter at the end of the alphabet works best.

e.g. use "S" for recording and "T" for fanart.

[nyplayer]

Originally Posted by babgvant

FWIW, I find that assigning a drive letter at the end of the alphabet works best.

e.g. use "S" for recording and "T" for fanart.

I have mine like this

M:\SAGEM
N:\SAGEN
O:\SAGEO
P:\SAGEP

Then I also run a script at start up on the client to open them up

net use M: \\NYPLAYER\M$ /PERSISTENT:YES
net use N: \\NYPLAYER\N$ /PERSISTENT:YES
net use O: \\NYPLAYER\O$ /PERSISTENT:YES
net use P: \\NYPLAYER\P$ /PERSISTENT:YES

[nyplayer]

Status Report

All Is OK very low cpu usage no breakups.

1. I gave dedicated NIC to the Prime my switch was getting maxed out. With 2 Hdhomerun QAM (4 Tuners Total) the Prime and clients.

2. Converted to NON-UNC Paths.

3. Now able To record 3 HD programs and watch 3 with very litlle cpu usage and memory.


Thanks guys for convincing me to keep trying.

[babgvant]

Originally Posted by Sparhawk6

Ok, here's a sample file. It won't play in Sage at all, but I can play it fine pretty much everywhere else.

https://dl.dropbox.com/u/43581/FoodN...TSSplit.1-2.ts

Does this just happen w/ Food Network?

[babgvant]

Originally Posted by Sparhawk6

Ok, here's a sample file. It won't play in Sage at all, but I can play it fine pretty much everywhere else.

https://dl.dropbox.com/u/43581/FoodN...TSSplit.1-2.ts

Also, the file is quite odd (it doesn't appear to be a valid TS file). Might be worth a conversation with SD.

[Sparhawk6]

Originally Posted by babgvant

Does this just happen w/ Food Network?

No. It happens with CNN, HGTV, and generally channels with numbers close to the Food Network. The catastrophe in all this is that the Food Network and HGTV are the wife's favorite channels. The WAF is very low right now.

[Sparhawk6]

Originally Posted by babgvant

Also, the file is quite odd (it doesn't appear to be a valid TS file). Might be worth a conversation with SD.

I hope it doesn't make any difference that I split the file using a program called TS splitter. I didn't want to post a large file. Who is SD? EDIT: Sorry, I now realize you mean Silicon Dust.

[Sparhawk6]

I posted on the SD forums:

http://www.silicondust.com/forum/viewtopic.php?t=12880

I'm praying for a resolution!