SageTV Version 1.4.7 Beta Available

[robogeek]

Sorry Narflex,

I've been using the SageTV server when experiencing the conflict problem. I keep forgetting I have SageTVClient sleeping on the HTPC in the livingroom

Hang on a second and I'll go check the client and see if the conflict resolution works from there. It still shows me a ! in a yellow TV box in SageTV so I know there are conflicts and when I go to Favorites it says 'There are unresolved scheduling conflicts. Do you want to be asked about these now?' with a Yes or No choice. Whether I choose yes or no it won't bring up the conflict resolution screen...unless I exit and restart SageTV.

OK..I'll go check the client now and post back in a few minutes

[robogeek]

Narflex,

OK, I think we can narrow the problem down a little more. I brought the client back in fullscreen on the HTPC and had the little ! in a yellow TV box. Clicking it gave me the conflict resolution screen. Then I shutdown the SageTVClient and went back to the SageTV server. With the client disconnected, the conflict resolution works in the server. I can click the little ! box and it brings up the conflict resolution screen right away. I went and restarted the SageTVClient and clicking the little ! box in the server didn't work again but still works on the client.

[salsbst]

I upgraded the drivers for my 2 250s and now the Recording Schedule doesn't list any cards (e.g. no SAGE 1 and SAGE 2).

UPDATE: I removed both sources and re-added them. Now, I do have SAGE 1 and SAGE 2 under Recording Schedule but when I set something up to be recorded, nothing appears under Recording Schedule.

I have zipped my properties and wiz.bin and emailed them to support.

UPDATE #2 (8pm Saturday): SageTV froze. Upon restarting the application, it now occupies 286 MB of RAM.

I deleted Wiz.bin. I am discouraged to have to do this.

Thanks,
Stuart

[bodgadle]

Originally posted by gplasky
Thought this was addressed (see number 2):

V1.4.5 Beta 7/14/2003
1. DirecTV Serial Control is now FULLY INTEGRATED. You can even control multiple DirecTV receivers by simply selecting a different COM port for each one. Thanks to Marty Gottesfeld of Amnet Voice & Data Systems, LLC for supplying the code for this.
2. Added mmc/always_tune_channel property. If set to true, it'll always send the IR/serial/plugin tune command even if its the same as the last command sent.
3. Removed "(NTSC)" from Python2 encoding namings since it doesn't apply.
4. Client/server clock syncing doesn't have a limit on how much it will adjust the clock anymore.


Gerry

lol, thanks for pointing that one out Gerry, that's what i get for missing a previous beta release

Thanks Jeff )

[justme]

Added scheduler_export_file property. If it is set, SageTV will write out the current schedule to that file whenever it changes.

My recordings schedule file does not seem to update unless I have to restart SageTV. The only other time I've noticed an update to the file is if I delete/rename it, then the file is eventually replaced with a new one. I guess this new copy is created when SageTV updates it's EPG data, I can't really say.

As an experiment I left the export file intact and did not restart SageTV for over two days. The file was not updated. I have actually gone into the RecrdingSchedule cancelled/scheduled recordings. The export file shows no changes hours later. Is this the normal behavior?

I would think the file should update as soon as a change occurs, this would help when controlling sage from afar. While writing this message I just picked a empty slot and scheduled a recording on the history channel. I then checked the export file and no change. Is this a beta bug or the designed behavior?

I have attached my logs. They include the manually scheduled show I mentioned in this post. Let me know if you wish a copy of my Wiz or properties file as well.

Much thanx

[Narflex]

justme,

That would be a bug. Thanks for catching it. It's fixed for the next build.

[justme]

I'm not sure if this is a beta issue or not, so I though I'd post here to avoid confusing others.

The issue(see tittle) has to to with shows within a group(auto_categorize_epg=true). The first week or two of shows is shown in newest to oldest order, but after that the order seems to reverse, at least for a while(*see example list below). By doing some checking in my different show groups it seems that 7/29 is the date when things changed. I believe that's when installed the 1.4.7 beta. Was there a change in the way this beta handles shows lists? If so, I like it. Or is this just some weird conincidence?

*simplified of a show list(Kikaider)
Fri 8/1
Thur 7/31
Wed 7/30
Tues 7/29
Tues 7/22
Wed 7/23
Thurs 7/24
Fri 7/25
Fri 7/18
thur 7/17
Wed 7/16

[salsbst]

I'm getting an intermittent thin black line about 1/4 screen width from the right side of the screen in the video frame.

If I bring up the OSD, the blue areas "erase" the portion of the line that they intersect with.

If I go back to the guide and come back into the video frame, it usually goes away (for a little while).

It does not seem to matter which video decoder I use (have tried default and Sonic) nor whether I use VMR or overlay and upgrading to DirectX9.0b didn't solve it either.

All of this leads me to guess that it must have something to do with SageTV beta, rather than a 250 driver issue.

Strange.

[insomniac]

Just wanted to throw it out there if it hasnt been already..

When I delete favorites which had been recorded (with "First Run") , if that particular show comes up again, it will record it again.

e.g.

real world gets recorded. I watch it and delete it. Comes on the next day and sage views it as a first run again.

anyway, just a minor annoyance..


I.

[dkardatzke]

I,

What you are experiencing is most likely not a bug, but actually a lack of information on the specific episode for the Real World. MTV is notorious for not providing any unique information about First Runs in their description. Thus SageTV doesn't know if the First Runs are unique or not. Take a look next time this happens to see if this is the case.

[mangriotis]

The lack of specific show information is exactly what is happening with Making the Band II. Every show has the same descriptor, so it records every run when available (and this show is repeated quite often, and not just one episode but several of the last few weeks, etc.). I usually just watch the first few minutes to see if I have seen it already then click 'watched' and it moves to the bottom...

[Narflex]

If you ever wondered....

The (N) that you sometimes see in the EPG Info for a show is to indicate it is a non-unique show. The same thing you're talking about here.

[dballer1]

I tried adding in scheduler_export_file in the sage.propeties by stopping the server, adding "scheduler_export_file=c\:\\schedule.txt " and started the server back up.

It doesnt write out the schedules to the file! Am I doing something wrong?

[Narflex]

This was fixed in 1.4.8. That's available now.

[salsbst]

Originally posted by salsbst
I'm getting an intermittent thin black line about 1/4 screen width from the right side of the screen in the video frame.

If I bring up the OSD, the blue areas "erase" the portion of the line that they intersect with.

If I go back to the guide and come back into the video frame, it usually goes away (for a little while).

It does not seem to matter which video decoder I use (have tried default and Sonic) nor whether I use VMR or overlay and upgrading to DirectX9.0b didn't solve it either.

All of this leads me to guess that it must have something to do with SageTV beta, rather than a 250 driver issue.

Strange.

I did not see this problem once last night... even before upgrading to 1.4.8. The only way I could explain this is if one or both of the following changes are not applied until either SageTV or the PC is restarted:

VMR vs. Overlay choice
video decoder choice

Thanks,
Stuart