Open Sound System

I have opened a bug tracking system (Bugzilla) for OSS at http://bugzilla.opensound.com . In the beginning the Bugzilla system will be used in parallel with this user forum and the old tehc support request form on our web site. However sometimes in the future Bugzilla will replace the other methods....

I have made another OSS4 adaption of xmss-1.2.10. These sources are available from http://www.compusonic.fi/~hannu/xmms-1.2.10.oss.tar.bz2 This version is more or less hackish so it's not fully usable. Unfortunately there are all kind of changes in the files related with configure so making a diff w...

This is not an API issue but a problem related just with live/audigy devices.

The API documentation recommends to implement pause/resume by feeding silence to the device or by closing/reopening it.

There is no solution. SB audigy uses three different stereo engines for 5.1 playback. It is possible that they get out of sync if the application stops writing new data to the device. I don't think this problem can be fixed in the future. It can only be fixed by modifying xine to handle pause/resume...

Actually the right place is in kernel/OS/FreeBSD/os_freebsd.c. Change the "int size = 64 * 1024;" line in the beginning of __oss_alloc_dmabuf(). Dropping the "64" to 32 or even 16 should fix the problem. However anything below 64k will break application(s) that assume 64k buffers...

FreeBSD makes only limited amount of DMA memory available for drivers. The sblive driver implements several parallel audio devices. The vmix (virtual mixing) driver adds few more of them and the system will run out of memory. As a workaround you can edit /usr/lib/oss/etc/installed_drivers and to rem...

We tried to use the clone() service but it was not suitable for OSS for several reasons: - The clone entry point doesn't give the open mode (O_RDONLY, O_WRONLY or O_RDWR). OSS uses the access mode to select a device that supports this mode. The stock FreeBSD driver assumes O_RDWR which will not work...

This problem will be solved after the Gnome volume control applet is converted/rewritten to use the OSS 4.0 mixer API. However this is likely to take couple of months.

I recall the exact problem was that the memory should be allocated with ddi_umem_alloc() begore the devmap(9E) interface could be used. I didn't manage to find out if ddi_dma_mem_alloc() is compatible.

Hi,

What is the exact model of the computer?

Best regards,

Hannu