StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7167330
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-08-23T20:47:45.557
FavoriteCount
0
LastActivityDate
2011-08-23T20:47:45.557
LastEditDate
LastEditorUserId
0
OwnerUserId
378418
ParentId
7149835
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
As Dan Ray said, <code>NSTimer</code> and <code>NSThread</code> are not reliable for precise timing. If I were you, I would use an <a href="http://developer.apple.com/library/mac/#documentation/MusicAudio/Conceptual/AudioQueueProgrammingGuide/Introduction/Introduction.html" rel="nofollow">audio queue</a> - it will request buffers of audio through an input callback, and you will fill them. Provided you respond promptly, it will request and reproduce these buffers at exactly the hardware sample rate, so you can do some simple calculations to figure out the timing of your taps and fill each buffer from your file or from samples stored in an array or vector. You'd fill it using <code>AudioFileReadPackets</code> if you choose to go straight from your file. This will be a little more work but it's much more versatile and powerful. You can use audio queues for live synthesis and processing of audio, so their timing is perfectly precise as long as you meet their deadlines. If you're careful about processor usage, you could have a tap sound every few milliseconds with no issue. Take a look at the <a href="http://developer.apple.com/library/ios/#samplecode/SpeakHere/Introduction/Intro.html" rel="nofollow">SpeakHere</a> sample application to get started with audio queues. <a href="http://developer.apple.com/library/ios/#documentation/MusicAudio/Conceptual/AudioUnitHostingGuide_iOS/Introduction/Introduction.html" rel="nofollow">Audio units</a> are also useful for this sort of thing, and you can provide data to them through a callback, but they take a little more setup and have a steeper learning curve. Good luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAccurate repeating iPhone sounds
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLuke
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAccurate repeating iPhone sounds
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COThanks for all the good input. As it turns out, simpler is better. I was already aware of the short comings of the NSTimer, so my threaded timing loop I think will suffice.
 singulars
 PostPostId
 PO
 UserUserId
 USCal30

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.