The new standard in Digital Virtual Organ technology.
Until you get to the customization and application of graphics phase, no XML, text or other input is required. The tools are designed to generate the disposition from your largely point and click inputs, so you do not have to worry about how it works, how to decipher pages of XML or other code.
The purpose of this tool is to compile the individual folders of ranks containing your samples into an operational sample set, which you can then quickly audition within a matter of minutes!
This tool can be also used on cleaned but yet unlooped samples to give an early indication of how the individual ranks sound, before going through the time consuming process of looping every sample.
This tool takes the form of a "wizard" like interface where you move left to right, setting various parameters as you go, according to the rank types, and then building into a playable sample set. These sample sets are imported into the next tool in the process, which links the ranks and samples to the actual organ disposition and functionality.
An example where a whole Swell division is being imported from prepared samples, and some release parameters are being set.
Reading the sample information, pitch and loop information
After you have completed the setup of the sample set, you can now audition the samples, even using the same convolution reverb system that is features in the main software! This process should take no more than ten minutes to reach the point of being able to audition samples!
We are continually improving this tool and adding more intelligence and features to it. One of these is the ability to drag and drop your own reverb samples from the building so you can get even closer at preview to the final sound.
The purpose of this tool is to instruct the software on how the organ is physically made up, ie its disposition. This software has a sophisticated model behind it, which is made up of lots of small components that know how to be bits of an organ.
An OrganStop knows what a regular organ stop does, so you don't need to teach it. What you do need to do is give it some basic information, such as the stop name, pipe length and so on.
This tool takes the form of a "wizard" like interface where you move left to right, setting various parameters as you go. This starts with information such as how may divisions, manuals, expression pedals and so on, before going on to ask you to fill in the detail of how those divisions are made up, and how they should behave.
Once you have completed the wizard steps, you should have a buildable deployable organ. It will not look pretty but everything should work. Your next job is to make it pretty!
Firstly, setup the basic shape and size of the organ.
Import the individual divisional sample sets created by the previous tool, and create rank definitions. A sample set rank can be used anywhere, more than once and used in any division.
Example, specifying the stops in a swell organ division.
Draft preview using generic stop images of what your stop layout might look like if left on default settings. This is intended as a verification mechanism, and the final appearance of your stops can be totally overriden.
Getting organ ready for build and deployment, or further customization in Microsoft Visual Studio
The disposition builder is designed to get you to the point of having a defined organ without having to touch a single line of code. However, as you have a fantastically powerful fully hardware accelerated graphical user interface technology at your disposal, why not take full advantage!
The user interface is written in XAML aka WPF. It is industry standard and there are many many online resources for training and how to achieve all manner of effects. We will help you get started with this but what we can tell you with complete certainty is the more time you invest honing your skills with customization, the better and slicker your organs will look. There is no getting around the fact XAML does have a learning curve but it is intuitive and not that different to HTML, except it is factorially more powerful and faster.
Ideally a desktop or small form factor desktop computer, dedicated to this purpose if possible.
Windows 10 x64
i5 4th Generation Processor or greater (although users report running successfully on much lower specifications than this)
16Gb RAM (Ideally fastest RAM machine can take)
128Gb Minimum, Hard Drive (Preferably a solid state disk SSD / M2.SSD)
Dedicated sound card (eg SoundBlasterZ) or USB external sound card
** NOTE ** Using our stripped down version of Windows 10, users are reporting significant performance improvements ***
This project is largely driven by user requests and feedback so your views are really important to us.
If you find something not working or you don't like, please come and talk to us first, as the chances are we can probably do something about your issue quickly.
Almost every issue encountered by users so far has had a resolution, so please don't be shy. We are only as good as the feedback we get!!
As this software is under a constant release cycle of regular updates, you may be surprised at how quickly we are able to incorporate all feedback received.
For issues with the software, licensing, or feature requests :-support@digitalVPO.com