• Welcome to the Pipe Organ Forum! This is a part of the open community Magle International Music Forums focused on pipe organs (also known as "church organs"), organists, organ music and related topics.

    This forum is intended to be a friendly place where technically advanced organists and beginners (or even non-organists) can feel comfortable having discussions and asking questions. We learn by reading and asking questions, and it is hoped that the beginners (or non-organists) will feel free to ask even the simplest questions, and that the more advanced organists will patiently answer these questions. On the other hand, we encourage complex, technical discussions of technique, music, organ-building, etc. The opinions and observations of a diverse group of people from around the world should prove to be interesting and stimulating to all of us.

    As pipe organ discussions can sometimes become lively, it should be pointed out that this is an open forum. Statements made here are the opinion of the poster, and not necessarily that of the forum itself, its administrator, or its moderators.

    In order to post a new topic - or reply to existing ones - you may join and become a member by clicking on Register New User. It's completely free and only requires a working email address (in order to confirm your registration - it will never be given away!). We strive to make this a friendly and informative forum for anyone interested in pipe organs and organ music.

    (Note: If you wish to link to and promote your own website please read this thread first.)

    Many kind regards
    smile.gif

    Frederik Magle
    Administrator

    Krummhorn
    Co-Administrator

Number 0,000000 contains locale dependent floating point warning

erikds

New member
Loading Palo's Pitea dispo in rev 1257 i get plenty of warnings such as:

Number 0,000000 contains locale dependent floating point
Number 100,000000 contains locale dependent floating point
Number 200,000000 contains locale dependent floating point

What does it mean and how can i correct this?

Also i get errors such as:

Duplicate combination entry TremulantNumber002 in General002
Duplicate combination entry TremulantNumber002 in General003
Duplicate combination entry TremulantNumber002 in General004
Duplicate combination entry TremulantNumber002 in General005
Duplicate combination entry TremulantNumber002 in General006
Duplicate combination entry TremulantNumber002 in General007
Duplicate combination entry TremulantNumber002 in General008
Duplicate combination entry TremulantNumber002 in General009
Duplicate combination entry TremulantNumber002 in General010

How can i correct this?

Where can i find more info about the disposition file syntax rules to be respected to avoid warnings and errors?

Thanks in advance.

Erik.
 
Last edited:

wehtam721

New member
The floating point error stems from the fact that some regions use a period as the decimal place separator while others use a comma. I believe that GrandOrgue is using a period now as the standard (correct me here if I'm wrong).

The tremulant errors come from having the same tremulant referenced twice in each of the generals. If you look closely at the definition of the generals, they say:

TremulantNumber001=-001
TremulantNumber002=-001

So, the generals are being told that their are two tremulants, but both trem references point to the same tremulant object. They should point to two distinct tremulant objects. It should read:

TremulantNumber001=-001
TremulantNumber002=-002

Making that change should take care of the majority of the problems that you're having.

On SourceForge, in the Files -> Testing folder there's a PDF which gives lots of specifics about how the ODF should be written. It's not completely up to date (as GrandOrgue is changing constantly :) ), but I've found that it's a really good starting place for figuring things out.


I hope that this helps!

Take care,
Matt
 

L.Palo

New member
Hi!

The first issue with locale dependent comma separator is easily fixed just by saving the organ again (then all decimal commas in the .cmb file you have on your computer will be replaced with periods instead).

There are some other lines that need fixing too, unfortunately I've not had the time to fix them all yet but I'll try to prioritize it and upload fixed odfs for the problematic samplesets.

Kind regards

Lars P
 

e9925248

New member
On SourceForge, in the Files -> Testing folder there's a PDF which gives lots of specifics about how the ODF should be written. It's not completely up to date (as GrandOrgue is changing constantly :) ), but I've found that it's a really good starting place for figuring things out.
The up to date version of the reference is shipped with GO in its help.
 

erikds

New member
Thanks Matt for pointing out the reasons for the error or warning messages.
Thanks Palo for the updated odf.
Thanks Martin for pointing me to the help file, but above all for all your efforts to develop GO.

I have now Pitea loading as Palo stated without any error or warning showing up.
But loading Palo's most recent odf did not eliminate the huge amount of warnings nor the errors i reported earlier.
The odf did load after several minutes however as before, but still showing a huge amount of primarily warning messages.
To get rid of them i have in Windows to change the keyboard layout it uses from Belgian-comma to Belgian-point.
The revisions up to rev 1226 did not result in massive warnings, but since rev 1240 it happens.
Is there really a need for GO to be so picky about which decimal character Windows is set to use?

Anyway, Pitea now loads ok.

All the best.

Erik
 

L.Palo

New member
Did you save the organ again after loading? That should "correct" the decimal commas that already exist in your .cmb file, if it doesn't it's a GO bug that we must investigate.

Are you referring to another odf by me? I know I'm a bit behind updating them (I'm unfortunately a bit busy with many other things too...) but the new Kalvträsk Church and the newly updated Piteå MHS should load without any warnings. The others I must check again if I've fixed only here and not uploaded...

Kind regards

Lars P
 

e9925248

New member
To get rid of them i have in Windows to change the keyboard layout it uses from Belgian-comma to Belgian-point.

For GO 1240 or latter, changing any locale option (including the keyboard layout) should not result in any change in the ODF/CMB parsing.

Did you press save and missattribute the behaviour change to the keyboard layout change? If you can prove, that the keyboard layout affects the GO behaviour, you probably have discovered a new bug.
 
Last edited:

erikds

New member
Did you save the organ again after loading? That should "correct" the decimal commas that already exist in your .cmb file, if it doesn't it's a GO bug that we must investigate.

Are you referring to another odf by me? I know I'm a bit behind updating them (I'm unfortunately a bit busy with many other things too...) but the new Kalvträsk Church and the newly updated Piteå MHS should load without any warnings. The others I must check again if I've fixed only here and not uploaded...

Kind regards

Lars P

Hello Lars,

http://www.familjenpalo.se/sites/default/files/sampleset/Kalvtrask_Church.rar

and

http://www.familjenpalo.se/sites/default/files/sampleset/Patch_BureaChoir_ODFs.7z

are loaded without any error message, as you stated.
The "messages" window does not even show up.
The selection of the keyboard in Windows 7 (komma or point) is of no influence as Martin indicated.

So these 2 dispositions are fully up to date.

Other ones i still have to check, but shall report as soon as this is done.

All the best.

Erik.
 

erikds

New member
For GO 1240 or latter, changing any locale option (including the keyboard layout) should not result in any change in the ODF/CMB parsing.

Did you press save and missattribute the behaviour change to the keyboard layout change? If you can prove, that the keyboard layout affects the GO behaviour, you probably have discovered a new bug.

Hello Martin,

I don't think there is a bug involved.
Anyway i cannot reproduce what happened and do not see any impact now from changing the keyboard layout.

All the best.

Erik
 
Last edited:

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Hi everyone,

Long time since my last post in this sub forum , but I've been busy too updating all my custom and free downloaded sets.....

Here I just replaced the , with a . and no warning about locale dependent stuff.

I'm running 1261 x64 and it's a KILLER version. Log helps me a lot to correct and now I'm Ok to know what should I type on odf.
I'm starting re-writing odf files from the beginning in some cases, I think will be better to get the odf right from the start.
I also did my homework reading the "manual" - help file which has many an info inside.

Saving the set was a solution too in some cases where nothing else worked.

Also I have found that is better to create the ranks first and then the stops.

If we want to know which stop is which I found that this is working fine :

NumberOfStops=2
; Principal 8'
Stop001=001
;Prestant 4'
Stop001=002

Instead of Stop001=001 ; Principal 8' (which brings log message) as we find it in many odf files

No HW1 version, no highest format load samples, no comments, no unused stuff... it's better this way in new GO, I vote for this even if I have tons of work to do updating texts...

It's big fun
Panos

PS. @ Lars : thanks for updated PiteaMHS odf ! I was about to upload one later this week :)
 
Top