v0.93.10 (13 August - afternoon)

[A_Brass]

Sub, I installed the latest release on two computers this past weekend. In both cases I had problems. One problem was desicrbed in this tread, the other I did not see mentioned. I just wanted to bounce it off of you.

My frist problem was the install finishing but crashing when it tried to run the Config app. I manually opened the config app but all was lost. All config info was wiped out. Core, and plugin's, nothing left So I manually tried to revert to previous version. Not a good idea. Now I have some bastardized GBPVR install that works but is not listed as the correct version. It thinks is current but it's really 92.11 So I see the best route is to save my mdb, and config, reinstall then re-upgrade. No prob. I'll try that tongiht.

Another issue was the install rolling back at the end. As mentioned in this thread, this happend when I was logged into another user account. So I assume that if I'm in a different user account I should not try to upgrade. (Can GBPVR be installed for all users?)

Another note on user accounts. Since I created the same user account on all my computers (to help with share's) I now have a Media MVP server window that opens on startup. What's going on with that? I thought if I had the autostart enabled, I didn't need to run the manual server. Now its running on its own.

Help!

[GoodGuys]

Sorry, I dont understand what you're asking?

To put it simply - I want to get the anti-dupes system to work for XMLTV too.
In order to do this, you need unique show IDs, which are not given by the XMLTV stuff.
I can write a small program that will assign IDs to shows as it encounters them, according to show title, and re-write the XMLTV file adding tags for showIDs.
Would this work?
What would be the tag names that you would parse for showID?
Thanks,
GGF

[sub]

Ah, gotcha.

It wont currently the unique show identifier out of an XMLTV files. It wasnt part of the standard, so it wasnt something I included.

In the next release it'll parse an optional <unique-identifier> element for this data.

[Chris Reynolds]

Sub,
I just thought I'd say thanks for a great release. The use of dvr-ms has solved all of the crash problems I was having with the Pinnacle 300i. If all goes well this week I could at last have a PVR set-up I can trust. I found a utility called 'DVR-Edit' at greenbutton that let me play about with the files too.
I know that dvr-ms support is pretty much alpha-ware at the moment and it seems churlish to comment but F7 for aspect change doesn't seem to work for me.
Once again thanks for a great product
Chris

[sub]

I know that dvr-ms support is pretty much alpha-ware at the moment and it seems churlish to comment but F7 for aspect change doesn't seem to work for me.

I've just tried this here, and its fine. Some MPEG2 video decoders default to locking the aspect ratio unless configured to do otherwise, which may be whats happening in your case.

[GoodGuys]

Ah, gotcha.

It wont currently the unique show identifier out of an XMLTV files. It wasnt part of the standard, so it wasnt something I included.

In the next release it'll parse an optional <unique-identifier> element for this data.

Cool! I'll work from there. Just to be clear, you will expect to see it somewhere between the <programme> and </programme> tags, right?
Thanks!
GGF

[sub]

yes

[jtokach]

It only works with zap2it, but is only as good as the unique show numbers that zap2it supply. Its widely known that these arent as good as they could be...

FYI: Last night when I unchecked the "don't record duplicates" and hit ok on the config screen, and my DB bought the farm again. The config app hung and I eventually had to kill the processes. After I tried to start the services again, the gbpvr.exe's kept restarting themselves, error logs said they couldn't find the mdb. I noticed that there was a file, old.mdb, that was very recent, and restored it to gbpvr.mdb. All but my latest additions were restored.

[sub]

There is a known bug in this release that can cause the gbpvr.mdb to be renamed old.mdb. The problem occurs if it fails to compact the database.
This is fixed in the next release.

old.mdb is just gbpvr.mdb renamed immediately prior to trying to compact the database, so nothing is actually lost.

[GoodGuys]

yes

Would the unique-identifier be any UTF8 string? Some other format?
Thanks,
GGF