Yair K. wrote: > > - Restoring vmix loop devices. Without vmix_numloops, quite a few cards would > not be able to record "what-you-hear" (ac97 devices have 'vol' recording > source, everything else will fail?). > Added back to osscore.conf. > - vmix default device autoconfig can be improved: > In 4.0, there were two methods for setting default card: > A. Linking to /dev/dsp > B. vmix_masterdev (Though autodetect usually worked). > If vmix is integrated to osscore, can't it be made so that the device linked > to /dev/dsp always gets a vmix attached? > Or maybe now that vmix can dynamically allocate devices, we could have vmix > attach to all outputs (except high end devices which can disable it, as they > do now?), but have it create zero engines except on default output? > In v4.1 the vmix subsystem itself doesn't attach to any of the devices. Instead the driver will call vmix_attach_audiodev() for the "primary" device. Some drivers may decide to call vmix_attach_audiodev() for the other devices too.
The kernel space code doesn't know which device is pointed by /dev/dsp. However typically it should be the primary audio device of the main sound card. > - Getting USB hotplugin working correctly under Linux (w/o ossdetect -d) > would be apperciated by users. > Unfortunately the devfs feature was removed from Linux. The way how device naming works in OSS (/dev/oss/<driver>/*) can only work properly on top of devfs. Under Linux the ossdetect -d command needs to be run after a new device is added. It reads /proc/opensound/devfiles and (re)creates all the device files listed in it. In addition the ossdevlinks command needs to be run so that the old style /dev/dsp# links get created. Maybe somebody could hack the hotplug system of Linux so that it runs "ossdetect -d;ossdevlinks" autmatically after a new USB sound card is added. Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
