Hi, > I wrote a set of patches once, that only pulled sound events once per > tick. (ie 60Hz). Make that *delivered*. It would leave things on the > queue so that delivery would be spaced out. Should I revive that? Sacrificing synchronity on a small scale to allow the code to process each queue event... No, I'd rather leave it the way it is now. It'd only help with bad coding style in SCI scripts (AFAIK ATM only a potential issue with fan games), and, in conjunction with ill-placed Wait() calls, could delay events by a significant amount of time. llap, Christoph
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Lars Skovlund
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
