Open steinj1945 opened 8 years ago
Generation should be plugin based, so that different outputs can be added and supported
I know this would be possible with Ableton and Max for Live but it might be bad to require the user to own expensive software like that. What is the intended audience? Just us?
If possible, it may be something to sell after it gets polished. (Thats a future review)
So for just us, its not important, but laying a foundation to build on to add a more retail audience may be helpful. If it can be modularized and loaded, it should make it easy to interface anything to the core data value output
The Windows.Devices.Midi namespace in the Windows SDK should allow us to easily manipulate MIDI inputs and outputs. For starters, we should be able to output to the cheesy sounding Microsoft GS Wavetable synth. Moving on from there, we could either encourage the user to install a different SountFont or create our own SoundFont. Or, a more robust way would be to create MIDI instruments using Max(by Cycling '74) which should be able to run standalone. Hopefully Max for Live, which would be the most useful to me should include all the tools needed to do that (which I would need to purchase/get 30 day trial)
@steinj1945 , how do you feel about making this a "Universal Windows Application"? That namespace in the SDK is not a class .NET assembly but some new format for Universal apps. I was successfully able to output to the Microsoft GS Wavetable Synth using a sample application from Microsoft which I built and ran. I think the Windows 8.1 SDK probably has that namespace too. Thoughts?
Currently, the proof of concept had MIDI playback on the Microsoft MIDI Mapper, sounding like Generic Piano.
Moving forward, tones and instruments need to be played (such as a kaoss pad, etc).