I'm not sure what you mean by "LE" specifically.. but I gather that you
mean making rezound more interactive and less procedural (which is still
Have you seen JACK? I think JACK itself would facilitate what you're
talking about. And if so, I'd prefer not to re-invent that very
complicated wheel. ReZound attempts to support JACK at present, but
much remains to be done still. JACK allows you to connect other
JACK-supporting applications together like you can in rewire I believe.
I would be interested in any new UI layout designs you might have. Just
send them here. I think you can attach files--if you need do. If not,
I'll try to change the list to allow it.
Benjamin P. Keating wrote:
>I've been thinking about rezound and design lately, mostly because im
>*still* working out a web design. All apologizes for the delay, it's
>been very busy here in the Bay Area and I want the look & feel to be
>the absolute best in presenting Rezound.
>Before the letter went out about front-end stuffage I got thinking
>about the UI, not the technical bits (gtk2 fox, etc) but the actual UI
>that users will interact with (im not much of a programmer). I have a
>lot of sketches that I've been thinking about converting to onscreen
>graphic mock-ups, would ya'll be interested in seeing them or is the
>UI going to remain the same? I strongly suggest that with this
>front-end migration, to whatever we use - the UI should be brushed up
>a bit. You know, put the flow back in work flow ;)
>There is also this other idea that was originally my own but thought
>it'd be interesting to hear your opinions on it - and that's dead
>simple "LE" version of Rezound. Why? I've been playing with Cuebase,
>Live and a bunch of other applications but it was mostly live that I
>was amazed with, mostly because of it's work flow. I wanted to have
>that sort of feel or even vibe with a sound capturing application,
>I use Rezound mostly for live events (usually lectures and raves) and
>I record the talk / dj sets to disk. The tools within rezound i count
>on to get this job done right; the level meters, time bar, recording
>indicator, etc. basically whats inside the record dialog window.
>Visually seeing the waveform after recording isn't that big of a deal
>to me as Im not concerned about that step until I get back to the
>studio to mix it down.
>So why not an LE version? How about cutting up the program into
>multiple 'sound tools', rezound could then become a suite of
>applications, sticking to the UNIX way. Is Rewire an open protocol?
>perhaps that could be used to string them together. If not, just an LE
>version would be nice.
>All in all, I feel the interface should be looked over and modified to
>better fit the studio, stage and road and all the challenges in
>between. It feels way to much like a programmers tool - when, with the
>features it packs, could easily become a musicians tool.
>There should be as few technical boundaries as possible when it comes
>to the user getting there ideas out and recorded.
>Can I help with this? Whether is be a UI brush up, mailing list chat
>or defining a separate LE version... i have energy for this, let me
>invest it into rezound.
>* I'll be posting a demo of the new design within the next 3 weeks.
>This SF.Net email is sponsored by:
>Power Architecture Resource Center: Free content, downloads, discussions,
>and more. http://solutions.newsforge.com/ibmarch.tmpl
>ReZound-users mailing list
>Subscribe/Unsubscribe and change options
>ReZound-users mailing list archive