Timers for MIDI
Timers for MIDI
- Subject: Timers for MIDI
- From: email@hidden
- Date: Tue, 26 Jun 2001 12:42:04 -0700
I have s small app that needs to generate timers for itself. I
originally looked
as NSTimer (it's a Cocoa app), but realized this probably wasn't the best
solution. I could preschedule a wakeup to handle the 50-100ms resolution
of NSTimer, but then I came up with a different solution I'd like to
have comments
on.
I decided to create a Clock destination in my app, allowing the user to
specify
either external or internal timing. If it was internal, my app would
attach a port
to it's own clock destination and every processing loop would generate a
clock
event in the future for the next wakeup. My only problem with this
approach
is that nothing prevents another app from also sending events to this
destination,
and my app has no way of knowing where the events received came from.
In the grander scheme of things, I have a suite of small apps that all
allow the
user to specify sources for their input destinations, and a separate app
to connect
sources to real hardware destinations (or Music Devices). So for my
suite of applets,
there is no way a user can connect multiple sources to a single input
(except by using a
merger applet, in which case I assume they know what they are doing). But
for other applications not following this scheme, it could be confusing
to the user.
Is there a way to either:
- Make a destination hidden to anything other than the creating
application?
- Restrict access to a destination.
- Determine who sent what to a destination.
Thomas
----
Hacker looking for work
http://www.tomy.net/thudson/resume.html
http://www.tomy.net/thudson/tools.html
---