Malore Watched Bar tearing again

[zoundz]

Help me. Help me. My Malore watched bars just started tearing again for the first time in forever.

Here's the deal. I accidentally started the client when the service wasn't running. I normally run with the service. The result of this is that the client used Sage.properties instead of SageClient.properties. Since this .properties was never initialized by the client, it started the setup wizard and loaded the default .properties file. This simple oops lost all the weird things that had been added to .properties since version 2.2 and Cayars stv. After getting things back to normal the only apparent problem is that now the Malore watched bars in the current recordings screen are doing their tearing and irrational thing when they are over playing video. I've looked at old .properties files looking for what might fix it. Can't find it. I'm sure it's there somewhere. I really don't want to just revert to an old file. I'd rather find the problem.

I've started from scratch on the .stv a number of times. I'm running SageTV3.stv with malore3_import.13.stvi, nielm ff and rewind stvi, and nielm dynamic menu stvi. I've tried all the combinations I can think of. If I start with the bare SageTV3 stv, the upcoming recording schedule is OK. As soon as enable the unsupported extras and use Malore current recording list, the watched bars tear and the upcoming recording schedule gets ugly. If I turn off the Malore watched bars, it all gets ok.

Anyone remember how to fix this? Overlay is not an option and this worked fine forever. I've tried searching the forum, but didn't find anything.

The thing is that basically nothing in the system changed other than SageTV decided to reinitialize it's properties files.

Running VMR9 on Nvidia GEForce 4 MX440 with the latest drivers. Win2K, 512MB, Sempron 3000+

TIA for any help

BTW, it seems to me that the behavior that initiated my problem is a fundamental bug/feature that should be looked at. Accidentally starting the SageTV UI without the service should not cause problems. The thing is that Sage.properties is not kept up to date with changes in SageClient.properties. There are lots of things that exist only in the client file after the system has been tweeked and adjusted. I'm not sure how to fix it, but it's definitely a potential problem waiting to happen. Possibly SageTV should use both files no matter what mode it's started in. That is the engine stuff that the service uses should always come from Sage.properties and the UI stuff should always come from SageClient.properties, no matter whether the service is being used or not. Getting the UI information from 2 different places is just asking for problems IMHO.

[Opus4]

Once you exit the UI, restart the service, then restart the UI, the UI portion goes back to using the sageclient.properties file that you were using previously, so all your previous settings should be intact.

As for the graphics glitches, about all you can do is turn off 3D Acceleration or at least disable playing video while on any menus.

- Andy

[zoundz]

Originally Posted by Opus4

As for the graphics glitches, about all you can do is turn off 3D Acceleration or at least disable playing video while on any menus.

- Andy

That's what's got me bugged. Prior to the UI incident, there was no problem with the malore watched bars on top of video. After the incident they are screwed up. I'm trying to figure out what the hell happened. Turning off 3D Acceleration in V4 also turns off VMR9 AFAICT. Overlay doesn't really cut it in the clone monitor environment on NVidia. This system worked flawlessly for months before this little happening and then something changed. Truly strange.

Still looking for suggestions on how to get rid of the tearing.

Thanks

Additional information. Just noticed that the watched bars and other stuff do NOT tear when the underlying video is paused. As soon as it is started playing again, the tearing returns. Since other threads have speculated that this problem had something to do with errors in drawing the boxes in the malore display, I wonder if there is any connection to de-interlacing here. I tried Bob, Weave, both, default and Irving, but they had no effect.