Patrick Shirkey wrote:
> On 09/01/2009 12:56 AM, Gabriel M. Beddingfield wrote:
>   
>> Hi Guys,
>>
>> There has been a lot of talk about new features, new directions, etc.,
>> etc.  In addition, Patrick is doing a good job of drumming up support for
>> the "Live" direction -- so we may see more developers.
>>
>> I suggest that we collect all feature requests and future directions into
>> one document.  (Well, as many as we can....)
>>
>> Then, let's agree on what we do and do not want... and make a semi-formal
>> specification for what Hydrogen "should be." -- Including mock-ups of
>> screens and menus.
>>
>> Then, let's set up a roadmap for how we plan to get there.  (E.g. right
>> now we have semi-tentative plans on what order to merge some of the
>> existing branches.)
>>
>> In the end, I think this will get us "there" faster, and allow better
>> coordination as features get added.
>>
>> What do you think?
>>     
Great idea! Here are some comments:
>>    
>>     
>
>
>
> I think it's the right approach and will save some hassles down the line 
> as well as give people something to aim for.
>
>  From my perspective I see the sampler interface requiring the following 
> core features:
>
> - Multiple song playback at one time - has anyone tried this yet with 
> the playlist code?
>   
That won't work at the moment, and i believe that it will be hard 
("hard" means "we have to touch a lot of code") to implement. What's the 
intention of having multiple songs playing at the same time? What about 
groups of patterns?

 Maybe we should clarify the terms here a little bit.. For us hydrogen 
guys, a song is like a container for patterns and instruments.
Furthermore a song contains temporary changes to the instruments ( like 
additional gain of on instrument).
And a song uses (in the most cases) just one drumkit, or at least one 
kit with some additional instruments.


> - Instant song loading (internal)
>   
When you're loading a song, you're loading the corresponding drumset. 
This takes some time. So it would be hard to load a song per midi and 
expect that it starts to play instantly. You have to think about 
disk-streaming or preloading to avoid this.
> - Midi bindings for the sample buttons (for controlling internal playback)
> - Per song volume control
>
>
> I see these as nice to have but not essential for immediate dev targets.
>
> - multiple bpm counters/per song bpm
> - midi control for external apps
> - instant multitrack record via jack/ardour/renoise etc...
> - Save session state with lash
> - load/bind to external apps/sessions and trigger playback per sample button
>
>   


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel

Reply via email to