Anomalies using Sage.jar v9.0.0.3 in SageTV7

[Denali]

1. SRE fails to load. Core dependency for 7.1.9.256. Noted in SRE thread.

2. Some EPG shows fail to show Future Airings.

3. Some Favorites fail to show all Additional Airings. Example Favorite of Lassie does not show Timmy & Lassie programs.

[nyplayer]

Originally Posted by Denali

1. SRE fails to load. Core dependency for 7.1.9.256. Noted in SRE thread.

2. Some EPG shows fail to show Future Airings.

3. Some Favorites fail to show all Additional Airings. Example Favorite of Lassie does not show Timmy & Lassie programs.

Great post ... saves me the trouble of copying over to my production server as there could be other problems that we are not aware off... I really do not watch YouTube on my TV so no reason for me to upgrade.

[Denali]

May go back to 7.1.9.256 Sage.jar before I get to far ahead although I do like the snapper performance of 9.0.0.3.
Will give it a few days to see if anybody else see's similar anomalies. Don't thinks it matters but this is with Win 10 Pro.

[nyplayer]

Originally Posted by Denali

May go back to 7.1.9.256 Sage.jar before I get to far ahead although I do like the snapper performance of 9.0.0.3.
Will give it a few days to see if anybody else see's similar anomalies. Don't thinks it matters but this is with Win 10 Pro.

I believe you cannot go back it converts the DB.... I could be wrong.

[Denali]

I saved a backup of the Sage folder prior. Just restore the original Sage.jar & lucene-core-3.0.1.jar. Also Wiz.bin.

Also found another anomaly on some programs & not others:

[SHS]

Originally Posted by nyplayer

I believe you cannot go back it converts the DB.... I could be wrong.

You can it should have save a backup copy with a ver number, check the in C:\Program Files (x86)\SageTV\SageTV

Just Del
Sage.jar
lucene-core-3.6.0.jar
Sage.properties
Sage.properties.autobackup
SageClient.properties
SageClient.properties.autobackup
Wiz.bak
Win.bin

Restore by rename the backup
Sage.properties.SageTV V7.1.9.256 = Sage.properties
SageClient.properties.SageTV V7.1.9.256 = SageClient.properties
Wiz.bin.SageTV V7.1.9.256 = wiz.bin

Uninstall sagetv and Reinstall sagetv to get back the old Sage.jar

[nyplayer]

Originally Posted by SHS

You can it should have save a backup copy with a ver number, check the in C:\Program Files (x86)\SageTV\SageTV

Just Del
Sage.jar
lucene-core-3.6.0.jar
Sage.properties
Sage.properties.autobackup
SageClient.properties
SageClient.properties.autobackup
Wiz.bak
Win.bin

Restore by rename the backup
Sage.properties.SageTV V7.1.9.256 = Sage.properties
SageClient.properties.SageTV V7.1.9.256 = SageClient.properties
Wiz.bin.SageTV V7.1.9.256 = wiz.bin

Uninstall sagetv and Reinstall sagetv to get back the old Sage.jar

Thanks SHS I will keep that in mind if I ever upgrade.

It kinda hoses up my Diamond Legacy Plugin ... and that is the one I use because it is simple and I can easily organize my seasons.... So no chance of me upgrading.

[stanger89]

Originally Posted by Denali

1. SRE fails to load. Core dependency for 7.1.9.256. Noted in SRE thread.

2. Some EPG shows fail to show Future Airings.

3. Some Favorites fail to show all Additional Airings. Example Favorite of Lassie does not show Timmy & Lassie programs.

Did you enter your license key the new way:
http://forums.sagetv.com/forums/show...&postcount=177

[Denali]

Originally Posted by stanger89

Did you enter your license key the new way:
http://forums.sagetv.com/forums/show...&postcount=177

Yes, I thought of that. I had guide data out 12 days. Since using the updated jar method it should not matter. It was not all programs but many.

[MrD]

Be careful with recordings.... (i.e. have a backup if you care).

An enforce limit bug (or the fixing of the bug) in a Sage v7 or Sage v9 causes Sage v9 to delete 90% of my Daily Show recordings.

[jm9843]

Originally Posted by MrD

Be careful with recordings.... (i.e. have a backup if you care).

An enforce limit bug (or the fixing of the bug) in a Sage v7 or Sage v9 causes Sage v9 to delete 90% of my Daily Show recordings.

This is somewhat alarming. Has anyone else seen this or believe that it's something to be concerned with?

[Monedeath]

Of note so far in use experience here:

EPG data is presenting some strange results in v9.

It seems every actor/actress listed as being present in a given program(example is from Falling Skies) were playing the role of the same character when viewing program details. Issue is present on new and old recordings alike.

I'm guessing this has to do with V9 not "elegantly" handling the lack of data that the GoogleEPG is providing to V8 users.

Also of note, the Recording Scheduler seems to not have a memory between system restarts. We're not seeing any upcoming scheduled recordings displaying on SageTV until (more than) a few minutes (depending on settings for look ahead) after the Server comes back online, making me think it has to rebuild the recording schedule upon restart. Not sure if that is working as intended or not, but thought I'd mention it.

[Monedeath]

Originally Posted by jm9843

This is somewhat alarming. Has anyone else seen this or believe that it's something to be concerned with?

The first time I tried to do the upgrade, it completely wiped out the wiz.bin and reimported everything into the archives. Reverted it and tried again, recordings made it through that time, took about another 12 to 16 hours before all of the tuners started working properly again, on their own.

[Denali]

Originally Posted by Monedeath

It seems every actor/actress listed as being present in a given program(example is from Falling Skies) were playing the role of the same character when viewing program details. Issue is present on new and old recordings alike.

I'm guessing this has to do with V9 not "elegantly" handling the lack of data that the GoogleEPG is providing to V8 users.

Same as I noted in post #5

[wnjj]

Originally Posted by Monedeath

Of note so far in use experience here:

EPG data is presenting some strange results in v9.

It seems every actor/actress listed as being present in a given program(example is from Falling Skies) were playing the role of the same character when viewing program details. Issue is present on new and old recordings alike.

V9 lets you dump the wiz.bin file to an ASCII file (dump_db_on_startup=true). Maybe a look at that will reveal if it's a DB corruption but it's likely a bug in code that got modified for OS.

[SHS]

Originally Posted by Monedeath

The first time I tried to do the upgrade, it completely wiped out the wiz.bin and reimported everything into the archives. Reverted it and tried again, recordings made it through that time, took about another 12 to 16 hours before all of the tuners started working properly again, on their own.

It most like just a bug I see the same thing as well

[sacrament055]

Not sure if this is related but I thought I'd mention it here. I have 5 ATSC tuners and I have Merit set to prefer my higher quality tuners and that has been working as far as I know until I moved to the new sage 9 jar.

Not quite sure if the Merit is not opposite (lower number is preferred) or if it's random but I keep seeing it pick a tuner that has Merit of 0 instead of a tuner that has Merit of 7 when there's nothing else recording.

[wnjj]

I think I figured out the Actor/Character repeating issue.

There were new fields added to the "Person" table for wiz.bin version 0x4F and above. My 7.1.9 version was using 0x4B and V9 is 0x55.

    if (ver >= 0x4F)
    {
      Wizard wiz = Wizard.getInstance();
      extID = in.readInt();
      .
      .
      .

The extID field is used to match actors to their roles in SeriesInfo.java:

  public String getCharacterForActor(Person actor)
  {
    if (actor == null) return "";
    for (int i = 0; i < people.length; i++)
    {
      // Resolve aliases as well so they match
      if (Math.abs(people[i].extID) == Math.abs(actor.extID))
        return characters[i];
    }
    return "";
  }

The issue is when the V7 db upgrades to V9, all of the actors have an extID of 0. So when the match takes place, the first actor in the DB matches the ID of the actor in the show. So what's needed is if the actor extID is 0, fall back to the other string search "guessCharacterForActor" instead:

  public String getCharacterForActor(Person actor)
  {
    if (actor == null) return "";

    if (actor.extID == 0) return guessCharacterForActor(actor.name);

    for (int i = 0; i < people.length; i++)
    {
      // Resolve aliases as well so they match
      if (Math.abs(people[i].extID) == Math.abs(actor.extID))
        return characters[i];
    }
    return "";
  }

[Denali]

Why is the in.readInt() returning 0 on the conversion and not the version 7 extID?

[wnjj]

Originally Posted by Denali

Why is the in.readInt() returning 0 on the conversion and not the version 7 extID?

The ver variable is read from the DB file so in.readInt() isn't called when reading the V7 db. Then the default of 0 is written when it gets saved. I'm assuming some extID's get fitted with the correct values over time.