Re: [Audacity-devel] compile trouble (MacOS X)

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

Webb,

> Features like vorbis / mp3 support and 32 bit sound may be more sexy, but
> what I want to work on is getting the "playback existing tracks while
> recording new one" to work on MacOS X, being able to open audacity files
> by double-clicking on them, fewer crashes, and a vertical playhead with
> scrubbing, and maybe a metronome click. Those are the areas most useful to
> me for recording music.

A few of these are already in progress.

* Full duplex (play while recording) is being attacked by the PortAudio
   team already.  Rather than reinvent the wheel, give them a couple of
   weeks and then we can test the new code.

* Vertical playhead is working.

Scrubbing would be great, but I tried to implement it once and gave
up for the time - it's very difficult!  Let's definitely talk about
it if you have some ideas on how it could be implemented.

The metronome click is a good, cross-platform feature that has been
requested before.  Shouldn't be too hard, but it would require the
full-duplex functionality to work first.

Opening Audacity files by double-clicking on them works for me
(and always has - that isn't new.)  What happens when you try it? 
(Audacity projects, WAV, and AIFF files are all that are supported...)

Actually there's one big Mac OS X thing that it would be great
if you could help out with.  Audacity doesn't get any idle events
from wxWindows while the mouse is being held down over a menu or
a scrollbar.  That means that samples get lost if you're busy
recording.

It would be great if you could investigate possible fixes for this.
Maybe a Carbon Timer would work; if not you may have to use a
separate thread.  In any event, this would probably require
adding some mutexes/critical section lockers.

One other thing comes to mind: since you have speech recognition
experience, maybe you could help with the Frequency dialog.
I'm not sure if the patch to get it working in 1.1 is in yet,
and then you could get Cepstrum to work.  I think I got the
formula wrong.

Another OS X bug you could look at: why does the program crash
if you open up 20 - 30 windows?

- Dominic