Am Fri, 17 Feb 2012 20:53:29 +0100
schrieb Albert Graef :
> On 02/17/2012 06:01 PM, Sebastian Moors wrote:
if i designed the hydrogen-sample-editor the main concept was to make them non
destructive and bind all sample settings to h2 song-files. this follow strictly the new
hydrogen song concept since version 0.9.4. since 0.9.4 it is possible to crate/modify/save
songs with instrument sets which can be independent from existing sound-libraries
(drumkits). imo, this is one of the biggest improvements for song creation in hydrogen.
in this case it make really no sense to save the results of sample editing directly into
the corresponding drumkit. more... this will destroy the no destructive load function. an
example here is, if you create a song X with sample(instrument) X which holds non
destructive changing via sample editor. what happens if you have changed this
sample(intrument) X for example some days later when you are working on song Y? you will
definitely destroy song X.
how ever, i am thinking about two improvements on the sampleditor which will go into
the direction you suggest.
* export sample-editor results as an audiofile
* quick create new instrument button. this will simple create an new h2 instrument which
include the resulting sample. my idea is, simple arrange the new instrument directly
below the instrument that you currently modifying. the problem here is that you have
to store the resulting audio file. currently i have no idea where i store this files.
(:the following is a bit offtopic but important for me to say. because imo, DrMr and
hydrogen are complete different tools which follow different composing ideas:)
but this improvements cannot reconstruct the main goal from the sample editor rubberband
implementation. i mean the instrument-layer-rubberband-batch-processor-function. :) long
word. maybe you know this function. if you have enabled the batch processor, hydrogen
recalculate at tempo changing on the fly for all samples which are modified with
rubberband. this allows users to change tempo for example via jacktransport.
if you work with loop-samples (i do this a lot) hydrogen's samples(loops) all time fit
into your beat. so it is possible to trigger the loop-instruments via midi triggers.
good for people which play live sessions.
currently all my further plans for the sample-editor goes into this live useability.
in moment hydrogen has two faces. first face is the simple and intuitive to use drum
machine sequencer which allows users to create drum tracks with only a few mouse clicks
without any experience.
but second face is a nice live tool which holds many nice functions in the background.
this features are mostly arranged in the background to keep the simple to use interface
as it is.
i think the future of hydrogen is more or less the way in direction live tool. also it
has a good useability to practice guitar, bass or whatever instruments. but it have no
future as an composing tool to crate(produce) static songs via an daw. here users need
plugins like DrMr. and so i think the future for DrMr cannot be an to closed
orientation on hydrogen drumkits and his structure and functions. imo, it's a good
idea to simply support h2 drumkits. but better is to follow an more modern and way of
sampling drums. and this need at least an other instrument structure of layering than
hydrogen instruments follow. DrMr is on the beginning. so everything is possible.
Linux-audio-dev mailing list