Author Topic: 2016.22 Open of current sequence  (Read 2554 times)

Offline worksopian

  • Jr. Member
  • **
  • Posts: 96
    • View Profile
2016.22 Open of current sequence
« on: April 25, 2016, 09:24:44 AM »
I just install 2016.22 and tried to open my one and only sequence and it crashed out almost immediately. I repeated the steps and crashed again.
Fenton, Michigan

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #1 on: April 25, 2016, 10:32:06 AM »
You have several corrupted effect entries in you sequence XML file.  No idea how they could have gotten that way.  For instance this chunk of xml below looks like only partial entries for the "On" effect.

Code: [Select]
    <Effect>E_TEXTCTRL_Eff_On_Start=15</Effect>
    <Effect></Effect>
    <Effect>E_TEXTCTRL_Eff_On_End=15</Effect>
    <Effect>E_TEXTCTRL_Eff_On_Start=0</Effect>
    <Effect>E_TEXTCTRL_Eff_On_End=0</Effect>
    <Effect>E_TEXTCTRL_Eff_On_End=1</Effect>

Offline worksopian

  • Jr. Member
  • **
  • Posts: 96
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #2 on: April 25, 2016, 11:12:55 AM »
I just rolled back to 2016.20 and loaded the same sequence with no issues. Could 2016.22 have corrupted the data?
Fenton, Michigan

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #3 on: April 25, 2016, 12:37:03 PM »
Did you use the sequence file you posted or did you revert to an older saved copy?  If so we need that copy.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #4 on: April 25, 2016, 12:38:56 PM »
If it is that exact same sequence file then it's just that the older version is more resilient to the corrupted effect lines.

Offline dkulp

  • Supporting Member
  • Hero Member
  • *
  • Posts: 812
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #5 on: April 25, 2016, 06:45:43 PM »
You have several corrupted effect entries in you sequence XML file.  No idea how they could have gotten that way.  For instance this chunk of xml below looks like only partial entries for the "On" effect.

Code: [Select]
    <Effect>E_TEXTCTRL_Eff_On_Start=15</Effect>
    <Effect></Effect>
    <Effect>E_TEXTCTRL_Eff_On_End=15</Effect>
    <Effect>E_TEXTCTRL_Eff_On_Start=0</Effect>
    <Effect>E_TEXTCTRL_Eff_On_End=0</Effect>
    <Effect>E_TEXTCTRL_Eff_On_End=1</Effect>


That's exactly what the ON effects should look like.    Non-defaults are no longer written out for many of the effects.
Daniel Kulp
Framingham, MA

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #6 on: April 25, 2016, 07:01:08 PM »
That's exactly what the ON effects should look like.    Non-defaults are no longer written out for many of the effects.

Gotcha....I must have been sleeping when that change was implemented.

Offline worksopian

  • Jr. Member
  • **
  • Posts: 96
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #7 on: April 25, 2016, 07:39:14 PM »
I used the same sequence in both cases.
Fenton, Michigan

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #8 on: April 25, 2016, 08:16:51 PM »
The problem is somehow you ended up with 3 phoneme's on your Spiral Tree model.  If you can show us how to cause that then we can make sure we block that from happening.  Unless you did any manual editing of your XML.  Just deleting those lines fixes the file.

Code: [Select]
<Element type="model" name="Spiral Tree">
      <EffectLayer>
        <Effect ref="11" name="etc" startTime="29150" endTime="29350"/>
        <Effect ref="11" name="AI" id="1" startTime="29350" endTime="29750"/>
        <Effect ref="11" name="MBP" id="2" startTime="29750" endTime="29950"/>
      </EffectLayer>


Offline worksopian

  • Jr. Member
  • **
  • Posts: 96
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #9 on: April 26, 2016, 06:35:02 AM »
Will check that out when i get home tonight, I have been having issues with my Logitech G500 mouse that may be the cause of this.
Fenton, Michigan

Offline worksopian

  • Jr. Member
  • **
  • Posts: 96
    • View Profile
Re: 2016.22 Open of current sequence
« Reply #10 on: April 26, 2016, 05:15:03 PM »
Thanks Gil,
I removed the offending phonemes that I accidentally dropped on the spiral tree and was able to upgrade to 2016.22.
Fenton, Michigan