Known Bugs and Errors

There is no audio: If you are not using the application from your /Applications folder or if you have renamed the application, there will be no audio.  This is a temporary lock-in that will be hopefully fixed in future versions.  Contrarily, if you have not installed ChucK, there will never be any audio.  You must install ChucK.  It is free!

Record button does not work: If nothing happens when you press the record button, it means that the program did not locate your midi input device correctly.  At the moment, your midi input device needs to in the second slot (after IAC Driver), but in the future, there will be a system of selecting which midi device you want to use.  If you think your device is connected correctly, relaunch the program and try again.

ChucK process still running: (You have to follow these steps every time you use the program) When you press Play or Record, the program launches a ChucK process so you can hear what you play.  It must listen forever or be told to stop, and right now the stop signal is the midi signal [119, 116, x] where x can be anything.  This corresponds to pressing the stop button on my personal midi keyboard, but it may not work for you.  There are a few ways you can stop the ChucK process (which you definitely should do, especially before launching another one via play/record).

Alter which signal ends the ChucK process:

  1. Right click on the application, choose “Show Package Contents”, and navigate to Contents/Resources
  2. Alter Play and Play2: first, uncomment line 160, and save the file.  Then navigate to Contents/MacOS and launch the process in that folder.  You will see MidiStochaster like normal along with a Terminal window where some statements will appear.
  3. Press Play.  Now, every time you hit a midi note on your controller, you should see its values printed in the Terminal window.
  4. Close MidiStochaster, and kill ChucK from the Terminal as described below.
  5. Navigate to Contents/Resources again and alter Play and Play2: Re-comment line 160, and change line 161 to check for the midi notes you want it to exit on.  Save the files.

You can also kill the ChucK process via the command line:

  1. Open Terminal.
  2. Type “ps -e | grep chuck” and press enter.
  3. You will see a list of processes that are running that have chuck in their name.  Each one has a process ID to the far left.
  4. For each one that isn’t “grep chuck” (since it ended when it finished displaying the processes), type “kill processID” except substitute in the actual process ID for processID, and press enter.
Advertisements