what about having a sound library like what you have in lmms or fruityloops.
a sample library (tree like, categorised, tagged) on top of that an instrument library (bundle of samples + presets, categorised, tagged) on top of that a drumkit library (bundle of instruments and/or samples) feels like the drumkits we have right now but much more open and easy to handle. you can import some new samples files, create new instrument mixing these new samples and old one then add the new instrument to an existing drumkit ... all that from the library management window. you can still load/save/export/import drumkits quickly change an instrument by browsing your library. loading another drumkit/song that shares common samples will be much faster. using instrument category/tags when loading a drumkit instead of instrument order (see above). On Sunday 26 April 2020 22:15, Philipp Müller via Hydrogen-devel wrote : > 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? yes ! H2 user settings should determine the order you want the instruments to be shown on the pattern editor, not the drumkit. when loading a drumkit, it's instruments should be assign to the proper pattern editor line using category/tags. same for patterns. > > 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 ----------------------- Jérémy Zurcher rue des Charmilles 7 1400 Yverdon-les-bains +41 (0) 79 599 84 27 _______________________________________________ Hydrogen-devel mailing list Hydrogen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
