On Tue, March 10, 2009 8:14 am, Krzysztof Foltman wrote:
>> I've just reached a point where, if someone wanted to, they could help
>> with what
>> I'm doing.  (and the help would be welcome!)
>
> I could try to help (as far as time permits etc.) but you'd have to tell
> me exactly which part should I do, etc.

Here's some ideas...

SeqScript and SeqScriptIterator need implementations.  I was thinking
about using std::priority_queue for scaffolding -- and working out a
realtime implementation later.  (Something that has memory pre-allocated,
like a ring buffer.)  Note that I plan to (eventually) move the headers to
libs/hydrogen/include/hydrogen because the GUI will need them to send
events.

I'm currently working on the song sequencer (merge TransportPosition and
current Song to a SeqScript)... but if you want, I can turn that over to
you.

H2Core::Hydrogen needs a total rebuild to act more as a controller for the
audio backend rather than a sequencer.

I have vague plans for rearranging H2Core::Sampler and
H2Core::Instrument... but I'm not exactly sure what I'm going to do just
yet.

A testing framework would be nice for the following purposes:  (a) testing
out the new classes and catching bugs early.  (b) Whenever someone creates
a new implementation of SeqInputInterface, SeqClientInterface, or
TransportMasterInterface... it would be nice to have a single test that
confirms that they conform to all the rules.  (c) To provide a sort of
scaffolding until the whole thing is working.

...and if something else inspires you -- let me know.  :-)

> I like the new design, it's clean and easy to understand (easier to find
> potential bugs later!).

Thanks!

-- 
               G a b r i e l   M   B e d d i n g f i e l d


------------------------------------------------------------------------------
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel

Reply via email to