Re: [Lmuse-developer] automation issues. Yes there seems to be a problem.

[Tim <ter...@ro...>]

Double D'oh ! My apologies - there appears to be a problem. 
Although I must re-test with localization off, 
 right now I'm German ("," decimal separator), 
 and when I reloaded the saved file from before, 
 behold - all the audio controller values are zero, 
 although none of the events are actually missing,
 and the values are still OK inside the file.
When I now save this file, the .med file shows all zeros stored 
 for the audio controller events, but again, none are missing.
I could have sworn it was working earlier today...

Therefore, there must be a problem not in writing, but in reading.
I will check it out - Thanks a whole bunch for spotting that !

Tim.


On Monday 01 June 2009 15:26:03 Robert Jonsson wrote:
> Hi Tim,
>
> that's kind of wierd, I'm running Kubuntu.
> The evidence points to a localization bug, but probably more subtle than
> last time... and if it works on your system it might not be that big an
> issue.
>
> Are you sure the localization worked, did MusE actually change language in
> the menus et al?
>
>
> I'll append the files (both good and bad), though the only really
> interesting change was the diff I sent.
> Here goes.
>
> /Robert
>
> 2009/6/1 Tim <ter...@ro...>
>
> > Hi, Robert.
> > I just tested with Swedish and German localization.
> > I made sure the decimal separator was set to ","
> >  and then gave it a try.
> > Found no trouble saving and loading. Tried several times.
> > With a short song, and a long song.
> > Checked all of Muse for "%f" usage.
> > None found, except for some insignificant printf debug lines.
> > The audio controller xml writing code uses QT strings, as Werner said.
> > Also, the XML module code uses QT strings to store floats and doubles.
> >
> > Can you send me the original non-localized .med file?
> > Maybe I can spot something from it.
> >
> > Tim.
> >
> > On Sunday 31 May 2009 13:56:40 Robert Jonsson wrote:
> > > I think I just found the root cause why it was not working for me. I'm
> > > running a localized (swedish) desktop since a few weeks and one of the
> > > quirks of swedish localization is that . is ,   e.g: 1.0302   is 1,0302
> > > The reason I thought to test this was that there was a similar bug a
> > > long long time ago where this definitely was the problem.
> > >
> > > I found the fix message from the changelog:
> > >       * changed all float printf("%f") to equivalent qt-string
> > >         routines; dont localize decimal point so that the
> > >         strings can be properly parsed; this should fix some
> > >         save/restore problems in localized MusE versions (ws
> > >
> > > I just diffed two test files where I added three automation points one
> >
> > with
> >
> > > localized muse and one without. Diffing the files reveals this
> >
> > difference:
> > > <         705600 0.0166629,         1058400 1.02164,
> > > ---
> > >
> > > >         0 1.02164,         705600 0.0166629,         1058400 1.02164,
> > >
> > > For some reason the first value is never written to the file when MusE
> > > is localized... this appears to be a somewhat harder nut to crack...
> > > There's always the workaround of not running MusE localized.