Sage 2.0 User opinion

[Crowdx42]

Well Sage 2 finally got released and guess what, it has been the worst release out of all the previous releases I have used. I have uninstalled several times and still have random lockups and at the start of some shows stuttering. This is all using the Clinet, I never use Sage TV itself to watch shows so I am not sure how well it is performing.
How does everyone else feel about the release vs the beta? I have been struggling with this for the last week and on each reinstall have hoped that it may be more stable. Nothing else has changed in the system, it has been all the exact same hardware from before RC1.
Kinda frustrated now.
Patrick

[mlbdude]

I don't think I have had one lockup on the Client yet and I use it extensively. I am not using a 350 on the client though either.

[ToxMox]

I know this may sound silly but have you upgraded both your server and client versions of Sage to .19? You probably have but just wanted to throw that out there. .19 has been the most stable release yet for me. Perhaps something wonky has happened to your hardware since. However I am not using a 350 on my client either. Have you tried testing with just outputting through your video card instead of the 350 to try to narrow down the cause of your problems?

[Crowdx42]

Well EVERYTHING worked fine before Sage went gold. never any lockups at all, regardless of whether it is the 350 that is locking up, it should not be happening, if it was still beta I would be waiting patiently for the next revision, but this is supposed to be the gold version and so I feel a kinda stuck.
Patrick

[mlbdude]

Don't be afraid to go through the official support channels.

[abiharbani]

I've never had lockups _if_ I only use a standalone Sage. However, I'm using sage mainly in client server setup.

I get these problems randomly when I use client:
1. Lock up. No video / audio comes out. The only solution to this is to reboot the server. It seems to me that the encoder is in a screwed up state.
2. Picture freeze. The solution is to wait several seconds and try hitting FF several times. Sometimes I have to stop and start the server (no need to reboot the server though).
3. Server crash. All of the sudden the server would crash.
4. No sound. Sometimes sound would dissappear when changing channel. A workaround is to keep changing the channel until I get sound.

I've tried different decoders: cyberlink, intervideo, elecard, ligos. Tried vmr, overlay.

For a client server setup, 2.0 still feels like a beta software. Can't wait till the quirks are gone. I love Sage as it's the only software that meets my need.

Systems:
Server
Athlon XP 2500+
Memory 512MB
XP MCE up to date
Avermedia M150
Dedicated 200GB 7200 8MB 64k blocksize for Sage recordings

Client
Athlon 64 3200+
Memory 1GB
XP Pro up to date
MyHD 120

Client & server are wired with 100mbps

[DynamoBen]

I too am one of the many that went thru the beta review process. I have to say I am very pleased with the "gold" version that was released. There were some rough releases at points but am quite happy with the final product.

I understand your frustration. I can't say I can related because everything is working well for me. However this is a first release to the public it is bound to have its hiccups. Everyone has different hardware and combinations its hard to be 100% perfect all the time.

Continue to use the support channels and know that Frey will do everything in their power to make it right and work the bugs out.

[Crowdx42]

I agree with abiharbani, all my problems are with the Client, random lockups, changing channels always feels like russian roulette, as 1 in 3 channel changes results in either a full lockup or I have to change off that channel and then back onto that channel again. Something I also have noticed which is SageTV related and only seems to affect the History Channel is that it does not tune correctly, the workaround is to move off the channel and then back onto it.
I am gonna run this 3rd reinstall of the client for a few days and then submit a tech support request with all the log files etc.
Patrick

[SHS]

what under hood of your Client Crowdx42

[Crowdx42]

Athlon 2400 + XP
256mb PC 3200 Geil Memory
A7N-266VM-AA
Ati Vivo 64 Video Card
USB-UIRT
PVR350
XCard
These are the client machine specs, they have not changed since RC1.
I have updated the specs in my signature.

[abiharbani]

Those who has rock solid client server sage 2.0, please state your:
- Java version (type in command line: java -version) both in client & server
- Tuner card
- Audio & Video Decoder
- Client & server OS.

Thanks much,

-- Abi

[mlbdude]

1.4.2_04

2x 250's (15 version) in Server, 2x 250's (16 version) in client 1, 0 tuners in client 2

Server NVDVD, Client 1 Hauppauge Intervideo, Client 2 Elecard

WIndows XP on all

[gplasky]

Java: 1.4.2_04-b05

Server:
2 x PVR250 ver.16's
Video: NVDVD 3.0, nVideo post processing and ffdshow
Audio: Sonic Audio decoder into S/PDIF out to DD receiver
Athlon XP 2500+
nForce2 chipset
FX5200 video card

Client:
1 tuner PVR250 (not being used by Sage. For testing purposes)
Video: NVDVD 3.0 and ffdshow
(will switch to Elecard with Dscaler Tomscomp filter on occasion)
Audio: Intervideo Audio (WinDVD)
Athlon XP 3000+
nForce2 chipset
FX 5700 video card

Release has been best ever for features and stability. I think it was RC2 that gave me occasional hangs every once in a great while. (FF would just stop and take about 5 seconds before taking effect. use_blocking_socket_for_mediaserver=true at the server fixed that.)

My server runs 24/7. I've had solid uptimes between every beta. Never rebooted until a new version came out. The only time I backed off a beta was from a functionality point and once it was fixed I installed it. I haven't had the server crash at all. Couple of times I had video issues at the client which was caused by me tweaking or tuning or trying new versions of ffdshow. I don't run the client 24/7 but I don't have any of the issues some folks seem to have.

Gerry

[kny3twalker]

yeah I think playback was at its best with .015 and staability was best with 2.018
I also have had a couple new issues pop up
I just got a tuner while waiting for hauppauge to send me my old one back
and I have had weird stutters in the files themselves since putting in this card but not often
I have also had my client blue screen tonight in the middle of a show
but that could have been the audio render I was messing with
I am getting my other tuner back soon and order a copy of XP Pro so I will do a clean install with 2 new tuners shortly
I am not worried though
my only real complaint is with 3d accleration not working like it use to

it was awesome in some of the betas and not it causes stutters one or two a show
and VMR 9 which has never worked well with my hauppauge files
yet is great with DVDs though

[rak306]

Crowdx42,

I'm having similar problems, see:

See my post

I switched back to 2.0.15 as that works ok for me (without 350 UI enabled).

By the way, I don't have and of these lockups on the client with the 350 disabled. So I think this is also a 350 issue.

Rick

[SHS]

My SageTV Client is just an old P3 600, with 512MB memory, GF3 Ti200 Soyo Slot1 BXchip, Realtek 8139 and SBLive.

[Chilli]

Crowdx42,

I have almost the exact same specs as your client A7N266VM/AA Athlon 2400+ PVR350, except I have a standalone system and 512MB of cheap memory (Spectek) Everything works fine for me for the last 5 days.

Java 1.4.2
PVR350
Video decoder = default
Audio decoder = Intervideo
WinXP Pro SP1

[Crowdx42]

Well an update on my issues. I went to watch Enterprise live on the client tonight, nothing, no output on PVR 350, changed decoder to software, still nothing, reboted machine, still nothing, uninstalled the client, installed RC3, worked BUT seems that the live show I was tried to watch now is screwed up also on the Server, so I miss 7 mins of the show, it is not showing as missing (red) just watched and will not rewind back to the beginiing.
So this problem seems not just related to the client alone, more so it seems to be the server sreaming to the client.
Arrrgggggh..