Am Fri, 24 Aug 2012 21:14:56 +0200 schrieb Thijs van severen <[email protected]>:
> 2012/8/24 Sebastian Moors <[email protected]> > > > Thijs van severen wrote: > > > hello again > > > > > > i'm playing around with some patterns that i want to save, but looking > > > at the 'h2pattern 'XML file there seems to be a field > > > called <pattern_for_drumkit> > > > i cant find an option (in H2) where you can actually change this info, > > > and in the patterns i have saved this field is empty > > > IMO an obvious default value would be the name of the drumkit that was > > > loaded at the moment the pattern was saved (but i guess you should be > > > able to overrule this manually) > > > > > > i'm guessing that this is a field that describes for what drumkit the > > > pattern was created, and that makes a lot of sense to me > > > i theory all patterns and drumkits should be GMcompliant, but we all > > > know that that's not the case. > > > therefore most patterns will only sound OK when using the correct drumkit > > Yes, this field is there to give an "advise" about the drumkit that > > should be used for the pattern. I remember that i discussed this with > > wolke quite some time ago, i'll have to look at the implementation to > > see if this is something that was already implemented.. > > - Sebastian > > > > Hi Sebastian > > i like that this is not a limitation, but an advice. > IMHO this field should be editable on the pattern properties window (right > click on the pattern name - properties) via a dropdown list of all loaded > drumkits > > grtz > Thijs hi, if i create the pattern export, my first thought was to store pattern in data/drumkit/drumkitname/pattern/patternname.h2pattern. so i decide to add the node pattern_for_drumkit. in this sort order the node makes sense, because i also planed to list the pattern in soundlibrary also sorted by drumkitnames. the second idea behind storing pattern in corresponding drumkit directory was, to export drumkits with all included pattern. a easy way to share drumkits with a bunch of pattern. in some discussions we found out, that the new song structure, which is at least drumkit independent, point into an other not static drumkit dependent work-flow. so we deside to handle all patterns at least drumkit independent. now, some years later and also some years more with extremely intensive hydrogen sessions my work flow have a intensive use of drumkit mixing in new songs. i drag and drop instrumentsra and save songs. but mostly, if the drumkit mix is really cool, i also decide to save the created drumkit compilations as a new drumkit. at least to share it with freinds or band members. i think most people use a similarly way if they work intensive with hydrogen. and in this case i would prefer to store and sort patterns drumkit dependent. so i wish me a pattern handling as i have planned at first. imo, it would be cool if we can discuss this here. plus: * share drumkits with many cool default pattern inside greetings wolke > > > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Hydrogen-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel > > > > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
