Ok, let’s start with some links, so you know what this is all about.
Some years ago I wrote an article about the 432Hz tuning and how to calculate musical tuning data, based on planetary orbital frequencies.
There is a comprehensive collection of the planet tunings on Planetware.
The 432 Hz tuning example, based on the Earth Year orbit.
YouTube Search Queries:
The Cosmic Octave
As you can see, there is lots of material online.
If you have any particular questions, please ask.
I programmed the tuning calculator, which is only available for Mac right now.
I am a media designer and not a full-on programmer, so it took me some time to manifest the tool and that is why I don’t have other versions for other platforms.
I also have a concept ready on how to implement these ideas into a synthesizer and more.
It is a big thing and there is a lot to explain.
Tempo should be on the top level available and not only in a sequencer.
Tempo is the heart of sound creation. Time is the very core and effects like Arpeggio, Delay, Tremolo, LFO are for example time dependent effects. How can one set this properly, if there is no general tempo defined?
So, Tempo is an essential setting even if one doesn’t use the sequencer.
Sound modulation is often time dependant and has SYNC functionality, which means it takes the timecode from the overall defined tempo.
Tempo and Tuning are of high importance and both parameters should be in a sort of master section.
In my case, I would create templates for each planet tuning, which has a precise tempo and tuning to it. Those two need to be together.
The momentary solution to set the tuning in the MIDI section via webconfig and the tempo in a sequencer is not straight forward for a good workflow.
Before I start making music, I always set my tempo and the tuning first.