Re: [Audacity-devel] Audacity Patches

[Gale A. <ga...@au...>]

    | From "sl contrib" <sl....@go...> 
    | Tue, 18 Sep 2007 23:38:22 +0100
    | Subject: [Audacity-devel] Audacity Patches
    | > (1) The 'mix to new track' suggests a more general option that any
    | > 'effect' can be rendered to a new track, with the original tracks all
    | > being muted....  So I don't want this one included in its current form
    | > for 1.3.4/1.4.
    | 
    | I guess my original aim was to create a simple way of checking whether
    | a mix was distorting somewhere. We often edit long pieces of audio,
    | and it's impractical to listen to the whole thing just to check for
    | distortion, so we need to be able to do a final check for distortion
    | somehow.
    | 
    | Does anybody have a view how this should be implemented in audacity?
    | I'd be keen to hear other people's thoughts.

I'd have thought longer term Audacity should aim to calculate this for 
itself i.e. see where the clipping occurs when tracks are mixed and 
reduce the gain on each by the same amount so that the mix is at - 0dB
(without having to explicitly mix and render).  Is this practical? View >
Show Clipping seems quite fast. 

As a workround, you could duplicate the tracks in your mix, then select the 
originals and Tracks > Mix and Render.  Then you have the originals 
plus the mix with clipping for reference.
 
    | > Richard:  Do you fancy making the solo
    | > buttons work on exports as well?
    | Is it planned to keep the current behaviour, where several tracks can
    | be solo'd? Or are you planning to move to a scenario where only one
    | track can be solo'd?
    | Currently, solo overrides mute. Again, are you planning to keep this?

We are occasionally asked that the solo buttons should be mutually 
exclusive so that you can only solo one track at a time. Someone 
requesting this on our Wiki says "this is a universally established function
of the solo button on mixers". But to "solo" two tracks out of eight you 
would then have to mute the other six. I'd think we have this right now
and perhaps the word "solo" is the confusion?  

Solo over-rides mute seems right to me, but my long-standing beef (unless
I am missing something) is that you should not be able to mute and solo 
a track at the same time. If I have two tracks, both on "solo", then only 
want to hear the first, the intuitive thing to do as I see it is to hit mute on
the second track, but this has no effect - I have to unsolo the second 
track. If I then want to hear the second on its own, there is no one-click
way to do that, whereas if mute on the first track turned its solo off, 
there would be. I would very much like to change this. 

Whatever we do, wouldn't the neatest code export only those tracks that 
still display blue waveform, irrespective of the solo/mute configuration
that creates that?


Gale  




Outbound message virus free.
Tested on: 9/19/2007 2:12:03 AM