ECI command timing limitations
Joel Roth <[email protected]>
| Newsgroups | gmane.comp.audio.ecasound.general |
|---|---|
| Message-ID | <20110930062923.GA16728@sprite> |
Hello list, I'm wondering if Ecasound buffers ECI commands it receives, or if there are any timing limitations. The background is that I have a user report of some troubles with Nama related to the solo function. Solo generates a series of commands (c-select, cop-select, copp-select, copp-set) and repeats this based on the track count. Other ECI commands get sent periodically to check on the Ecasound engine status. I have assumed that the socket send and receive interactions are atomic and that Ecasound isn't easily overwhelmed, however this report prompts me to inquire further. The issue is also relevant as Nama sometimes issues command bursts, for example tapering the volume level on transport start/stop. Thanks, Joel -- Joel Roth ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Ecasound-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecasound-list