GO for Windows 32/64

[CatOrg]

Speaking of minimum configuration

I installed GO 0.3 but it just doesnt work as it should. Blocking, slow, noises and other problems. Reading here I suppose my Computer doesnt follow:

Laptop Fujitsu-Siemens Amilo 1650G
Processor Sempron 3400+
2 GB RAM
WinXP-Home 2002 SP3
Asio4all installed

MyOrgan works fine with some VPOs (with the big BureaXtended too), and/but I had already problems with GO 0.2 (dont remember which it was).

Is my computer too old?
What would be the minimum to run GO 0.3?

And btw: will come a Linux GO 0.3?

Thanks in advance

 

[e9925248]

@ Ghekorg7:
1) 16 bit only is just DS. GO supports more backends on Windows.
2) GO support directly recording 24 bit wav files too.
3) Dither (http://en.wikipedia.org/wiki/Dither#Digital_audio) is only present in the PA backends and seems to be disabled in the PA ASIO backend.

 

[e9925248]

@CatOrg:
I hope, that you mean a current GO 0.3. GO should run on it too, but I can't tell you, what polyphony it can handle.

I already have writting various tips in this thread:
Start with low polyphony (one register), one sound interface and one audio group and try to get the sound stable.
Raise samples per buffer and latency. Use linear interpolation and disable lossless compression.
Concurrency should be about the number of processor cores.
Try the different entries for your sound card in GO.

In regard to Linux support:
Percompiled GO 0.3 is available for linux, but the binaries are only rarely updated. In contrast to Windows, compiling (as packages) on Linux is easy.

 

[Mathbob]

Just downloaded V0.3/32 from sourceforge this morning. Really impressed! I especially like the ability to alter configuration file setting from the screen. But one large problem. All of my V0.2 files seem to load OK, manuals, stops & swells are working properly. But on every note, the sound is punctuated by a rapid, loud clicking. Happens on all notes, all stops, all organs (eg Berea chapel - small, loads quickly so a good test organ - but I have tried larger with same result), so I assume it's an audio setup problem. Fortunately, I left V0.2 installed and it still works properly. I tried to compare the audio setups between the two, and they match as far as they can, but V0.3 has many more settings. I know you may need more info, but for starters, it's on a 3GHz,2Gb dedicated PC, MAudio Delta 5.10, Windows XP prof 5.126. There are new settings on V0.3 for latency, concurrency, etc that I have no clue about. I've read earlier posts in this thread, but still stuck. Help?

Later same day:
Additional clue: I've tried changing just about everything - polyphony very low (4); adjusted lossless compression, concurrency, interpolation, looping, etc - no noticeable effect. BUT I did discover one thing: the lower "samples per buffer" is set, the faster the clicking. At 64 it is much faster than at 1024. The number of keys depressed and the number of stops drawn seems to have no effect.

Thanks, Bob

 

[erikds]

@e9925248

Hello Martin,

I read on the German GrandOrgue forum that there is progress made with multichannel.
I have downloaded and installed the setup_GrandOrgue_0_3_0_5_TDM64.win64.970.exe.
I have set up 3 audio groups with the PiteaMHS sample set as reported earlier.

I can now set concurrency and release concurrency levels at 4, corresponding to the 4 cores in my processor (Q6600).
Samples per buffer still needs to be set (relatively) high, minimum at 768, inorder to avoid sound breakup. This does not seem to result in higher latency.
The timing of actually saving the new settings remains very critical as reported earlier.
I have to wait till really minimum processor load and then click the OK button; otherwise i have distorded sound from one keyboard only.
If i remember correctly, you indicated that this could have something to do with the way Windows 7 handles writing to memory.

Anything in particular you want me to test ?

Thanks for your work.

All the best.

Erik.

 

[Mathbob]

I resolved this. By clicking on the audio driver and clicking advanced (or properties or something, I've forgotten), you can set the latency. Making this somewhat longer worked. It seems to be fairly sensitive, just a notch or two too low and it won't work. Is there any problem with having it set too high?

I'm still adjusting other things. For one, the audio level is very high - I have it set on -10 to avoid overdriving the sound board.

 

[CatOrg]

@CatOrg:
... a current GO 0.3. GO -> Yes the last build

I already have writting various tips in this thread:
Start with low polyphony (one register), one sound interface and one audio group and try to get the sound stable. -> No effect
Raise samples per buffer and latency. Use linear interpolation and disable lossless compression.
Concurrency should be about the number of processor cores.
Try the different entries for your sound card in GO.

@ e9925248

Build version? -> Yes the last build

... polyphony ... sound interface ... -> No effect

Just giving some out-of-tune techno-sounds out of itself.

I raised the latency (thanks 2 Mathbob) to 30ms then with a mix of techno and organ sound. At 60ms it works finally. Stiehr-Mockers extended is working even better than in MyOrgan, but I cant load the Burea-xtended that I could run in MyOrgan.

Temperaments needs improvements. Some major-chords become suddenly minor, but on different notes (Do 3 and Si 3, but Do 4 and Si 2 are fine - speaking of Werckmeister).

The new features are impressive. Thanks for that anyway.

 

[Ghekorg7 (Ret)]

Hi Cat and friends

To be able to use Temperaments correctly the wav files must have pitch information embedded, also to type the relevant HarmonicNumber= in odf
For example HarmonicNumber=8 for 8' Ranks 16 for 4' ranks ect .
Mixtures are more complicated, just need some more time spent per octave.

Wait for me I'll upload asap an .organ file for all to see how things is done in the new GO

Best
Panos

 

[JLD]

To avoid mis-tuning when using temperament with an organ which has not been created for more recent versions of GO, if this organ is tuned to concert pitch with equal temperament which is the case for most former HW1 type organs, check the option to ignore tuning from organ samples in the Audio/Organ menu.

To use temperament with organs that are not at concert pitch and not at equal temperament, you not only need to set the harmonic number for the stop, like Panos suggested, but you also need to have the pitch of the sample correctly documented in the wav file.

JL

 

[Ghekorg7 (Ret)]

Hi JLD,
Yes, I also posted about pitch info in wav.

Our friend's Lars' LoopAuditioneer can write such info as far as I'm aware of. So the simple thing to do with a HW1 type is to open wav in LA and resave...
Also I found out that Jiri's old HW1 Smecno set (16/44100) has pitch info inside (I think...) because it works in GO3 temperaments !

 

[e9925248]

I raised the latency (thanks 2 Mathbob) to 30ms then with a mix of techno and organ sound. At 60ms it works finally. Stiehr-Mockers extended is working even better than in MyOrgan, but I cant load the Burea-xtended that I could run in MyOrgan.

1) Is the Samples per Buffer setting the highest number?
2) What is the load error?

 

[CatOrg]

dfg

Dear e9925248

- Samples per Buffer setting: 320
- Load error what out of memory, even for very little organs. Now (with the latency set to 60 (dont find that again, where is it?) is fine I repeat. I also set realtime priority for GrandOrgue in the system.

I have some wishes for enhancement too
- re-able the shift-key. In PiteaMHS, I can only set memory with the set-button on screen, shift doesnt work
- possibility to determinate (in odf) the number of steps of the swell box(es) on screen. I swell throught a script for Keyboard (connected to a diy-pedal), that clicks pixel for pixel to swell up or down, but 15 steps all-inclusive is not enough. I set more pixels in the odf, it works, but the effective swell-area stays at 15 pixels.
- And of course routing the output (or does it work, for now I have obnly one stereo soundboard?) in different channels for the differents keyboards.
- publish somewhere the new definitions for the odf. The Taskin-Pedal doesnt open anymore (Out of range value Label001/positiony) I can modify it somehow (I removed all labels), but better if syntax changes are documented.

Anyway, thanks again!

 

[e9925248]

- Samples per Buffer setting: 320
- Load error what out of memory, even for very little organs. Now (with the latency set to 60 (dont find that again, where is it?) is fine I repeat. I also set realtime priority for GrandOrgue in the system.

The current default for samples per buffer is 1024 as this is the less problematic value. In my option, this setting is even more important than the latency setting.

Load errors were the PoolAlloc errors in older GO versions (which shouldn't be present in current versions any more)? Or just the memory pool full warning?

- re-able the shift-key. In PiteaMHS, I can only set memory with the set-button on screen, shift doesnt work
- possibility to determinate (in odf) the number of steps of the swell box(es) on screen. I swell throught a script for Keyboard (connected to a diy-pedal), that clicks pixel for pixel to swell up or down, but 15 steps all-inclusive is not enough. I set more pixels in the odf, it works, but the effective swell-area stays at 15 pixels.
- And of course routing the output (or does it work, for now I have obnly one stereo soundboard?) in different channels for the differents keyboards.
- publish somewhere the new definitions for the odf. The Taskin-Pedal doesnt open anymore (Out of range value Label001/positiony) I can modify it somehow (I removed all labels), but better if syntax changes are documented.

1) Shift + another key works for the moment
2) The number of pixels to click on is dependend on the enclosure size. You can change the default layout with various options. I noticed that the mouse axis specification is currently broken (will be fixed shortly) - this would allow even more control.
3) The current state is already covered in older posts in this forum.
4) The ODF specification is part of the help.

 

[e9925248]

2) The number of pixels to click on is dependend on the enclosure size. You can change the default layout with various options. I noticed that the mouse axis specification is currently broken (will be fixed shortly) - this would allow even more control.

New build with a fixed mouse axis setting is available in the SF.net project.

 

[JLD]

Windows build (989) are available on SourceForge with all latest fixes from e9925248.

Win64: http://sourceforge.net/projects/ourorgan/files/Development releases/Windows 64 build/setup_GrandOrgue_0_3_0_5_TDM64.win64.989.exe/download
Win 32 (recent processors with sse3): http://sourceforge.net/projects/ourorgan/files/Development releases/Windows 32 build/setup_GrandOrgue_0_3_0_5_TDM64.win32.989.exe/download
Win 32 (older processors without sse3): http://sourceforge.net/projects/ourorgan/files/Development releases/Windows 32 build/setup_GrandOrgue_0_3_0_5_TDM64.win32.no_sse3.989.exe/download

I believe they fix all reported problems!

JLD

 

[JayR]

Still getting a pool allocation error at load with a 1.5GB ODF. Once I click OK on the error message, GO works fine. Just letting you know...

Thanks!
Jay

 

[e9925248]

Still getting a pool allocation error at load with a 1.5GB ODF. Once I click OK on the error message, GO works fine. Just letting you know...

RAM size? OS Version? Data printed in the Pool Alloc error?

 

[erikds]

Windows build (989) are available on SourceForge with all latest fixes from e9925248.

Win64: http://sourceforge.net/projects/ourorgan/files/Development releases/Windows 64 build/setup_GrandOrgue_0_3_0_5_TDM64.win64.989.exe/download
Win 32 (recent processors with sse3): http://sourceforge.net/projects/ourorgan/files/Development releases/Windows 32 build/setup_GrandOrgue_0_3_0_5_TDM64.win32.989.exe/download
Win 32 (older processors without sse3): http://sourceforge.net/projects/ourorgan/files/Development releases/Windows 32 build/setup_GrandOrgue_0_3_0_5_TDM64.win32.no_sse3.989.exe/download

I believe they fix all reported problems!

JLD

Thanks for this latest version.
Multichannel now works without any problem.
No poolalloc error here.
Snappy response to notes played on midi keyboards, with samples per buffer set to 1024.


All the best.

Erik.

 

[JayR]

RAM - 2GB
CPU - P4 2.8GHz
Windows XP SP3
Memory Pool is full - 1484128256 of 1484128256 used.

 

[e9925248]

Multichannel now works without any problem.

GO multi sound card support has not seen any changes in the last weeks.