Hi folks!
I second Phillip here.
Restrictions of this are really bad IMO. GM is a standard, but not
something professionals that need to come as possible as the real thing
relay on, the GM standard is just a simple thing in this regard. One has
to be able to have several levels of open hi-hats, make rolls, be able
to hit drums and cymbals different places and so on - not to mention
virtual instruments. The GM standard is not sufficient when it comes to
triggering virtual drum kits. Adding stuff to the end of the GM standard
will be a truly mess from an end-user perspective.
Jostein
On 2020-04-27 09:41, Philipp Müller via Hydrogen-devel wrote:
Well, I wouldn't restrict the allowed instruments to the list below.
After all Hydrogen is way more than a synthesizer/sequencer for MIDI
and
the GM standard is almost 30 years old. It's certainly a matter of
taste
and music but I prefer having a semi-open hi hat, a rimshot or maybe
even a second snare over a mute triangle, bongos, and a cowbell.
But I'm not into MIDI. What is the pain you are having with respect to
the current implementation? Maybe we can expose (per default but
adjustable by the user) a reduced set complaint with GM based on the
tags. Or make such an exposure optional.
Cheers,
P
On 4/26/20 10:22 PM, muzzol wrote:
My opinion is all kits should use standard GM as reference and if
someone wants to go beyond just add instruments at the end:
Note Drum Sound
==== ==========
B0 Acoustic Bass Drum
C1 Bass Drum 1
C#1 Side Stick
D1 Acoustic Snare
Eb1 Hand Clap
E1 Electric Snare
F1 Low Floor Tom
F#1 Closed Hi Hat
G1 High Floor Tom
Ab1 Pedal Hi-Hat
A1 Low Tom
Bb1 Open Hi-Hat
B1 Low-Mid Tom
C2 Hi Mid Tom
C#2 Crash Cymbal 1
D2 High Tom
Eb2 Ride Cymbal 1
E2 Chinese Cymbal
F2 Ride Bell
F#2 Tambourine
G2 Splash Cymbal
Ab2 Cowbell
A2 Crash Cymbal 2
Bb2 Vibraslap
B2 Ride Cymbal 2
C3 Hi Bongo
C#3 Low Bongo
D3 Mute Hi Conga
Eb3 Open Hi Conga
E3 Low Conga
F3 High Timbale
F#3 Low Timbale
G3 High Agogo
Ab3 Low Agogo
A3 Cabasa
Bb3 Maracas
B3 Short Whistle
C4 Long Whistle
C#4 Short Guiro
D4 Long Guiro
Eb4 Claves
E4 Hi Wood Block
F4 Low Wood Block
F#4 Mute Cuica
G4 Open Cuica
Ab4 Mute Triangle
A4 Open Triangle
I think this instrument is the only one that people break this rule
(beside fun noises), you'll never find a C in flute corresponding to a
F, so why is this allowed in drums?
mussol
Missatge de Philipp Müller via Hydrogen-devel
<hydrogen-devel@lists.sourceforge.net> del dia dg., 26 d’abr. 2020 a
les 22:14:
I'm quite interested in this one too. But for a slightly different
reason. Right now it is not possible to just switch between different
drumkits in order to determine which one fits a particular song best.
Since the assignment of the new instrument while switching is
determined by the vertical position of the particular instrument and
not by its nature, one has to do a lot of adjustments by hand. I
ended up writing some elisp helper functions [1] but it's still
tedious.
Another thing is the renaming of the per-instruments JACK ports after
switching the drumkit. Is it really necessary that the ports have to
same name as the particular instrument or could it be just "snare1,
snare2, kick1" ..? This way JACK-based wiring into effects, mixers or
other applications could be preserved to a large extend.
I think both inconveniences could be resolved by tags. One with a
limited set of qualifiers (like "crash", "kick", etc) and one holding
an uint to determine the order/priority. If the second one is
missing, the order of appearance will be used. If the first one is
missing (for all or some instruments), they will handled upon
switching/renaming as we do right now. What do you think?
Cheers,
Phil
[1]
https://github.com/theGreatWhiteShark/configurations-and-scripts/blob/master/emacs/elisp/hydrogen.el
On 4/26/20 12:12 PM, mau...@smoors.de wrote:
3- Patterns should be kit agnostics. Sometimes I discard a pattern
because it sound bad and later I found is because it was created with
another kit so elements get mixed. This shouldn't happen. Also it
would be great to be able to import midi directly. I know this have
been discussed in the past and maybe is a good time to start.
Yes, this has been discussed in the past. But without any result. Do
you have any good idea how to implement this? We discussed a
tag-based
system, but this was years ago and nobody had since an interest in
implementing
this.
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
