1 reply to this topic

[A_M]

So then, hello new forum. I did a search to see if anyone had posted about this, and didn't find anything, so I suppose I'll ask.

Furthermore, if anyone can link me to a resource on Interrupt level programming, that might help...

I'm building an audio engine, which means a lot of calls from my audiointerface to request more audio data. I'm making it very streamlined, so that if a user makes a change in the song he's (or she's) working on, there wont be more than a short pause in the audiostream.

Now, I understand that an interrupt will stop the program and start working on the audiostream, but what confuses me is that sometimes the windows loop will interrupt the interrupt from the audiointerface. This can cause a huge error, stalling the program.

I did a brief work around (the message loop pauses until the audiointerface is idle), but I don't trust that it's stable. So, can anyone give me a few pointers on scheduling of interrupts vs a windows message loop?

I hope this question isn't to N00b or obscure...thanks in advance for your help..

[A_M]

Hrm, it looks like I've inadvertently started multi-threaded programming, and could resolve this with a TThread object or two...

Nevermind, perhaps.