Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: Frederic Bouvier wrote: What is the right way to exit the main loop, rather than just calling exit() ? If there is no other option, we need an atexit call. I put alutExit() before exit(), with a sample playing from a previous run and the sound created by this instance are shut, the program stop as expected and my crazy sample is still playing. Rebooting once again... Fred, I added an atexit() function to CVS that deletes the global class. This should then also delete the soundmgr class which will cause alutExit() to be called. This might also give us the opportunity to hook in the SDL cleanup function as well. That works well, either by asking to exit in the menu, or closing the window. Destroying the samples kill the sound, alutExit just cleaning a quiet process. I'll have to remember not to kill fg or interrupt a debugging session. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] OpenAL update
I am going to commit my OpenAL changes to SimGear and FlightGear this afternoon. I haven't seen even one negative comment on OpenAL since I first brought this topic up several days ago ... so hopefully everyone is on board with this change. I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the configure script assumes we want to link with -lopenal, but I don't expect this to work right for every platform. I expect there may be a couple days of head aches here while we get these platform dependent differences ironed out. Please be patient! Thanks, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL update
I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the I didn't see a CygWin platform listed for OpenAL on their web site (openal.org). I also didn't see mention of Cygwin here: http://developer.creative.com/landing.asp?cat=1sbcat=31top=38. I wonder if I simply download the source if I can compile it ... there's an experiment waiting for a developer. I'd do it, but the weather is turning nice (http://instacam.com/instacamimg/KEMAH/KEMAH_s.jpg - just up the street overlooking Galveston Bay, tonight's dinner destination), so I'm going outside with the family. This OpenAL thing has got me a little uneasy, being a CygWin user, but the benefits look real good. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: I am going to commit my OpenAL changes to SimGear and FlightGear this afternoon. I haven't seen even one negative comment on OpenAL since I first brought this topic up several days ago ... so hopefully everyone is on board with this change. I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the configure script assumes we want to link with -lopenal, but I don't expect this to work right for every platform. I expect there may be a couple days of head aches here while we get these platform dependent differences ironed out. Please be patient! I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. Regards, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. Hmmm, I wonder if I'm not doing the exit stuff correctly. This problem doesn't happen on Linux, but linux maybe better at cleaning up wayward processes? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. It doesn't look like the sound manager destructor is ever getting called. This should happen inside of the globals destructor, but that is never getting called either. I don't think any one has paid much attention to cleanup and exiting from FG, but we may need to address this now. Do we need an atexit() function that will clean things up for us? Curt. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. Hmmm, I wonder if I'm not doing the exit stuff correctly. This problem doesn't happen on Linux, but linux maybe better at cleaning up wayward processes? The OpenAl Programmer's guide says one must call alutExit before exiting. alutExit is in the destructor of SGSoundMgr, but AFAICS the manager is not destroyed at shutdown time. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: Curtis L. Olson wrote: Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. It doesn't look like the sound manager destructor is ever getting called. This should happen inside of the globals destructor, but that is never getting called either. I don't think any one has paid much attention to cleanup and exiting from FG, but we may need to address this now. Do we need an atexit() function that will clean things up for us? What is the right way to exit the main loop, rather than just calling exit() ? If there is no other option, we need an atexit call. I put alutExit() before exit(), with a sample playing from a previous run and the sound created by this instance are shut, the program stop as expected and my crazy sample is still playing. Rebooting once again... -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL update
I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the configure script assumes we want to link with -lopenal, but I don't expect this to work right for every platform. I expect there may be a couple days of head aches here while we get these platform dependent differences ironed out. Please be patient! Has anyone seen reference to the use of OpenAL with CygWin anywhere? I downloaded it, and tried configuring the linux subdirectory to build under cygwin - no joy (yet, at least). The Windows directory is so far a bit of a mystery, but there is no mention of cygwin there, either. I did a google search but so far have not found the words cygwin and openal together in a meaningful web page. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Jon, I did a google search but so far have not found the words cygwin and openal together in a meaningful web page. http://cvs.seul.org/cgi-bin/cvsweb-1.80.cgi/games/openal/linux/configure.in This looks like it could be the openal cvs source tree (I don't have it to check). If you search for cygwin on this page it says 'fixes for cygwin builds, that might mean someone has tried it at some stage. Chris. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Frederic Bouvier wrote: What is the right way to exit the main loop, rather than just calling exit() ? If there is no other option, we need an atexit call. I put alutExit() before exit(), with a sample playing from a previous run and the sound created by this instance are shut, the program stop as expected and my crazy sample is still playing. Rebooting once again... Fred, I added an atexit() function to CVS that deletes the global class. This should then also delete the soundmgr class which will cause alutExit() to be called. This might also give us the opportunity to hook in the SDL cleanup function as well. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
