Your email was sent to musickit-developers from an unsubscribed address
which redirects into the moderator list which is used to catch spam
from being sent to everyone on the list. I only just picked that your
email wasn't spam. Sorry for the delay in replying.
> when using MK 5.4.4 and calling [anMKScore writeMidifileStream:s] this
> produces no note-offs.
> In previous versions it worked fine.
I don't recall fixing such a bug, but this may be a symptom of a deeper
fix in MKNote. It may be worth checking the CVS log for MKScore to see
if anything was done. Otherwise if you supply a runnable example, I
could test it here. Failing that, I'll attempt to test this in the next
couple of days.
> Probably this is fixed allready in the CVS, but I cant compile it,
> because each time I look at it, the MK depends on a new library.
It's true that the CVS version of the MK now depends on a library (HIP)
for MP3 decoding that is yet to be released by LAME. I have some
patches that I have now managed to get into a form that would be
acceptable for the LAME maintainers and I will be submitting that
together with a request that they produce a downloadable source
distribution. Otherwise I'll provide one on the MusicKit site. I hope
to get this out very soon.
> Is there a way to configure the building of MusicKit.framework in a
> way, that all the sound stuff is not needed?
Generally you can expect the MusicKit framework to use more of the
SndKit in the future. I have started work gutting MKOrchestra such that
it becomes a SndStreamClient subclass in order to do native synthesis.
The CVS version of the MusicKit now has an MusicKit.xcode project in
the top level directory that builds the distribution including
Frameworks, Palettes, Tools, Examples and Applications. It does not
build every example and application, I hope to have that tackled once I
get the HIP patches out.
> I just use MKScore, MKPart, MKNote and Midi- and Score-In/Output.
I would suggest you create your own subset project to build these
classes, although there are a number of other source files that are
required, including classes such as MKNoteReceiver and MKNoteSender.
While it's possible to build subset frameworks which do not include the
entire collection of classes, this just introduces more work
determining what that collection should have in it, i.e.
MKTuningSystem? MKNoteFilter? Since this is an application specific
requirement, it would be better if application developers chose to
adopt their own subset. Alternatively, they could help me smooth the
installation process so we have an easier system to install.
> It would be nice to have a more decoupled build process with #ifdefs
> or Objective-C categories for dependencies on other libraries or other
> runtime configuration means, rather than producing lots of link
I do recognise that the current work building the MusicKit is tough,
although in my defence, the number of libraries that the MK relies on
is substantially smaller than many more widely used open source
projects (e.g gnumeric or GNUStep) and that I do provide a series of
links on the web page to the libraries necessary to install. It would
be nice to have an autoconf process that produces appropriate subsets
of the MusicKit depending on the libraries present (i.e. not compiling
SndMP3 if HIP is missing) although this is tough to do with Xcode. I
will look at this in the future though, as I do want to make the
MusicKit more accessible. The forthcoming 5.5 should make it much
easier to work with and addresses a massive number of
> Anyway, thanks for Your work Leigh! :-)
Thanks for your feedback!
Leigh M. Smith