Re: [Musickit-users] Saving to file
Brought to you by:
leighsmith
From: Matthew C. <cal...@ma...> - 2003-12-14 06:11:02
|
Hello, I've searched high and low through the docs, but I'm unable to find the=20= passage on looping you mentioned. I thought I could figure it out just=20= from your description, but I still haven't been able to get it working.=20= I registered my NSDocument subclass as my MKScorePerformer's delegate,=20= and implemented a performerDidDeactivate method. =46rom there I'm = calling=20 [myScorePerformer activate] and [MKConductor startPerformance]. This=20 does loop, but not cleanly, and it crashes when I try to quit, so I'm=20 obviously doing something wrong. Any ideas? Also, is it necessary to do something more than this: midiInstrument =3D [[MKMidi midi] retain]; if (!midiInstrument) { NSRunAlertPanel(@"My App", @"Default MIDI driver is=20 unavailable.", @"OK", nil, nil); return self; } [midiInstrument open]; in order to prepare a MIDI device to receive output from my=20 application? If I open up SimpleSynth and then my app, when I hit the=20 open method a dialog pops up saying "Music Kit: MIDI port is=20 unavailable. Perhaps another application is using the port." Then I get=20= the same error when I send run to my MKMidi object. No other MIDI=20 devices are connected, though. The clue is that if I open up MidiKeys=20 and send some events to SimpleSynth, then SimpleSynth will thereafter=20 respond to my app. What sort of initialization might MidiKeys be doing=20= that I'm not doing? Thanks again, Matt El Tuesday, 9 December, 2003, a las 04:11 PM, Leigh Smith escribi=F3: > I don't see anything that stands out to me as being a problem. I would=20= > confirm the path of the file you are trying to write with NSLog(). Try=20= > printing out the MKScore instance (using the debugger or NSLog()). > > Certainly score file (ASCII, not binary/optimized) writing worked the=20= > last time I tried it and it has been fairly heavily exercised in the=20= > last year. > > As for looping MKScores being performed, there is some description on=20= > the mechanism in the Concepts manual under Performance. I haven't done=20= > this myself, but generally you should set the conductor to not stop at=20= > the end of the note stream and you want to set a delegate to be=20 > informed when the MKPart or MKScore has reached the end of the note=20 > stream, again using a message to MKConductor. If I get some free time=20= > I'll see if I can dig into the documentation myself. > >> I'm still using MK 4.5.3 on 10.2.8, if that makes any difference. > > I assume you meant 5.4.3. I don't remember anything changing from=20 > 5.4.3 to 5.4.4 in score file writing (you can check the ChangeLog=20 > accessible off musickit.org). > -- > Leigh Smith > mailto:le...@le... > http://www.leighsmith.com > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for=20 > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys=20 > admin. > Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick > _______________________________________________ > Musickit-users mailing list > Mus...@li... > https://lists.sourceforge.net/lists/listinfo/musickit-users > |