Wannabe Tsotsi wrote: > Thanks Yair and Hannu, > > > Vmix "feeds" silence to the device when any of the client engines is > > opened. However this should not cause more than about 300 > > interrupts/second. > > I've built and installed OSS 4.0 build 1016 on my stable platform and > the same simple test program which opens /dev/dsp for 1 second > repeatedly generates 384 hdaudio0 interrupts per second. > > Would you expect double this interrupt rate if 2 client engines were open > simultaneously ? > No. The interrupt rate will be the same regardless of the number of open client engines. > Would it be feasible to configure/modify the rate at which silence is fed > to the device, low quality silence ? > 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. > Any other method of reducing the hdaudio0 interrupt rate when audio is > quiescent while still using vmix ? If no application has vmix opened then there will be no audio play/record interrupts. There will be unnecessary interrupts only when an application has the device opened but it has not started the actual play/record operation yet. This situation is very rare.
If you are getting interrupts even when none of the vmix engines is open then this is caused by the other devices sharing the same interrupt line. The hdaudio device may also cause some other interrupts (than audio play/record). However I have not been able to see this in any of the hdaudio systems I have. Does the interrupt count reported by ossinfo -d keep increasing even when there are no applications using the device? Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
