Re: [ecasound] future of qtecasound?

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] future of qtecasound?
From: Jeremy Hall (jhall@UU.NET)
Date: Thu May 04 2000 - 14:23:00 EEST

One of the reasons, imho, that people really love ecasound is because it
is feature-rich and delivers what it is supposed to. One of the strong
reasons for this is that people decided the best way to do this is build
the necessary tools so that the required features could be there, then
later if somebody wanted the gui they could buid it. Many projects get
hung up on "needed" vs "likeable" things.

I suppose one could argue that a GUI is needed for the program to function
correctly, I am not one of those people since the GUI will slow down the
processing power of ecasound. (not to mention I don't use the gui)

If the question is whether to develop more functional or gui features,
there's a toss up. To evaluate it, you have to decide whether the user
will be willing to use ecasound's console interface to benefit from the
features, or whether the gui will attract more developers and thus both
would happen. It really depends on the community you're trying to reach
and their preferences.

just my $.02


In the new year, lee johnson wrote:
> >
> First off i want to express my deep felt appreciation for the ecasound in the
> first place..moving to linux ( and not having benefit of ..yes..acid music of
> which i use express ( freeware) version ) has been somewhat not without
> hurdles but ecasound/wave/qtecasound has helped greatly reduce
> that.........
> so from my vantage point anything you do to improve these programs is
> awesome and very appreciated....anything i can do i love to help..
> as far as which one should you concentrate on...well from what i've seen (
> and not much yet i'm really NEW to ecasound etc. ) ecasound is very feature
> rich already so i'd concentrate on the gui if it were me.....I personally
> don't want a acidmusic/cakewalk clone but something just as good or better
> but with its own distinctive richness and ease of use for say beginners who
> want to try their hand at music me :)!
> hope this helps
> lee-
> URL ref -what i've done mostly with acid music/realproducer ( singalong site
> at above url ) and look forward to doing it all someday soon on my linuxbox
> :)))))))))))))
> >
> >
> > Another problem is that I don't use it myself anymore. At the moment,
> > console-mode ecasound and ecawave are enough for my purposes. I know many
> > people would like to see qtecasound with an interface something like
> > Cakewalk or Acid. This would be great, I admit, but it won't happen
> > overnight. Writing a full-blown GUI, is always a _big_ project.
> >
> > So, now I'd like to hear your opinion? Should I spend time on improving
> > the current qtecasound interface, or should I redesign the whole thing?
> > What kind of interface you'd like to have? Do you use qtecasound? What
> > things you find most difficult to do with the console mode interface?
> >
> --
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <>.

To unsubscribe send message 'unsubscribe' in the body of the
message to <>.

New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Thu May 04 2000 - 14:23:54 EEST