r5000 system messages

[RandyJohnson]

Since I upgraded to the latest version of sage 6.6.2.218 I keep getting the following system message:

Error - Halt Detected in Recording
The device input "R5000HD-100458E on 127.0.0.1:6970 USB" stopped producing data while recording "XXXXXX" on XXXXXX on physical channel XXXX. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

Any idea how I an go about fixing this?

I have upgraded to version 3.1c of the r5000 "multi" version as I have 4 r5000 recorders.

Some recordings work but most do not. This is definitely lowering the WAF.

Thanks in advance...

Randy

[RandyJohnson]

Anybody...?

[dgschoel]

I am having the same problem with my r5000 since updating to the latest version of Sage. Previous versions did not have this many failed r5000 restarts and failures. It looks like Sage is mistakenly determining that there is inadequate signal from the r5000 and causes unnecessary restarts in the recording process. Is there any way to lower the sensitivity to this forced restart of the recording?

[Fuzzy]

I don't think older version of sage checked at all, so you may have been having these 'glitches' all along. You could try using the R5000 Proxy app over at AVSForum.. it does sort of work around this issue. However, I think your problem may be somewhere else (possibly USB controller?)

[iammike]

I think I'm seeing the same problem too. The R5000 log says it received a stop message from Sage, and then it says that Sage sent a start. A snippet from my log file is below:

18:53:59 Sent filesize: 457312256
18:54:14 Raw string: GET_FILE_SIZE W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-1.ts

18:54:14 GET_FILE_SIZE of W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-1.ts rec'd from Sage
18:54:14 Sent filesize: 457312256
18:54:14 Raw string: NOOP

18:54:14 Ping from Sage
18:54:14 Raw string: GET_FILE_SIZE W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-1.ts

18:54:14 GET_FILE_SIZE of W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-1.ts rec'd from Sage
18:54:14 Sent filesize: 457312256
18:54:14 Raw string: STOP

18:54:14 STOP rec'd from Sage
18:54:14 Raw string: START Dish211-100595E USB|139|2511467309504|W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts|MPEG2 Max Quality

18:54:14 START rec'd from Sage
18:54:14 Sat: , Channel: 139
18:54:14 Profile Matched: 100595E (0)
18:54:14 Profile used: 100595EAB›pNp2Q

18:54:14 Recording launch from SageTV: CH 139-0, W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts...Set timer and exiting
18:54:14 Sage recording fired...
18:54:22 Opening ts file for SageTV: W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts
18:54:29 Raw string: GET_FILE_SIZE W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts

18:54:29 GET_FILE_SIZE of W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts rec'd from Sage
18:54:29 Sent filesize: 3128320
18:54:44 Raw string: GET_FILE_SIZE W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts

18:54:44 GET_FILE_SIZE of W:\Sage Recordings\MLBBaseball-NationalLeagueChampionshipSeriesGame2TeamsTBA-386884-2.ts rec'd from

[kbates]

Just to add another vote, I'm also seeing these messages on a regular basis since upgrading to the latest SageTV. Upgrading to the latest R5000 software didn't seem to help. As an FYI, I'm also seeing the same message for programs recorded from HD HomeRun (over the air) HDTV that is connected to SageTV. In all fairness, those messages are for a channel that is very weak in this area, so they could be valid. I guess it all depends on what is meant by a "halt", since I certainly can't detect any video problems such as dropped frames.

[btrcp2000]

I am about ready to trash these r5000s, and I am rapdily coming to the conclusion that upgrading my server's hardware and os to whs was a colossal mistake. Since then I have had nothing but trouble from the r5000s and my hdpvr, where they were flawless before. r5000 gives me a different problem every day, either asking for the license key endlessly, or cranking out endless system messages. has anyone figured out the secret to this?

[MrFusion]

Hi,

I had a similar problem with my DVB-T tuners after upgrading java to 1.6.0_17. Rolled back to _15 and problems evaporated.

Any good for you?

[btrcp2000]

Without saying anything that would be too revealing to the jinx gods that I have come to believe in since starting with sage, I would like to simply wish MrFusion an extra happy holiday season... so far...

[lolachampcar]

I am also having R5000 drop outs. Can someone please give me some hints to "Rolling Back Java".

THANKS in advance.

Bill

[MrFusion]

Originally Posted by lolachampcar

I am also having R5000 drop outs. Can someone please give me some hints to "Rolling Back Java".

THANKS in advance.

Bill

Presume Windows... Simple way -- go to control panel; add/remove programs; remove the latest version(s) of Java; get _15 from Sun website & install.

You could also go to the Java control panel applet, Java Application Runtime Settings, and disable all but _15 (presuming you have multiple versions installed, though I didn't do this, so I don't know how well it works).

Cheers.

[lolachampcar]

Thanks.
I went to Sun and got _15 from their archives, installed and am on day one of no R5000 failure messages. I will report in a week or so...

Thanks again to all that contributed to this thread.

Several more days down the road without issues....
Thanks Much for the tip!!!!!!!!

[stanger89]

So you guys still having this issue, or has the Java version rollback or something else solved the issue?

Well I just ordered one so I guess I'll find out soon

[lolachampcar]

Just a quick warning if you do not already know (I did not)-
You will be charged extra when you want to download the R5000 software if you want "Sage Support". This does not show up when you buy your hardware, only when you go to install the software after getting your hardware configured.

[Fluffdaddy]

99.9% of peeps already knew this "before" buying.

[lolachampcar]

I just got three successive errors from the R5000 after weeks of no problems. How is everyone else doing on error messages?

[Fuzzy]

I'm doin alright on mine since downgrading java to _15. I do still get the occasional message, but I'm pretty sure it's due to signal issues throwing hitches in the works.

[stanger89]

Well, I was having a lot of recording halts (and thus messages) when I just recently installed my R5000, it was the "c" software, and I apparently had some rather old version of Java 6 (like update 2 or something).

Since updating to update 15 and the new "d" R5000 software, not a one.

[voorhees]

Originally Posted by stanger89

Well, I was having a lot of recording halts (and thus messages) when I just recently installed my R5000, it was the "c" software, and I apparently had some rather old version of Java 6 (like update 2 or something).

Since updating to update 15 and the new "d" R5000 software, not a one.

@stanger89, thanks so much for posting this. I did not even realize there was a "d" version. It looks like it fixes the port issues I was seeing and the dropping out and reestablishing every once and a while. However, I will not get a chance to test it tonight, since we have a showing of our house first thing in the morning and have to clean up after the guests for the holidays tonight. Thanks again for the info.

[panteragstk]

I've been thinking about getting an r5000 box. Are issues like this common? I don't want to shell out the cash for one and have these kinds of problems.

Also, I thought that these boxes were going to become extinct soon as cable/satellite companies weren't making compatible boxes any more.

Correct me if I'm wrong.