Impossible to open xml after update

[MikeB]

@ustk I also had this about three weeks ago. David's video - good as it is - didn't help.
The XML were fine.

I then took the XML from my backup - two days before - and it worked again.

[d.healey]

@MikeB said in Impossible to open xml after update:

I then took the XML from my backup - two days before - and it worked again.

So the XMLs weren't fine ;)

[ustk]

@d-healey said in Impossible to open xml after update:

@ustk Did you check both the XMLs?

Yes

@MikeB said in Impossible to open xml after update:

@ustk I also had this about three weeks ago. David's video - good as it is - didn't help.
The XML were fine.

I then took the XML from my backup - two days before - and it worked again.

So have you spotted any discrepancies between the two?

[MikeB]

@ustk @d-healey

But - all tests have no errors in the XML structure or semantics.

The error was in the interpretation.

Lately I have often noticed that the system reports that components are not available although they are there. See screenshot

[d.healey]

@MikeB Is that the name of the project or a script - _Final_33-Test?

[MikeB]

@d-healey Is the name of the project or
the current XML file

[d.healey]

@MikeB Perhaps its related to the setMidPoint error above. Check that you have set the middle position of your sliders to a valid value.

[MikeB]

@d-healey

I have 40 knobs in the project - I have now checked them all - and in fact 2 were set to -1 which is wrong.

Now the error is gone.

Thanks David

[d.healey]

@Christoph-Hart Might be good if that error tells you which component is affected.

[ustk]

@MikeB @d-healey strangely, -1 should be interpreted as a default value not to take into account, but sometimes it does…

[d.healey]

@ustk For the middle position?

[Christoph Hart]

@d-healey yeah I hate that middle position property: -1 is a terrible default value, that‘s why scriptnode uses a skew factor as property which defaults to linear (=1).