Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Problems with CoreMidi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problems with CoreMidi

Subject: Problems with CoreMidi
From: Stéphane Letz <email@hidden>
Date: Wed, 9 Jul 2008 11:22:33 +0200

Hi,

Our CoreMidi code does the following:

Open in a separated thread (so that NotifyProc get called in the separated thread)

gClient = MIDIClientCreate(..., NotifyProc, );
gInPort = MIDIInputPortCreate(...);
gOutPort = MIDIOutputPortCreate(...);

CFRunLoopRun();

Close:

MIDIPortDispose(gOutPort);
MIDIPortDispose(gInPort);
MIDIClientDispose(gClient);

Il seems that Close does not correctly free resources, since if another Open is done right after we get and error calling MIDIClientCreate:

*** CFMessagePort: bootstrap_register(): failed 1103 (0x44f) 'Service name already exists', port = 0x300b, name = 'Apple MIDI Client'

This behaviour seems new with 10.5, tested here on 10.5.4

Any idea of what is wrong?

Thanks

Stephane Letz

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



Prev by Date:
Re: A simple 'Device Through' app (need some help).

Next by Date:
Re: How to Control App Crashing

Previous by thread:
Re: Saving a MIDI/SMF file: How?

Next by thread:
AUNetReceive property

Index(es):

Date
Thread