[Yannick Schillinger]

Hi Daniela,

i opened the project file in a text editor and manually replaced all the instances where the periods had been mixed up.
The file is in XML format and the occurences follow certain patterns. Many of these patterns can also be replaced automatically by using regular expressions, i found an example on another site.
But still, it can be a lot of work, and you might be better off starting your project from scratch. To avoid this error in the future, you should set your regional settings to use period (.) as the decimal symbol, while using Premiere Pro.
If you need more information, i can take a look at it again.

Yannick

[Yannick Schillinger]

Hi,
thanks for the answer. It turned out that Premiere Pro had messed up the project file by replacing periods with commas in keyframe values (a known issue, ref. https://premierepro.wikia.com/wiki/Error:Keyframe.h-138 ).
In the end I managed to fix it manually, although it was lots of tedious work (still less than recreating my work from scratch).
I’m surprised this software has such a serious bug which hasn’t been fixed, though existing since version 2.0 (at least according to the wiki).