I'm trying to get the first OpenAL demo/lesson working (the converted SimpleStaticSound from www.devmaster.net). However it references ALut.alutLoadWAVFile, which doesn't appear to be in the standard Joal build, nor is it included in the lesson download.

I can only assume that this has been replaced in some way by the WAVLoaderand WAVData classes, and the lesson hasn't been updated However I can't figure out how to actually get AL to use the WAVData in the example. Anyone any suggestions?

Edit: Actually theres much more thats broken it seems, ALut is also used for initialisation and shutdown. Anyone have a *working* example of Jogl that I can see?

I found ALut in the joal.jar included with the Lesson01 download. After moving it to my ext directory and removing all other traces of a joal.jar from my classpath, I was able to get it to croak at me. I don't think the sounds I heard were what was intended. I haven't tried again since OpenAL 1.0 was released.

Note, don't even have the same jar in two separate directories in your classpath. That causes an exception outside the vm.

ALut has been added to the CVS tree. Not sure how it ended up missing, but it's there now. I apologize for not spending more time on the project but have been pulled in several directions recently. Any assistance with debugging the code would be greatly appreciated. :-/

I went ahead and did a clean download and install of the demos and they all sound like their working on the dev machine where they were created. This shouldn't be too surprising, but I wanted to make sure that there wasn't anything in my classpath, path or otherwise that might not be in the downloaded zip file.

Two questions that will help in solving this:

1) What configuration of hardware/OS/audiocard are you using?

2) Do you get the same result if you unpack lesson01 into a new directory and run "ant run" from the command prompt? (Make sure no other instance of joal is your classpath or ext directory before trying this.)

It may be that you're running in an environment that hasn't been tested, in which case knowing what you're running will help me track down the problem and get it working for your system.

It may also be the case that one or more bug fixes or changes to the build.xml have introduced an incompatibility with the code in the lessons, in which case they'll either need to be updated, or a new bug will need to be identified and fixed.

In either case, any information you can provide in answering these questions will be greatly appreciated.

I'd just like to remind everyone that if you do encounter issues with JOAL (or any of the other APIs) to PLEASE file a bug report with the Issue Tracking tool provided on the site. So far, only two bugs have been reported, both of which have been fixed, and neither of which has been re-opened.

Unlike JOGL and JInput which have both been in devlopment for some time, JOAL was written from scratch just weeks before it was released in order to get it into the hands of the community as quickly as possible. As a result there was minimal testing done outside the specific configuration of the development machines.

It seems that now that people have gotten up to speed on JOGL they are beginning to use JOAL, which means that there will be many new issues discovered as people try the APIs on different platforms and in different applications. The good news is that as issues are reported, addressed and rectified we'll begin moving much more rapidly toward a stable release.

While I fully appreciate that JOAL may be extremely buggy right now, the only way it's going to improve is if people actually file their complaints, so PLEASE go ahead and do so. I promise you won't hurt my feelings.

As it is now I had to disable sounds in Wurm totally because Joal only worked on about 1/3'rd of all machines now. In other cases, it ranged from throwing an exception to causing the os to freeze.I was using some really strange binaries though, taken from one of the demo apps, and only the windows .dll

Hmm.. That's just it. There isn't currently a "stable" build of any of the core APIs, just nightly builds reflecting the current state of bug-fixes. We are in the process of putting together a release schedule and set of release criteria in order to get to a stable release ASAP, in the meantime we need to get bugs reported in as much detail as possible (preferably using the Issue Tracking tool on the site) so we can get something we can call a truly "stable" release.

/me kicks the forum software and mumbles about email notification not working...

I currently have a bunch of other things that need attention, as well as a list of bugs that need fixing on my project before I can even think of adding any new ones so it might be a while before I can give this a proper test again. I'll try and give the new builds a test soon though.

Yes. This should represent the state of the JOAL (and other binaries) as of Friday night's build. A note: ALut.class which was added on Friday, did not make it into the most recent build. If it is still not there after tonight's build, there may be a problem with the automated build process, in which case I'll need to look into what's going on. If there is a problem, I should be able to rectify it within the week.

Okay. Turns out there was a problem with the build machine which has now been fixed. The binaries that are currently up there represent the most current version of JOAL

I haven't had a chance to update the lessons zip files yet, but I have tested the newest joal.jar and joal.dll with the lessons (by replacing the respective files) in the dev environment and they're still working (here at least)

I'll try to get the lessons updated ASAP, in the meantime you can try replacing the joal jar and dll with the new binaries and see if you get any better results.

EDIT: Oops. While fixing one bug, uncovered another which caused lesson 1,2 & 3 to crash (but not 5) I've sinced fixed the problem and the lessons are now all *really* running in the dev environment. The change is in CVS now and should show up in tonight's nightly build. Sorry for the confusion.

On a related note. if people were experiencing crashes when calling alcOpenDevice(null), that should be fixed now. This may also account for the lessons crashing under Linux. Please let me know if you're still experiencing difficulty with this call.

Also, I'm not sure when after midnight the nightly builds get made so, if you're working from the build, you may want to check to see that the files (in the archive) are dated 11/18/2003 and not 11/17/2003 as the 11/17 build has a serious bug in it.

Sorry folks. The check-in with the fix never went through as Sun's proxy server apparently went down while I was committing the file. I've put the fix in so you can either get it from CVS or wait for tonight's build. Once again, I apologize for the inconvenience.

I believe the check-in for the updated tutorials did go through. If people are still getting alutInit() crashes with the newest version of the tutorials, please let me know, and I'll recommit the files.

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!

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org