Gabriel M. Beddingfield wrote: > On Mon, 31 Aug 2009, Gabriel M. Beddingfield wrote: > > >> I suggest that we collect all feature requests and future directions into >> one document. (Well, as many as we can....) >> > > FWIW, I plan to build this document after fixing issues with the manual. > I have all the e-mails and will use those to compile it. > > I considered using the Trac Wiki... but I don't think I can get > notifications on edits to just a single page (e.g. RSS feed or e-mail > notice). > Maybe the assembla wiki is capable of this? Haven't used it so far.. > >> 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. >> > > Here are some of my wants: > > * Audio loops with time stretch (both beat slicing > and time stretch) > > * One screen, uncluttered interface.[1] Make sure it works > with Netbooks (like the EEE PC). > Does this refer to the whole application or just the sampler interface? > * JACK only. Reduce the number of drivers we support and > focus on what we do best. In redesigning the backend, I've > noticed that I'm having to RE-implement JACK in order to > maintain compatability with all our audio drivers. This > is a duplicate effort. > Huh.. At least "jack-only" is a surprising for me.. That would mean that we drop support for OSX / Windows (ok, we could see if we could build packages for those platforms with jack support..) - Sebastian
------------------------------------------------------------------------------ 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
