Client 13 + SageRecorder problem

[ericr]

Hey all,

Now I might have just plain messed this up but here goes. I updated to client 13 no problem and then the following day added SageRecorder (production version of course)

I followed the reference page here about copying the info from the properties file to the server.. so far so good. The server sees the new source no problem. Shows are set to record there and life seems to be good.

The next day I bring up the TV onto the input with Sage client and have a message box up, in fact there were several queued up. Basically I think the client was trying to do something and there was a conflict with the recorder. I would have to repeat the process to get exact message box contents.

Does this sound like something you all have run into with this configuration?

If this is a problem should I move my tuner from the client to the server and install the recorder there?

Thanks!

[jptaz]

Did you upgrade to 1.5 of sage recorder? 13 requires 1.5 of recorder to work

[ericr]

Hmm, good question. I just downloaded the other day so I'll check.

Edit: the download was SageRecorder_V1_4_10Setup.exe so I guess not.

Is there a link to that version around?

[fidget]

Originally posted by ericr
Is there a link to that version around?

Yes, try here.

[ericr]

Ok, I have that installed but its pegging my CPU..

On the Video tab in the recorder's setup, I have all of the items set to default.

[ericr]

Bump..

I'l still having problems with the recorder on my client. I get popups and the cpu is still pegging. Is anyone else having this kind of trouble? If not I;ll document and bug it..

[ericr]

I just thought of one other question after reading another thread..

Where should recorder store the recording at? Currently I have it as a UNC back to the server. Should I change te location to be local to the client and add the directory to the server?

[fidget]

Originally posted by ericr
Bump..

I'l still having problems with the recorder on my client. I get popups and the cpu is still pegging. Is anyone else having this kind of trouble? If not I;ll document and bug it..

What do the popups say? The fact that you get them is not nearly as important as their content.

[mlbdude]

SageRecorder when used with SageTV as a network encoder does not use the store path in SageRecorder. It pulls this from the Server.

So, if on the server you have video directories M:\ and V:\, then you must have those same paths available on the SageRecorder machine. If you want to use UNC you need to setup your video directories on the server as those UNC paths. Then make sure the SageRecorder machine has access\permissions to that exact path.

[ericr]

Ok,

Here is what I did to get to this point.

I have to server going of course.

I start a client on my desktop and tune to some channel, full screen.

I start up the recorder on my client system and then the Sage client.

I tune to a channel and the popup has:

There was a problem utilizing the SageTV DirectShow Filters. Unable to set the file in the dump filter. ErrCode=0x80070015

When the popup comes up the CPU pegs.

Part of the fix was:

1. On the server I shared the root on the D drive
2. On the client with recorder, I had to move my D drive (a cdrom) to E
3. Mapped a network drive as D: to the share made in step 1

The result is no more error but the recorder system is still pegged and both clients are displaying jerky video

Edit:

I noted that both client systems are pegged. Also
I put the system with recorder back to the top menu and then with the other client I tuned to the same show that the recorder had been recording and got this error (not as a popup but on the main screen):

There was a MPEG-2 Video Error in playback. Details:

Failed connecting video stream to the Overlay mixer
ErrCode=0x80040217

[fidget]

I would recommend using UNC pathes for everything. There is a requirement that both SageRecorder and the server use the same paths when storing files. this gets around having to make sure that everyone has the correct volumes mapped to the same drive letters. The UNC path would be \\computer_name\share_name\

[ericr]

Ok, I put the UNC back into the recorder but I used the new one I had made to map the drive but that did't work, I'm back to the same error message.

Also, unrelated but I turned on the 350's TV out to try and get rid of the CPU pegging, I restarted the client.. sometimes Ive noticed that all I get are the color bars.. is there any answer for that?

[fidget]

Originally posted by ericr
Ok, I put the UNC back into the recorder but I used the new one I had made to map the drive but that did't work, I'm back to the same error message.

Also, unrelated but I turned on the 350's TV out to try and get rid of the CPU pegging, I restarted the client.. sometimes Ive noticed that all I get are the color bars.. is there any answer for that?

I think I need to start back at square one.

1) What are the UNC paths that you are using?

2) Are you sharing a directory with the same name as is used in the UNC path? I.e., On computer pvr, I am sharing d:\video\recordings\ as video, so my UNC path is \\pvr\video\. You can not use \\pvr\video\recordings\ unless each directory in that path has been shared (at least that has been my experience with WindowsXP).

3) Are all of the directories that hold video being shared and accessed via UNC paths? The error you are showing looks as if the directories are not being shared.

[ericr]

Yes, its the same path but I think I might understand the problem. Are you saying that the path that was used in the server should also be a UNC?

Currently, the server stores recordings in D:\SageTV and I noted in the recorder that it was trying to save its file to D:\SageTv\filename.whatever

On the client, as soon as I mapped a D: to \\server\SageStorage which points to the server at D:\ every thing is fine.

I think what you might be saying is that I should use the same UNC path in the server so that when the recorder gets this path it points to the correct location.

[fidget]

Yes, both the client and server must have the same UNC path. I discovered this the hard way early on.