It is currently Thu Apr 18, 2024 4:30 pm


Use of CODM with exact pitch noise samples

Using the CODM to create your own organ definitions, exchange CODM organ definitions, ...
  • Author
  • Message
Offline

WmHurt

Member

  • Posts: 65
  • Joined: Mon Dec 13, 2004 1:00 pm
  • Location: Seattle, Washington, USA

Use of CODM with exact pitch noise samples

PostSun Jan 06, 2008 5:59 am

The St. Maximim sample set by sonusparadisi has keyboard action noise samples whose pitch is specified by <Pitch_SpecificationMethodCode>4 and a <Pitch_ExactSamplePitch>100, which, according to the documention, specifies the exact pitch in Hz. All of the noise samples for a keyboard have the same specified frequency. This is all specified in the published organ definition file.

Can one set up the CODM to make use of these? At the moment there seems not to be an associated InstallationPackageDefinition file associated with these.

Has anyone tried this with this or other similar sample sets?
Offline
User avatar

mdyde

Moderator

  • Posts: 15475
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

PostSun Jan 06, 2008 7:32 am

Hello Bill,

Have a look at the Hauptwerk v3 ExampleCustomOrgan2.CustomOrgan.Hauptwerk.xml and ExampleCustomOrgan6-StAnnes-WithAllFrills.CustomOrgan.Hauptwerk.xml files for examples of how to use action noises. Basically you just need to cheat by telling Hauptwerk that the files are tuned to A- 440/equal at a given rank pitch (e.g. 8') and tell it to play them back at that rank pitch (e.g. 8'). Then no real-time re-pitching will occur.

See also the section on action noises in the CODM user's guide.

You might also need to rename the files to the CODM filename format (036-C.wav etc.). First copy them into an 800000-899999 range installation package of your own if you want to edit/rename them.

At the moment there seems not to be an associated InstallationPackageDefinition file associated with these.


That's not actually possible - a sample can only be referenced via an installation package (See the Sample table in full-format ODF). However, they don't necessarily have to be listed in the package definition file (not a strict requirement for CODM use).
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.

Return to Custom Organ Design Module (CODM)

Who is online

Users browsing this forum: No registered users and 0 guests