|
SageTV Beta Test Software Discussion related to BETA Releases of the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. regarding SageTV Beta Releases should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Any PVR 350 related bug fixes w/ Sage 2.1??
Just out of curiousity, are there any bug fixes to improve stability for the 350, especially related to using the OSD? I didn't see anything specifically listed in the release notes on the web.
Specifically, the two things that plague me (and most 350 users) most are: - The end-of-file bug (Sage takes about a minute or so to respond when reaching the end of a recording) - Hard lock-ups with heavy ff/rw usage (doesn't happen to me very often; maybe once a month) I know these are likely driver issues that need to come from Hauppauge, but hey, can't hurt to ask, right? Also, a side note: anyone know if we can expect some new 350 drivers any time soon? SHS, you know anything? Justin |
#2
|
|||
|
|||
I'm gonna guess that some of the 350 problems may have been solved with them saying "Numerous Bug Fixes and Performance Enhancements".
However, it sure would have been much nicer if they would have list just what those "Numerous Bug Fixes and Performance Enhancements" were! Got similar problem over at shspvr... "new driver" with usually no hint as to what (if anything) it actually fixes. Strange, with any other software they usually have a complete EXACT list of what they changed/fixed and why. With this PVR stuff even when they fix something it seems to be kept top secret. |
#3
|
|||
|
|||
Quote:
Also, correction to my question about new 350 drivers... I saw that on SHS's ftp site, in the inf directory for the 250/350, there are several "new" drivers there, the most recent dated September 10th I believe. I looked at the release notes and the last modification was made last month! Compared to the release notes for what you download from Hauppauge's site, where the last modification was last January. Looks like the most recent version is 22254. Was everyone else aware of this besides me? Was there ever a note about this and I missed it? Has this driver fixed any 350 problems mentioned above? Anyone? Bueller? Fry? Justin |
#4
|
||||
|
||||
I don't know about stability fixes, but I installed 2.1 last night and everything seemed snapier though my 350. All menu changes, FF/RW - everything seemed faster. Could be my imagination, or the fact that I just put a slot cooler on my 350, but right now I'm attributing it to 2.1.
I don't know anything about the drivers though. I installed new drivers for the first time in 6 months a couple of weeks ago. used the most recent at the time from the hauppauge site. Seem to be rock solid now. To all those having problems with the 350, what are your case temps? In my case (pun not intended) the temps used to be 40C, I put a slot cooler right on the 350, and now they're down to 36C, and it seems MUCH happier. The 350 probably saw more than a 4C drop b/c it was tucked away in the bottom of my case. Anyways, people should check that first, before looking for driver fixes. |
#5
|
|||
|
|||
Nope, both of these issues are easy to reproduce with 2.1.
-End of file bug is easy, just let a show end (it might just be luck in what I have noticed so far but the system process does seem to die off a little sooner than in 2.0). -FF/REW a few times, CPU usage jumps up to 99% (only if the UI is enabled, FF/REW with only TVOut enabled is under 20%) and soon the UI will hang and you get the green screen of death. It appears that some attempt has been made to address this issue because it seems that Sage is trying to reset things but it hasn't ever worked for me. The UI does come back but you can only play video for a split second before the card locks up for good. You might get a few tries at it but the lockup is inevitable. It would be good if you could disable whatever the fix is because at least using a manual method you could restore it before without a reboot. Now its trying to do something on its own and it's not working correctly and instead making things worse. Being that there is a tried and tested workaround, I wish Frey would just accept this is a problem that they cannot solve at the moment for whatever reason (perhaps a driver simply out of their control) and create a command that would execute the simple fix. Everything is already there, it just needs to be tied together as a command. peace . . . Quote:
__________________
PVR user since the late 1900's . . . |
#6
|
|||
|
|||
hrm... I'm going to give the 2.1 a try... The ONLY update I'm really looking forward to is fixing all the bugs with the PVR-350. Since this card is conceivably one of the best video-out solutions for sagetv, I'm suprised more time hasn't been spent on addressing these SERIOUS BUGS. Cosmetic changes on features that already work fine; those don't interest me that much.
|
#7
|
|||
|
|||
I'd just like to remind everyone that if you do have ANY problems with the beta v2.1 that you should report it directly to Frey (preferabably thru their bug report form on the beta download page). They don't read each and every post in this forum, so unless you tell them it very likely won't get fixed.
From my past experiences with them I will say they DO try really hard to help fix problems. It may not always work out, but they do at least try their best. I have to give them a lot of credit for their effort to do so. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|