Hi Yair K., > I didn't ask for that. But there are some things that can be done to make > life easier for users.
of course ;) > ALSA works only on Linux. FreeBSD uses OSSv3 (there's disabled support for > OSSv4) and OpenSolaris will use OSSv4. If they want to be cross-platform > (and not 'Linux-only'), they should add support regardless of "ALSA vs OSS > propaganda". Well, time will tell .. I hope the KDE people will one day review my post on their devel mailing list and won't hold it back forever. > > Neither in KDE3 nor in KDE4 for example is KDE able to > > control the volume properly. While it's not that hard to solve the issue > > in KDE3, KDE4 entirely depends on information gathered by HAL - HAL does > > not support OSS4 either, so KDE4 doesn't detect OSS4 devices at all. I'm > > currently talking with the devs about possible solutions (though my > > proposals won't likely either bother or please them too much). > Is there a public bugtracker for this discussion? The problem here, I don't know where to put those bugreports. I didn't try asking the HAL-guys yet, but the problem is: What sense does it make to ask if you already know the answer? Well, I'll ask anyway then... I would even like to work on fixing some of the issues, but it's too much for just one person. > I've never had this problem. One thing I did notice is that if another > program connects to the same engine after a program disconnected, then it > gets the last volume, while if the previously disconnected program > reconnects afterwards, it get the maximum volume from the newly used > engine. (In short, the volume is saved per-engine, but not per-program, > which seems less useful to me) > > I have a diff to ossxmix in the works, which lets it store specific volume > for programs. ossxmix reads an ini file into memory, when it detects a > program starting, it sets its vmix volume to the pre-set value. Making it > work for temporary settings is easy as well. These bugs can than be > worked-around by setting the respective program volume to maximum. > Alternately, this will allow to drop the "save last vmix volume" behaviour > without losing functionality. You should save those mixer levels per-app and user instead for obvious reasons. But another question here... wouldn't it be enough to just raise vmix volume to maximum upon application disconnection? I assume most apps initially push their volume settings in - correct me if I'm wrong. > > Another more enerving issue happens with libflashsupport.so. Sometimes it > > just makes flash crash (I've no idea how to debug that) although it > > happens rather seldom. Also I _always_ experience some kind of very > > strange and loud initialisation sound when flash is loaded, comparable to > > a completely overdriven amplifier, just for half of a second. This > > problem only happens with flash. > > Maybe the plugin issues are browser related? > (FireFox is broken enough to crash when a plugin crashes. Opera just keeps > going, and I've never had a plugin crash with Konqueror). The browser used is unimportant here.. konqueror(4), firefox - all with the same results. Regards apriori _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
