Hi everyone!
Here comes my proposal..
--
We're using the folder "data/drumkit/drumkitname/pattern/" for
"default patterns".
A default pattern is a pattern which is inherently related to the
drumkit. Example:
If you look at the quite popular "DeathMetalKit", the default patterns
will be some
evil blast beat patterns and such. Pattern get default patterns by
placing them in
respective folder, nothing else. No big magic.
All other patterns, even the patterns which are used in songs for the
"DeathMetalKit",
go into data/patterns. The patterns XML structure receives a new
element, a list of
drumkit advices. The advices tell hydrogen which drumkit is compatible
with this pattern.
In the real world, you would list most likely only one kit there, but
you can also list more.
A use case for listing more then one pattern is the use of a
GMKit-compatible drumkit,
where you can list all the drumkits which are built using the GM standard.
If you want to export/save a drumkit, we could offer a dialog which
searches your soundlibrary
for compatible patterns with this drumkit and offers to use some of
these patterns as default
patterns.
</proposal>
For sharing with friends, i would think that we should work out a real
proposal for our .h2project
stuff. A simple plan:
- .h2project is a compressed file which has the same directory layout as
your .hydrogen folder
- Use case: You want to export your project in a way that everything you
need for that project (drumkits, songs, patterns)
is available to the remote system (the system on which the
.h2project will be loaded later).
Btw. we need to think about the path name handling (absolute/relative)
in songs before we do sth. else, that's the last bug (ok, the second
last, with the "note off" bug) for 0.9.6 that keeps us away from
releasing an RC.
- Sebastian
> 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
------------------------------------------------------------------------------
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
