• 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

New free sampleset for GrandOrgue!

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
I think, that there are better ways to create a PDF version. The help is written in docbook, which supports (customizable) conversions into multiple formats.

To get something editable, my current recommendation is:
Code:
docbook2rtf grandorgue.xml
Package docbook-utils need to be installed (either from any Linux distribution or Cygwin). This results in one RTF document with TOC, only the image import is not working correctly.

To produce directly a PDF, my current recommendation is:
Code:
dblatex grandorgue.xml -o grandorgue.pdf
Package dblatex needs to be installed (Cygwin or any linux distribution).

Both ways use predefined layout templates - the customization of these layout templates is possible.

I'll attach an up to date help generated with dblatex (covering the multi-rank support too).

Hi ,

I'm only on windows.... and I do not want to get involved into a linux/windows build of Cygwin... too much for me, as my main goal is to play music as easy as possible concerning software (far from easy so far..... he he)

So I tried as I could. Your pdf is super ! I like the (at last !!) coloured background examples GO offers !
Thanks for this and for sharing it !

Panos
 

Larioant

New member
I thank those who intervened to help me. Now I am able to build any interface virtual organ (such as HW 4), which is certainly nice to see. I hope that GO will continue to grow.

thank you very much.

Antonio.
 

e9925248

New member
I'm only on windows.... and I do not want to get involved into a linux/windows build of Cygwin... too much for me, as my main goal is to play music as easy as possible concerning software (far from easy so far..... he he)

Cygwin compiles the various *nix software as windows exe programs (using some compatibility DLLs and is a little bit slower).

Cygwin is an easy to use:
You download and start the installer, point it to an install directory with some free space and finally select the software (=packages), you want to install.


If you want to work with the various docbook tools under Windows and don't have any easy to use/install native version, you really should use cygwin.
 

Dell Anderson

New member
Hi all -
My first post here and mainly to say that this Pitea organ is wonderful. I've been playing for two days now and I love it more and more. I had not discovered the help files or larger text panels, so this thread has been quite useful. Thanks so much for the huge amount of work involved. It is really difficult to imagine how much effort has gone into this organ (as well as GO) to make it possible. Bravo!

Dell Anderson
California, USA

PS Thanks also to Panos for creating the PDF - timing is perfect as I will take it on the train with me this afternoon.
 

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Hi Dell, welcome to this super forum !
Indeed one can find serious help from many special people in here.
Also many enjoy-full discussions are regular and lots of fun !

Thanks for your kind feedback, I love this organ too, but still maybe there is something we missed along the way.
So, if you spot anything please post, so Lars, Graham or me can deal with :)

Try e9925248's latest pdf GO manual, as this has more info and especially about the number and the texture of the wooden panels, with example images on !

Best
Panos
 

masi

New member
The following applies to other samplesets also, but, as I am currently looking at the Piteå samples, I am going to ask this question in this thread. Here it is: Descriptions of the WAV file structure at http://www.myjuni.com/xe/MyDoc/57801 or http://www.sonicspot.com/guide/wavefiles.html tell that the start and end fields of the loop data in the smpl chunk are given as byte offsets. So the value of start and end should be a multiple of 4, shouldn't it? But this is not the case. For example the value of the loop start in PiteaMHS/HVCornetV/053-F.wav is 93563, which is not even even :))). Obviously the values are given in frames instead of bytes. Right? Does the WAV specification allow this?

Markus
 

L.Palo

New member
Hi!

Try reading some official documentation on the WAVE format. For instance http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/Docs/RIFFNEW.pdf or similar.

The dwStart and dwEnd of a <sample-loop> does specify samples not any offset in bytes. Nowadays I think that frames are used instead of samples in the terminology to avoid confusion of whether you intend to have all the samples for all existing channels at a certain point or if you just want a single channels data (sample) at a certain spot. In my opinion it's easiest to think of the wave data just as the first channel with it's data laid out in a row (every sample in it's own column) and the possible additional channels as the row(s) beneath the first one...

Anyway, it's certainly possible to have any individual sample (for a mono file) or frame (for multi channel files) as the dwStart and dwEnd, odd or even, and be perfectly standard compliant.

Kind regards

Lars P
 

masi

New member
Thanks for that link, Lars, which will make for an important entry in my bookmarks. Other than the two documents that I referred to (and which seemed as if they could be trusted), this specification of Microsoft does indeed talk of "samples" and does not mention "byte offsets".

Markus
 

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Hi Mathbob, glad you liked.

I did a new .organ file for the positiv small model so it will work with temperaments and other stuff and a Baroque Dorf type version 2m/p.

I'll post the .organ files here for testing.

Best
Panos
 
Top