Re: [Audacity-devel] {Posible SPAM} Re: [PATCH] Bug 473 - Track can be in "Solo" mode when there is no solo button

[Federico M. <fm...@fc...>]

Dear all,

> It's a bit odd that we save the solo/mute state in the project at all 
> (though it is convenient for "picking up where you left off"). 

Several years ago I used to program in QuickBasic. When I changed to 
Pascal I was delighted with that simple feature of opening a project 
exactly where you had left it.

I think that any move towards allowing the user to close a project and 
then reopen it exactly as the last time they worked on it is worth the 
effort since it makes the program more friendly to use.

> A bit of explanation if it's not obvious: "Solo / Mute" states are 
> either part of the project state or not. If we consider that they are, 
> then they should be saved in the project and treated as a change to 
> the project when changed, If not, then they should neither appear in 
> History nor be saved in the project. 

I think a project could be far more than just an audio file. Edition 
events are good candidates to be saved as well as undo lists. The only 
thing that prevents this is that clips are actually modified when 
effects are applied. It is just a matter of storage capacity vs. 
renderig time. You could store the result of each effect applied 
creating a new waveclip so you can go back, or you could store the 
edition events and then replicate each edition event up to the undo 
point you choose. The first is storage-consuming, the second is 
time-consuming. However, provided that the original material is not 
overwritten, the second allows good documentation of all processes 
applied, as well as the possibility to optimize the whole process (for 
instance, if there have been many amplifications, they could be reduced 
to a single one, which could improve the result.

Regards,

Federico