On Friday 19 March 2004 09:01 am, Alexandre Prokoudine wrote:
> Point one: Commercial distribution.
> I remember Dominic or Matt uploading two sample
> projects or at least two pair of files to be mixed. If
> you make a sample project of, say, 4 tracks (drums,
> bassline, piano and some soloing instrument) and make
> it easy to open it -- this will be great.
This is a great idea, and it's something I could throw together pretty easily,
but I am somewhat limited to guitar, drums, and bass. If a piano line is
really needed, I could use some help there. ;)
> Poin two: Future.
> I wonder, if you do, but I really have no idea what
> Audacity will be like in a year. I spent much time on
> using sound apps (for Win) about 5 years ago. At that
> time both Cubase and Cakewalk still were
> MIDI-sequencers and were not that good for audio.
> Samplitude was just a multitrack recorder/editor.
> CoolEdit was just an editor. Some time later I stopped
> using them all for some reasons. I never returned to
> them till last week.
Two things about this. Taking cues from the commercial apps is good,
yadayadayada. But there's a reason there's separate open source apps for
audio and midi, and I don't think we can completely ignore that reason,
whatever it is. Ultimately, the cues the make the important design
decisions, in my opinion, should come from users and actual usage.
> Several days ago I installed modern versions of DAWs
> for Win -- Samplitude, Nuendo etc. just for my
> curiousity, what they look like now. You might know
> what I've found out: they are all DAWs now, except
> Adobe Audition (ex-Cooledit) and SoundForge. In all
> other apps MIDI and audio are tightly integrated.
> When I look at opensource apps, I see that there is no
> real DAW like e.g. Nuendo, because developers focus on
> either MIDI, or audio only. This is why I didn't like
> much the fact that Alacrity will be a standalone app,
> however much integrated with Audacity.
This is a conceptual thing, and I don't think you're quite grokking my whole
fancy vision. :) I'm thinking something more along the lines of Mozilla, in
the end, the two GUIs as separate, independent projects won't really exist
anymore. The thing is, Audacity is already pretty mature and stable, so
experimenting with the GUI in Audacity by the nature of where the project is
right now can be difficult, and it can hold up new features being
implemented. But a GUI for MIDI stuff, right now, needs a fair amount of
experimenting. (I have issues with both RoseGarden and MuSE) So, in my
opinion, having a separate MIDI app for awhile that allows the level of
experimentation you find in a younger project is a good thing, but in the end
Alacrity will cease to exist as a standalone app. So, we're on the same
page. Really, we are! :) Think more like Excel and Word, which aren't
really separate applications anymore, they're just activex hosts embedding
either the excel control or the word control, but they can embed each other's
controls and use them. I wouldn't be surprised if the excel and word
binaries are the same with only a few bytes difference that tell it which
activex control to use. ;)
> Audacity already has a mechanism to handle features
> requests. Could a a features roadmap be the next step?
Well, on my plate as part of my website rewrite is to take another pass at the
feature request script (and to put it on my website so people can request
features for the website and for the feature request script itself. Eat my
own dog food, I will). I've got a guy who's interested in seeing an
authentication mechanism built in. I can add priorities, user assignment of
features, and so forth, so that the Feature Request script can generate a
roadmap, and in the process it'll be a roadmap people can vote on. It won't
be able to remain in one single file any more, but that's fine. So, if you
guys want me to add more stuff to it, now's the time to speak up. :) I'm
already wanting to add comments ala slashdot to it, so a user mechanism is
already going to be added anyway.
> I also have some notes about current website of
> Audacity, but I will share them a bit later, after I
> sort them out better.
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> Audacity-devel mailing list
Visit my website!
Give thought to your reputation. Consider changing name and moving to
a new town.