Re: some usability review

[Will Light <filterchild gmail com>]

On Thu, 16 Dec 2004 16:10:14 +0100 (CET), Tim Janik <timj gtk org> wrote:
> On Thu, 16 Dec 2004, Will Light wrote:
> 
> > On Thu, 16 Dec 2004 04:47:43 +0100 (CET), Tim Janik <timj gtk org> wrote:
> 
> >>>   suggestion: replace the whole functioniality by "File -> Export Song as
> >>>   Audio" and "File -> Export Loop as Audio"
> >>
> >> i don't see how this would be an equivalent feature. the Export Audio
> >> feature records everything that is produced by the current interactive (!!)
> >> session to a WAV file. offline rendering of the sound file is not a
> >> suitable replacement for that.
> >>
> >
> > 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 :)

> ---
> ciaoTJ
>