Re: [Audacity-devel] Menu options

[Dominic M. <do...@au...>]

Greg Mekkes wrote:
> Maybe I'm the only one who actively uses all the align functions, but
> that's why I wrote them all and put them in.  There are scenarios where
> each of the different flavors of align can be very useful.  I'm not blind,
> but do find them useful.  If I'm the only one thinking this way, then just
> go with the main train of thought and do what needs to be done.

For what it's worth, I find these options incredibly useful.  I think 
there should be easier ways to do some of this alignment (i.e. clips could 
automatically "snap" to places like 0.0, to the start pos of another 
track, etc.) but until then, we have to keep these.

I will join the rest of the discussion when I have a chance.  But in a 
nutshell, I propose that somebody go ahead and make all of these proposed 
changes in CVS and we'll see how we like it.  I think I'll agree with 90% 
of them, and probably most others do, too.  I propose that we don't 
actually delete any options at all, unless you want to implement an 
improved function that satisfies the same capability some other way. 
Instead, let's move them somewhere else.  For example, even "Import MIDI" 
is really being used by a few people - I use it to check the results of 
pitch-recognition algorithms that generate MIDI files.  But I'm happy 
removing it from a prominent place in the Project menu; maybe just have 
"Import Audio" call that code when it gets a file ending in .mid or .midi 
would be fine.

- Dominic

> 
>>...
> 
> 
>>Edit Menu: Snap-to|Snap-to on/Snap-to off.  This just seems wrong to be
>>a menu option.  Maybe it could be moved to a check box on the selection
>>bar.
> 
> 
> Sorry, that was just the simplest way to implement it at the time.
> What you are suggesting was along the line of what I had in mind
> originally and would be an improvement.
> 
> 
>>...
> 
> 
>>Project Menu: Align and Move Cursor.  Get rid of them them all. The
>>concept of moving a clip without moving the selection might be useful,
>>but why not just make those samples a different clip?  If truly deemed
>>necessary, we might be able to devise a 'lock selection to clip' mode or
>>markers that are bound to sample positions rather than timeline
>>positions.
> 
> 
> Yikes, see above comments.  However, the concept of locking selection
> to clip or not locking to clip could potentially be all the same
> functionality that there is now, just presented in a different way.
> 
> 
>>...
> 
> 
>>Comments?
> 
> 
> Just on some of them.
> 
> Greg Mekkes
> 
> 
> 		
> Yahoo! Mail
> Stay connected, organized, and protected. Take the tour:
> http://tour.mail.yahoo.com/mailtour.html
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel