Posted
I do want also work with Mulab..but the developer Jo says that it not support a GM Init Function
That means the HN2 cannot adress the right General Midi sounds for playing the accompaniment ?
Direct adressing the accompaniment sound is also not possible, because the sounds will differ on the midi channels
What works for one accompaniment will not work for a another
So i am stuck now with Mulab..oh that is a pity
I try to convince the developer for adding this GM Init function to add to Mulab ( i don't know if it is difficult and how much work it will cost? ) the dataformat seems to be different than he used to be is
Thu, 2011-06-30 - 22:28 Permalink
HN2 can address any sound you can imagine. All you need to do is create a device description and add tell HN2 where to find and how to select it.
What works for one accompaniment will not work for a another
With direct addressing, yes. Don't use it for accompaniments. Instead create a device description with at least a few generic sounds:
- Piano
- Bass
- Guitar
- Strings/Chords
- Drum Kit
- Synth bass
Then you will no more have to select any sound for any accompaniment.
Fri, 2011-07-01 - 23:48 Permalink
:? Seems to me impossible
example
: accompaniment 1 : Band1 : Fills sound on track 3
: ,, 2 : Studio 64 : Offs sound on track 4
Then you will no more have to select any sound for any accompaniment.
These 2 sounds are not included in the generic setup , but exists in the accompaniment
HN2 nows for "Fills" and "Off"s sounddescription than what sound to choose ?
It means also that the Fills and Off sounds in a random Vsti must be exist ?
Crazy...
I can see only possibility all different than the soundnames here below in the accompaniment belong to one of these sounds too
E.g Fills is a pianosound ...
- Piano
- Bass
- Guitar
- Strings/Chords
- Drum Kit
- Synth bass
The accompaniments instruments are based on ....General Midi i think ?
--------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------
Well
But as i noticed that is the pain here ..Bandstand is outdated and not sold anymore
I will look at the Kontakt player
As test i use the simpel hypercanvas module, but not a ricght soundallocation ?
Perhaps it has still to do with Mulab ? or with Vsti hypercanvas ?
Two uncertain issues... so i must use a another DAW than Mulab what is supported by Cognitone and try there the hypercanvasmodule
Later i can use a another soundmodule with modern midi management
Instead of addressing a particular MIDI port and channel, the instruments in a song use a description of the sound they wish to play.
The sound manager will lookup an appropriate sound automatically, reserve a MIDI channel for it and select it when needed. If it can't fnd the original sound, it will look for a suitable replacement that best matches the description.
Let me find out what DAWs are supported...
==============================
It is a dead end this VSti soundmodule i think,..
To analyse this i must know exactl how the Midi protocol works
Parameter control via MIDI |
Most of the parameters that can be set from the panel of this software can be edited using MIDI control changes and RPN (Registered Parameter Number) or NRPN (Non-Registered Parameter Number) messages.
- Parameters shown here in blue are parameters defined by GM2 (General MIDI 2). These parameters will change in response to GM2-compatible MIDI messages.
- MIDI messages shown here in green are used only for Hyper Canvas. Since the VST instruments cannot use exclusive messages, some of the functions defined by General MIDI 2 are assigned to NRPNs to be used with the Hyper Canvas.
- References to [CC#(number)] indicate control change numbers.
- References to [RPN (number)] indicate the MSB/LSB of the RPN that can be used to control the corresponding parameter.
- References to [NRPN (number)] indicate the MSB/LSB of the NRPN that can be used to control the corresponding parameter.
For details, refer to the MIDI implementation