Wannabe Tsotsi wrote: > Thanks Hannu, > > > No. The interrupt rate will be the same regardless of the number of > open > > client engines. > > I've since verified this is the case, same interrupt rate regardless > of number > of open client engines. > > > This is not possible. The interrupts are driven by the actual hardware. > > The driver level interrupt handler calls vmix which feeds audio to the > > device if any of the applications are running. It is not possible to > > change the interrupt rate (fragment size of the actual device) on fly. > > In my ignorance of things OSS, audio codecs, etc, let me ask some dumb > questions. > > Why are these (feeding silence) interrupts generated when using vmix > but not > when vmix is disabled? Why does vmix need to feed silence when osscore > does not ? Vmix needs to work in this way because starting/stopping the device every time some application starts/stops makes things too complicated. > If I disable vmix and accept a single audio stream no interrupts > (well, one!) are generated while the audio device is open() but with > no audio > playback or recording. This is my apps quiescent state. Maybe your application should close the device when it doesn't use it.
Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
