r5000 live

[RandyJohnson]

Has anybody seen a problem while attempting to watch a live stream from the r5000 that causes the CPU to race over time.

If so is there a solution or fix?

It appears that Sage keeps asking for the file size which is continously changing.

Over time Sage keeps asking for the file size so much that it brings the whole system to a halt.

Other than not being able to watch an r5000 stream live, I have 4 installed and they are working flawlessly.

Once I installed the Power DVD 8.x Ultra software, I have had no problems playing back any r5000 recordings once completely recorded.

I also modified the number of buffers registry setting, that was mentioned elsewhere in the forum.

Thanks in advance...

Randy

[NEOSG]

Are you saving the files that SageTV is recording via the R5000 to a UNC path

[SpiffyRex]

Has anybody seen a problem while attempting to watch a live stream from the r5000 that causes the CPU to race over time.

Are you running anything else in your sage server?

Other than not being able to watch an r5000 stream live, I have 4 installed and they are working flawlessly.

Could you post your r5000ver30 network encoder settings? I would like to compare it with mine and see if the problem is there.

Are you saving the files that SageTV is recording via the R5000 to a UNC path

I have been saving the recordings to a UNC path for a long time with no problems. Do you have a HDHomeRun? The only people I see having problems with UNC paths are using the r5000 and the HDHR.

[RandyJohnson]

SpiffyRex...

Yes I am using UNC paths.

I currently have a system that has 5 OTA HD vBox cards, 2 PVR 500 cards, and then the 4 r5000 boxes attached.

It is only when watching the stream live that I am having problems.

Regarding the preferences:

Record to: Disk Only
Auto Generate Filenames as Date/Time is checked
Bit Rate: Compressed (no filler pkts)
Service: EchoStar(Dish)
STB Model: DISH 211/411
.ts (Mux direct to Transport Stream) is checked

Is the above what was being asked for?

Again thanks...

Randy

[SpiffyRex]

I currently have a system that has 5 OTA HD vBox cards, 2 PVR 500 cards, and then the 4 r5000 boxes attached.

That's 13 tuners! What kind of hardware is this running on? Are you playing mpeg2 or h.264, or both? Is there only one tuner active when the CPU utilization rises? Do you get stuttering or is just abnormal CPU utilization? I assume you have a dedicated recording drive(s), with a 64K block filesystem since this doesn't happen all the time. Sorry for all the questions but need more clues.

Regarding the preferences:

Yes, tks. Will compare them with mine when I get home. What's the recording directory? It's shown as "save as" in the main window.

Can you test this without UNC paths to see if it makes any difference? I'm not saying there isn't a problem but that it looks like a configuration issue or incompatibility with the HDHR network tuner. Since you don't have a HDHR it could be a configuration problem or, hopefully not, a problem with the r5000 network encoder.

[jmv]

this is the UNC path problem...If I remember correctly (it is written somewhere on the furums) you can use UNC, but the path needs to be identcal on both the server and the clients...ie sharing the root drive G:\ and putting recordings in G:\Recordings...and setting the UNC path as \\Server\Recordings...

Sorry if this is confusing, but I'm not at home...

[RandyJohnson]

The recording directories are setup as follows:

\\sagec03\SageTV
\\sagec03\SageTV2
\\sagec03\SageTV3

I also have an 8TB raid system that contains the DVD collection

\\HSAS01\DVDs

The main server is a AMD 2.61Ghz Dual Core w/2GB of RAM.

The only time that the server has a CPU problem is when I am watching a LIVE stream from the r5000.

I rarely use the SD channels. About the only channel not on dishHD is FX so that is recorded from the SD channels.

The OTA recordings I believe are MPEG. The Dish r5000 are h.264.

I was having problems playing the h.264 until I installed PowerDVD 8 Ultra on the client machines.

In talking with the r5000 people they said they had heard about this CPU race problem before, but had not been able to reproduce it.

Hopefully we will get some feedback from them as we sent them a bunch of logs.

Again thanks for the assistance...

[SpiffyRex]

The recording directories are setup as follows:

\\sagec03\SageTV
\\sagec03\SageTV2
\\sagec03\SageTV3

You don't need to put the UNC path in the r5000HD app. The r5000HD app is Nextcom utility to record from the USB port. To that they added the SageTV network encoder. Been a network encoder it uses a machine: port# format rather than drive: pathname. In my Sage server my recording drive is E: and I have two recording directories, E:\r5000HDrecordings and E:\SageTVrecordings. The later is the one I use as the UNC directory. The former is the non UNC path that I put in the "save as" entry in the r5000HD app. So when the r5000 app is idle it shows E:\r5000HDrecordings\[datetime].ts as the recording pathname and when it's recording it shows \\MC\SageTVrecordings\filename.mpg. It obtains the UNC pathname from the Sage server, not from it's configuration file. Don't know if this makes a difference but that's the configuration I have been using for almost two years without a problem.

[RandyJohnson]

Thanks I will give it a try

[RandyJohnson]

I spoke to soon about the flawless playback.

The first couple of recordings did playback smoothly.

Now I am seeing a very jerky playback.

The audio is ok but the video seems to have slight frequent pauses.

Are there any registry settings that need to be set?

The video card is Nvidia 8700 GTX.

The processor is an Athelon 64 3500+ with 1 MB of memory.

The standard OTA mpegs did not have any problems.

Thanks in advance...

Randy

[SpiffyRex]

Are there any registry settings that need to be set?

For smooth h.264 you need to change:

Frey Technologies\Common\DSFilters\MpegDeMux\NumBuffers

from 40 to 80

[RandyJohnson]

Yep...

That was the only registry setting that I changed.

Does anybody know if the Nvidia 8700 GTX card have hardware decoding for h.264?

Randy

[SpiffyRex]

It appears that Sage keeps asking for the file size which is continously changing.

Has this gone away? I'm curious b/s several people seem to have problems with UNC paths and the r5000HD but I never seen it on my rig or on other neighbors and co-workers systems.

[Slipshod]

Originally Posted by SpiffyRex

Has this gone away? I'm curious b/s several people seem to have problems with UNC paths and the r5000HD but I never seen it on my rig or on other neighbors and co-workers systems.

I never saw it either. Been running fine for a couple of months.