stereo's picture

[Audio] AudioContext initialization fails on openSUSE linux

Project:The Open Toolkit library
Version:0.9.8
Component:Code
Category:bug report
Priority:minor
Assigned:Unassigned
Status:closed (invalid)
Description

I used the OpenTK 0.9.6 in my application. And I had a serious problem with sounds through OpenAL on openSUSE . After my changes, the initialization of sound will run and sound is playing on openSUSE Linux!.
I attached modified files for OpenTK 0.9.8

I would like also to exploit the SoundData class in my application but at present I cannot. I added the simple modification of this class which gladly I would see at the standard OpenTK library.

AttachmentSize
linux_sound.zip10.9 KB

Comments

the Fiddler's picture

#1

I cannot reproduce this on Ubuntu amd64 with OpenAL Soft. I will test on openSUSE once I get VirtualBox working again.

the Fiddler's picture

#2

Status:open» confirmed

I can reproduce this on openSUSE 11.0. It seems they still ship with OpenAL 0.0.8, which is broken in too many ways to count (for example, throwing an 'OutOfMemory' on initialization, which stops AudioContext from working).

the Fiddler's picture

#3

Title:sound initialization on openSUSE linux» [Audio] AudioContext initialization fails on openSUSE linux
Inertia's picture

#4

Priority:normal» minor

I'm interested whether the new&improved^TM AudioContext handles this correctly. Can you please run this diagnosis app and either c&p or attach the output?
http://www.opentk.com/files/AL%20Diag%20v2%20Debug.rar

The best course of action would be notifying openSUSE developers about the outdated driver, so they can update to OpenAL 1.1 though. (Afaik other distributions just did that)

Priority changed to minor, because it's an ancient driver.

the Fiddler's picture

#5

Can someone please test whether this issue persists in OpenTK 0.9.9-1 or newer?

the Fiddler's picture

#6

Status:confirmed» closed (invalid)

I am going to close this as invalid. If someone can confirm that the problem persists with OpenTK 0.9.9-3 or higher, please reopen the issue.