No AL object created

Java Sound & OpenAL
#1

Ok, latest binaries and source as of now, and ALut is in there so thats one problem fixed. However now the first tutorial just stops dead with a NPE almost straight away.

It seems that the ALFactory.getAL(); just returns null straight away. Annoyingly trying to step though this ends up with line numbers not being found so its tricky to figure out where it goes wrong. Currently i’m seeing it go into ClassLoader.findNative(ClassLoader, String) in the middle of ALFactory.init(String[]) and eventually find ‘something’ on its third attempt. Almost straight after than the whole lots returns and i’m left sitting with a null AL object.

Of course this is all with lesson 1, so it blindly goes and calls ALut.alutInit, leaving the follwing console output:
Go TEAM!
Entering alutInit()
In alutInit(): Device Name = MMSYSTEM
Entering alcOpenDevice()
In alcOpenDevice: Device Pointer = -2116564104
Exiting alcOpenDevice()
In alutInit(): Device = net.java.games.joal.ALC$Device@81d7cb78
Exiting alutInit()

System is an AthlonXP 2600+, 512Mb ram, sound card is a PCI Creative SoundBlaster Audigy. Other small (native) AL test programs work fine.

#2

Okay this is a new one. The nightly builds are created with optimize turned on, so you lose the line numbers. If you build from the source yourself you should get them.

What OS are you running? (XP, 2000 or something else?)

The most frustrating thing here is that on several systems, including the few I’ve managed to test on personally, we’re running fine, while on a number of others we’re seeing crashes that are consistent on one machine, but different from the failures we’re seeing on other machines. Grrrrr… :-/

I’m going to put together a few pure native tests and put them up on the project page for people to run. Hopefully, these issues are all related and we’ll be able to track them down soon.

#3

[quote]Okay this is a new one. The nightly builds are created with optimize turned on, so you lose the line numbers. If you build from the source yourself you should get them.
[/quote]
While building it myself is possible solution, can we get the optimise turned off? At least until Joal is actually stable? I’m getting somewhat tired of jumping though hoops just so I can attempt to debug someone elses code. >:(

Forgot to list the OS, its a WinXP machine.

#4

Can do. I’ll send an email to the buildmistress asking her to turn off optimize for joal until we’ve ironed this out.

EDIT: I just sent Oiching the message. I doubt she’ll to get to it before Monday, but I assume as of Monday night’s build, optimize will be turned off.

#5

In the meantime, I’ve added the latest version of the code, with debug turned on, along with a test class here:

http://joal.dev.java.net/test.zip

try unpacking it and running:

ant clean -Djava.library.path="./bin" run

from the command line.

I don’t anticipate this fixing the crash, but it should give you the line numbers. Let me know what you get.

#6

Line numbers and debugging working now, but theres not much more that I can tell you other than the output:

net.java.games.joal.OpenALException: Could not load ALC function pointers.
at net.java.games.joal.ALFactory.init(Native Method)
at net.java.games.joal.ALFactory.initialize(ALFactory.java:61)
at net.java.games.joal.ALFactory.getAL(ALFactory.java:88)
at com.vecript.test.openal.SingleStaticSource.main(SingleStaticSource.java:132)

#7

hmm… I updated my sound card drivers (a whopping 13mb) and it works fine now :o They were new a couple of months ago, but the ‘latest’ seem to have fixed things :slight_smile:

#8

two down, 774 platform configurations to go…

#9

I’ve added a poll to the forum in an attempt to get an assessment of how stable the current version of JOAL is on different windows platform configurations. Please follow the instructions on post #1 of the poll before voting. Your participation in this survey will be greatly appreciated, and go a long way toward getting us to a stable release. Thanks in advance!

#10

Might be useful if we had both release and debug builds of these libraries - both native and jar.

#11

[quote]Might be useful if we had both release and debug builds of these libraries - both native and jar.
[/quote]
Yeah. It should be easy enough to set up in Ant, but I should talk to our buildmistress before making any changes of this nature.