I searched the forum for an answer to this but I did not find one so I am writing a post looking for help.
I just installed the AudioMulch 2.1.0 trial on my MacBook Pro. On initial launch and when I tried to apply changes to the sampling rate from 44.1 kHz to 96 kHz in the Preferences I got the following error:
Internal PortAudio error (PortAudio error -9986)
I am using the Built-In audio card which can run up to 2 channels at 24bit/94kHz.
I looked online and found no information on this error. My system is installed on a recently zeroed out drive and has Live 8.1.5, Logic Pro 9.1.1 and MaxMSP 5.1.4 installed on it. All of which work fine.
Apple MacBook Pro
2 GHz Intel Core Duo
2 GB 667 MHz DDR2 SDRAM
OS X 10.6.4
Built In Audio
Thanks in advance for any assistance.
I don't have a definitive answer for you, but if you set AM to output at 96kHz and you are running any other audio software at the same time, and that software is not also set to 96kHz output then you will get this error. So make sure iTunes is not running and you have any other running audio software switched to 96kHz.
If you have no other audio software running and you still get this error please get back to me and I can look into it further.
Since you're on Snow Leopard, it's also possible the following update will fix the problem:
[EDIT] Version 2.1.1 available here -> http://www.audiomulch.com/download.htm [/EDIT]
That's a beta of the next update. It should be officially released next week. It includes some fixes for OSX audio including a Snow Leopard compatibility issue that was previously fixed in 2.0.4 but didn't make it into version 2.1.0
AudioMulch is the only application that is running when this happens. I will download and install this update and see if it resolves the issue. I will let you know of the results. Thanks very much for your attention to this. It is greatly appreciated!
No problems. Please do let me know if it works for you. Here I can change sample rates without problems so hopefully it fixes the problem. If not I would like to get this resolved this week before I release the update. Thanks.