Recent changes to bugs

Trigger not working

Anonymous — Wed, 23 Dec 2009 09:35:25 -0000

The trigger control simply seems not to work. MacCRO X installed on MacBook 2 GHz Intel Core 2 Duo, 2 GB 667 MHz DDr2 SDRAM OS X 10.5.8.

installation barrier...

Anonymous — Fri, 12 Dec 2003 02:27:08 -0000

After successfully downloading MacCRO 0.1.2 I am not getting an
authentication popup when I go to install the package. This
causes an error message about not having priviledges to install
the software in the default place on my OS-X HD drive as I
continue through the install sequence.

I am running OS-X version 10.2.8 on a 533Mhz G4.

I tried an Apple install of itunes upgrade just to make sure the
system was working correctly and the authentication popup came
up with no problems giving my the chance to enter my admin
password. They are using the same type of installer as you are.

Any ideas?

BTW,
I have an old OS9 MacCRO 2.0 that works great in the OS-X
classic environment.

I really like your log amplitude and frequency functions on your
spectrum analyzer.

Can you email me with an answer and also let me know when
your finished OS-X version is ready?

Also,
My registration number is not being excepted in the 2.0 version
of MacCRO (1611889550).

Thanks,
William Martens
martens@cs.utah.edu

martens@cs.utah.edu

"invalid sample rate" crash on G4 mdd

david myers — Tue, 22 Apr 2003 15:25:12 -0000

On my 1 GHz mirrordoor G4, launching MacCro X produces no
windows. Selecting any menu item (even "about...) shuts down
the app.

Hmmm.

David Myers
dmgraph@earthlink.net

PortAudioSampler fails to open input stream (iMic)

Philip Derrin — Sun, 02 Feb 2003 12:38:02 -0000

On a G4/466 using a USB iMic input device:

The first time MacCRO X runs after each reboot, it fails to open the input stream with the following error message:

Could not force buffer size!2003-02-02 21:46:56.279 MacCRO X[729] Pa_OpenStream: returned -10000 (Host error.)

It works correctly on subsequent runs.

This appears to be a limitation in PortAudio's CoreAudio implementation. According to messages posted on the PortAudio mailing list, the next release of PortAudio (v19) should fix this problem, but it is still under development.