[CM] portmidi

Rick Taube taube@uiuc.edu
Mon, 2 Jan 2006 14:24:06 -0600

sorry i fixed this already (today) in rev 1.3 of midishare.lisp. the 
error happens because the most recent cffi finds two bugs in my api 
that eariler cffi versions did not find

cvs is already updated but it may take several hours to migrate to 
anonymous cvs access. at that point if you have already installed it 
via cvs you do:
	cd /path/to/midishare
	cvs update
otherwise first login to cm's sourceforge cvs and then do
	cvs checkout midishare

On Jan 2, 2006, at 2:12 PM, Johannes Quint wrote:

> Am 02.01.2006 um 21:00 schrieb Rick Taube:
>>> (the whole thing - audio midi setup - seems not to work with the 
>>> quicktime synth,
>>> bad for me, because i've no external synth in the moment, but this 
>>> is no cm problem...)
>>> thanks for your quick answer, johannes
>> for access to quicktime you can use midishare instead of portmidi 
>> (midishare has built-in quicktime support). after installing 
>> midishre, use their msDrivers app to assign an output port to 
>> Quicktime, then quit msDrivers and test your port connection with 
>> msConnect. Once you know you can play quicktime with msConnect, first 
>> quit and then start CM and do:
>> 	(use-system :midishare)
>> If the midishare port number for Quicktime is higher than 0 you will 
>> access it by setting  midi :channel values greater than 15.
>> for example, if QT is midishare port=0 then use :channel 0-15, if 
>> port=1 using :channel 16-31, port=2 is :channel 32-47
>> and so on. For example assuming you want to send to channel 0 of port 
>> 1 do:
>> output (new midi :time (now) :channel 16 ...)