Announcement

Collapse
No announcement yet.

Composite Sample Set

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    May I ask what software you use to create composite sample?

    Comment


    • #17
      The organ definition file (ODF) used by GrandOrgue is a text file. So I didn't use any specialized software to create the ODF.

      The ODF is structured and is composed of several different elements, e.g., organ, manuals, windchests, tremulants, couplers, stops, ranks, etc. I have several different templates that I use. I start with a basic template containing thee manuals, pedals, approximately 25 stops, and standard couplers. Since my console only has two manuals, one of the manuals is a "floating" manual, and I have set up couplers which allow me to couple the floating division to either manual, or replace the ODF manual assigned to a keyboard.

      I have also written some quick and dirty python scripts to help me create the rank objects. Depending on the samples, there can be several attacks and/or releases for each pipe, as well as tremmed samples with attacks and releases. One of the sample sets I use has 17 lines for each pipe. The ODF consists of over 30,000 lines. Using templates, its possible to create the rank objects using global search and replace in a text editor, but it is pretty tedious. I use the python scripts to set up the rank objects in batches.

      Comment


      • #18
        I tried odf file once but did not understand what to put where

        Comment


        • #19
          Johnallen, you can look at the ODF for the demo organ that downloads with GrandOrgue. There is also a help file. In my case, I had to experiment quite a bit to see the effect of changes that I made in the ODF. It's a bit like hacking. But eventually, if you refer to a well made ODF along with the help file, it makes sense.

          Comment


          • #20
            Is Grandorgur odf easier than Hauptwerk odf?

            Comment


            • #21
              I haven't worked with HW ODFs. They are in XML format. I've looked at a couple in order to check release keypress timing and I haven't been able to parse them. The GrandOrgue ODF is a structured text file.

              I believe HW sells a program which allows a user to manipulate the ODF but I don't know anything about it. There are probably others here who can provide more info.

              Comment


              • #22
                HW has a "simple" XML format for building (Custom Organ Design Module) as well as the full featured format. The full format can be "compressed" (options are named a, b, c, d, e, ....) or with readable option names. The format is structured like a relational database with numerical primary keys and references to them.

                CODM documentation is available on their web page - I have heard rumors, that the full format documentation is only available at request under special conditions.

                A GO ODF can be a HW1 format [some options are reported as unused] and you can start using newer GO features for just the situations, where you need more features (eg. multiple releases, graphics, ..).

                Comment


                • #23
                  Originally posted by e9925248 View Post
                  HW has a "simple" XML format for building (Custom Organ Design Module) as well as the full featured format. The full format can be "compressed" (options are named a, b, c, d, e, ....) or with readable option names. The format is structured like a relational database with numerical primary keys and references to them.

                  CODM documentation is available on their web page - I have heard rumors, that the full format documentation is only available at request under special conditions.

                  A GO ODF can be a HW1 format [some options are reported as unused] and you can start using newer GO features for just the situations, where you need more features (eg. multiple releases, graphics, ..).
                  Thanks for that information. I've been unable to follow the keys in the full format since I don't know the entity relationships. I suppose I could parse it with sufficient patience, but it doesn't seem worth the effort. The only information I've looked for is for maxkeypresstimes.

                  The sample sets from Piotr Grabowski don't use the exact same keypresstimes that correspond to the length of the samples denoted by the path names for the releases. I understand that the sample sets from Sonus Paradisi also do not correspond exactly. Since I'm making composite sets from the various free demos from SP, I wanted to see if I could more closely match the value for the maxkeypresstime. As it is now, my sample sets use the exact same values as specified in the paths. I'm not sure if it makes a great deal of difference.

                  Comment

                  Working...
                  X