Re: some usability review

[Tim Janik <timj gtk org>]

On Thu, 16 Dec 2004, Will Light wrote:

> On Thu, 16 Dec 2004 16:10:14 +0100 (CET), Tim Janik <timj gtk org> wrote:
> > On Thu, 16 Dec 2004, Will Light wrote:

> > > a way to do this would be to switch the audio driver to null, play the
> > > file, then restore it.  try this: create a song in beast, save, quit
> > > beast, reopen beast with "-p null", and try to export it.  depending
> > > on how complex your song is, the export will be much faster.  here's
> > > what an "export song" menu command should do:
> > >
> > > 1) prompt user for file to save to
> > > 2) switch audio driver to null
> > > 3) play song (exporting to a wave file)
> > > 4) switch audio driver back to oss/alsa
> >
> > this would have to be an alternative/extra feature though, since
> > you can't modify the sound during playback that way (e.g. by moving
> > sliders or via means of external MIDI events).
> > also, it doesn't properly deal with endless song loops, i suppose
> > one could add a maximum loop counter to that dialog though.
> >
> > in any case, it doesn't eliminate the need for the current
> > WAV file recording field which allows for interactive song
> > modifications during playback.
>
> i agree.  but still, people coming from the Windows world are used to
> really fast song exports.
>
> btw, andrew (other half of the hindenburg symphony orchestra), thinks
> that if you put the fast export feature in, it should have a
> progressbar :)

yes, it should. i'm just saying, it would be another feature, not replacing
the current recording file field.
and, we might simply use a script for this and render the song via
bsesh in an extra process. that way, it won't interfere with ordinary
(maybe still running) beast stuff. (and it also solves the problem
of switching sound drivers during runtime, whcih beast can't do).


---
ciaoTJ