Ah, drat. Posted too soon: I have "fixed it"! On the other hand, maybe others can profit from this solution:
What I had overlooked: There appears to be one case where a decimal number has less than 10 decimal digits, and that's when that decimal number is 0.5. (I'm worrying a bit that there might be other exceptions, but I haven't found any in my files).
So, the following solution worked for me, allowing me to open the project successfully:
Using a decent text editor (one that supports regular expressions with lookahead assertions, for example EditPadPro or UltraEdit (when setting it to Perl regex mode), search for
and replace all with a single dot (.)
This regex searches for a comma that is either followed by another comma, an opening angle bracket, a decimal fraction of at least 10 digits, or the number 5 (but only if that comma is preceded by the single digit 0).
This allows me to open the project again. However, as soon as I save it again, the file gets corrupted again.
Interestingly (and possibly related), when I try to open the (repaired) file, a PE information window appears ("PE is updating a component. Information is being transmitted..." or something like that in German) and a Windows 7 UAC dialog pops up, asking me to allow the Windows Regserver to modify my system. It doesn't matter whether I allow or deny that request (which appears twice in succession, by the way), as soon as I save the file again, it's corrupted.
The commands that are asked to be executed are:
C:\Windows\System32\regsvr32.exe /s "C:\Program Files\Adobe\Adobe Premiere Elements 10\mc_dec_mpa_ds.ax" "C:\Program Files\Adobe\Adobe Premiere Elements 10\mc_dec_mp2v_ds.ax"
C:\Windows\SysWOW64\regsvr32.exe /s "C:\Program Files\Adobe\Adobe Premiere Elements 10\32\mc_dec_mpa_ds.ax" "C:\Program Files\Adobe\Adobe Premiere Elements 10\32\mc_dec_mp2v_ds.ax"
But at least I can now re-open that file after "fixing" it.
Still it would be nice if Adobe could fix this problem. Is this the right place where Adobe technicians will read it and act on it, or do I have to do something else?
Some system information: Windows 7 Pro 64bit with all current patches, 64-version of PE 10.0 installed.
We're just fellow users on this forum, not programmers.
So it might be easier if you just telling what you were doing with which format of video and then what happened.
All that code might as well be hieroglyphics to most of us!
thanks for the info - the forum thread I linked to above gave me the impression that at least some Adobe employees (e. g. a helpful fellow with the nick PRE_help) frequent this forum.
I hadn't been doing anything fancy - just putting some clips from my EOS 5D Mark II together, trimming them a bit, playing a bit with the audio levels and adding a couple of soft fades between clips, then applying the "Broadway" DVD menu scheme to it and editing the button names and keyframes on that.
But the corrupted .prel files I'm seeing are definitely the result of a localization bug.
There are a few Adobe employees, who drop by, from time to time. However, the frequency of their visits is variable - we might see three in a day, or go a week, with no employee interaction.
I would guess that right now, most are involved in the development of PrE 11, which will likely be released in Sept-Oct of 2012. Some might "take a break," and read/respond to some threads, especially if they suspect that they might be useful to the on-going development of PrE 11. Remember, however, that is but a guess on my part.