> Add the libs to FG, SG does not need them.
>
> Harald.
>
Hi Harald,
Thank you for your reply. I did add the libraries to FG as you
suggested but I still get the same errors. It looks like for some
reason or the other the header files are not being read... for
example the function alGetErro
bass pumped wrote:
Hi,
I'm trying to compile pre-rel-3 in MSVC 7 but i'm running into a
linking problem again. It looks to me like simgear is unable to read
the openAL header files while trying to link. I have put them in the
sound_mngr directory and modified the include statements to read it
Hi,
I'm trying to compile pre-rel-3 in MSVC 7 but i'm running into a
linking problem again. It looks to me like simgear is unable to read
the openAL header files while trying to link. I have put them in the
sound_mngr directory and modified the include statements to read it
directly from there,
> From: Jon Berndt [mailto:[EMAIL PROTECTED]
>
> > I have placed a compiled tarball of yesterdays OpenAL CVS files @
> > http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz
> >
> > you might want to test these against the current FGFS
> before blindly
> > overwriting your currrent instal
Jon Berndt wrote:
I have placed a compiled tarball of yesterdays OpenAL CVS files @
http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz
you might want to test these against the current FGFS before
blindly overwriting your currrent installation
Is this distribution modified for use with C
> I have placed a compiled tarball of yesterdays OpenAL CVS files @
> http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz
>
> you might want to test these against the current FGFS before
> blindly overwriting your currrent installation
Is this distribution modified for use with CygWin as disc
I have placed a compiled tarball of yesterdays OpenAL CVS files @
http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz
you might want to test these against the current FGFS before
blindly overwriting your currrent installation
Norman
___
Flightge
> For Cygwin users, OpenAL needs to be retrieved from this site:
>
> ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz
>
> I placed this file in the /usr directory and untar'ed it, though some
> place it in the
> /usr/local/ directory tree - which might be more appropriate. Some
libra
Jon Berndt
> > In the developers' list archives is the best we have. Cygwin wouldn't
> work
> > at all if it were not for the excellent work by Norman Vine. There's no
> sign
> > of OpenAL being ported to Cygwin at the moment, so this is the best we
> have.
> > We are in constant danger of being
> In the developers' list archives is the best we have. Cygwin wouldn't work
> at all if it were not for the excellent work by Norman Vine. There's no sign
> of OpenAL being ported to Cygwin at the moment, so this is the best we have.
> We are in constant danger of being left behind.
>
> Have you g
Jon Berndt
>
> > Hmmm ... we had to fiddle with it to make it work some months ago ... I
> > forget exactly what we did
>
> This seems really unfortunate for FlightGear - that we have to rely on
> another package
> where some of us have to "fix" the code to work for CygWin users. Is this
> even
> Hmmm ... we had to fiddle with it to make it work some months ago ... I
> forget exactly what we did
This seems really unfortunate for FlightGear - that we have to rely on another
package
where some of us have to "fix" the code to work for CygWin users. Is this even
documented
anywhere?
jon
Jon Berndt
>
> > Jon Berndt wrote:
> > >
> > > I'm finally getting around to reinstalling FlightGear after a hard
> drive
> > > crash a couple months ago. I have this as a place to get OpenAL for
> Cygwin:
> >
> > Try this version:
> >
> > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg
> Jon Berndt wrote:
> >
> > I'm finally getting around to reinstalling FlightGear after a hard drive
> > crash a couple months ago. I have this as a place to get OpenAL for Cygwin:
>
> Try this version:
>
> ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz
>
> Vivian
I got that file. I
Vivian Meazza writes:
>
> Jon Berndt wrote:
>
> >
> > I'm finally getting around to reinstalling FlightGear after a hard drive
> > crash a couple
> > months ago. I have this as a place to get OpenAL for Cygwin:
> >
> > http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
> >
> > Is this still th
Jon Berndt wrote:
>
> I'm finally getting around to reinstalling FlightGear after a hard drive
> crash a couple
> months ago. I have this as a place to get OpenAL for Cygwin:
>
> http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
>
> Is this still the latest/best dist?
>
Try this version:
ft
I'm finally getting around to reinstalling FlightGear after a hard drive crash
a couple
months ago. I have this as a place to get OpenAL for Cygwin:
http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
Is this still the latest/best dist?
Jon
___
Fligh
When Curt introduced OpenAL to fgfs, he wrote[1]:
| 2. The plib sound system was set to play at 8000 hz no matter what the
| sample was recorded at. So a 22000 hz sample wouldn't play at the right
| pitch by default. We compensated in our sound config files for this by
| offsetting the pitch
some coworkers and I have been trying to compile the
latest FlightGear Build (0.9.5pre2). Unfortunately, we
don't seem to be able to download the OpenAl source
code from CVS. After downloading the SDK from
Creative's website, we have not been able to build the
samples they provided. Has anyone had
I noticed that the least bit of extra CPU/Bus activity can cause the sounds to
stutter after our switch to OpenAL. This might be a reason to remain
conservative with our sound files (e.g. 8bit Mono). This is especially
noticable on my system with the 16bit/44khz/Stereo merlin sample with the
Spit
Jon Berndt wrote:
Note you will need a recent Cygwin DLL to use these
this is untested
http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
Norman:
Is this file still online? Cape.com seems to think the site is offline or the file
doesn't
exist. Transient ISP problems?
Maybe this is am alternative:
> Note you will need a recent Cygwin DLL to use these
>
> this is untested
>
> http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
Norman:
Is this file still online? Cape.com seems to think the site is offline or the file
doesn't
exist. Transient ISP problems?
Jon
_
Upgrading to the latest CVS OpenAL from the version distributed with Debian
SID solved my OpenAL problems -- the planes sound great now. Unfortunately,
the voice ATIS is even quieter, so that it's hard to tell that it's even
playing now, much less to make out the individual words.
All the best
Curtis L. Olson wrote:
It sounds ok to me here on my sound blaster live hardware. Can you hear
the morse code beeps, marker beacons, or other sounds ok? Do some
aircraft sound ok, or do all of them sound this way?
The ident codes sound strange also (high-pitched and slow).
All the best,
David
_
David Luff wrote:
On a related note, I believe you had problems with hearing the ATIS voice
due to low volume previously. Do you still have this problem post-OpenAL,
or can you hear it OK now?
I cannot hear the voice at all now, unfortunately.
All the best,
David
__
David Luff wrote:
On a related note, I believe you had problems with hearing the ATIS voice
due to low volume previously. Do you still have this problem post-OpenAL,
or can you hear it OK now?
I haven't checked, because the engine audio is so intolerable (think dental
drill) that I turn it off ri
On 5/24/04 at 10:44 AM David Megginson wrote:
>
>I'm not sure if what I'm hearing right now is an OpenAL library problem or
>a
>FlightGear problem, but it does not sound much like an airplane. The
>sound
>of a plane from inside the cabin is a very low, loud rumbling (or even
>roaring) sound -
Erik Hofman wrote:
No. It can be heard from within the cabin also.
But there is an effect that steps in at higher angles of attack, I'm
just not sure how it really should sound like (I thought the current
effect was quite close) and how to achieve that effect correctly.
I'm not sure if what I'm h
Matthew Law wrote:
On my system (gentoo, SB Live 128) I hear what sounds like the turbine
sample when at high angles of attack/sideslip and bank in the pa28-161.
It's a very strange thing to hear in those situations and had me looking
around at first to find the 'bogey'. Up to now in real fixe
Curtis L. Olson wrote:
It sounds ok to me here on my sound blaster live hardware. Can you
hear the morse code beeps, marker beacons, or other sounds ok? Do
some aircraft sound ok, or do all of them sound this way?
Curt.
On my system (gentoo, SB Live 128) I hear what sounds like the turbine
sa
David Megginson wrote:
For at least a couple of weeks, the audio for the PA-28 or C172 on my
Dell Inspiron notebook has sounded like an angry mosquito dying of
tuberculosis.
I think the problem started about the time of the switch to OpenAL
(which I remember vaguely). I'm using the current Deb
For at least a couple of weeks, the audio for the PA-28 or C172 on my Dell
Inspiron notebook has sounded like an angry mosquito dying of tuberculosis.
I think the problem started about the time of the switch to OpenAL (which I
remember vaguely). I'm using the current Debian sid versions of libo
Jim Wilson wrote:
That reminds me...it appears that there are no "releases" so to speak of
openal. I could only find cvs. Anyone know more about this? Will this be an
issue for our *nix users or do the latest distros all include some form of openal?
I was a little dismayed to discover this t
"Curtis L. Olson" said:
> Josh,
>
> Add /usr/local/lib (or where ever you installed libopenal.so) to
> /etc/ld.so.conf and run ldconfig.
>
> Curt.
On my system the install just didn't do the binding step, but yeah if that
isn't there ldconfig won't work anyway.
Best,
Jim
_
Josh Babcock said:
> Josh Babcock wrote:
> > I just did my first recompile in a few months and everything seemed to
> > build fine including openal, but at runtime I get this:
> >
> > [EMAIL PROTECTED] SimGear]$ fgfs
> > fgfs: error while loading shared libraries: libopenal.so.0: cannot open
>
Andy Ross wrote:
Josh Babcock wrote:
I just did my first recompile in a few months and everything seemed to
build fine including openal, but at runtime I get this:
fgfs: error while loading shared libraries: libopenal.so.0: cannot
open shared object file: No such file or directory
$ ls -l /usr/l
Josh,
Add /usr/local/lib (or where ever you installed libopenal.so) to
/etc/ld.so.conf and run ldconfig.
Curt.
Josh Babcock wrote:
I just did my first recompile in a few months and everything seemed to
build fine including openal, but at runtime I get this:
[EMAIL PROTECTED] SimGear]$ fgfs
f
Josh Babcock wrote:
> I just did my first recompile in a few months and everything seemed to
> build fine including openal, but at runtime I get this:
>
> fgfs: error while loading shared libraries: libopenal.so.0: cannot
>open shared object file: No such file or directory
>
> $ ls -l /usr/loca
Josh Babcock wrote:
I just did my first recompile in a few months and everything seemed to
build fine including openal, but at runtime I get this:
[EMAIL PROTECTED] SimGear]$ fgfs
fgfs: error while loading shared libraries: libopenal.so.0: cannot open
shared object file: No such file or director
I just did my first recompile in a few months and everything seemed to build fine including openal,
but at runtime I get this:
[EMAIL PROTECTED] SimGear]$ fgfs
fgfs: error while loading shared libraries: libopenal.so.0: cannot open shared object file: No such
file or directory
[EMAIL PROTECTED]
Vivian Meazza writes:
>
> I downloaded the most recent CVS version, with the modifications already
> made, and I still get
>
> Config.status: creating \
> .infig.status: error:cannot find input file.
Hi Vivian,
Was this a fresh CVS checkout or did you just refresh
your existing files ?
If the
David Luff helped some more
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> David Luff
> Sent: 28 April 2004 21:18
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] OpenAL
>
>
> "Vivi
David Luff wrote:
> "Vivian Meazza" writes:
>
>
> > Result - failure,
> >
> > I downloaded openal.gz (not openal.tgz) and extracted the archive - no
> > problems as far as I can see.
> >
>
> Are you *sure* that your browser isn't mangling the file extension - it
was a .tgz on Norman's web page whe
Erik Hofman writes:
>
> David Luff wrote:
>
> > You have to admire Curt's methodology - fatally breaking the Cygwin build
> > has certainly created a momentum to fix it, and presumably saved the time
> > and hassle of riddling the sound code with ifdefs!
>
> He has proven to be a good student >:
"Vivian Meazza" writes:
> Result - failure,
> I've downloaded the latest FlightGear, made the changes. Configure reports
> with:
>
Ah, you shouldn't need the src/Main/Makefile.am changes anymore, Curt has added the
libs to configure.ac already.
Remove your src/Main/Makefile.am, recheckout a
"Vivian Meazza" writes:
> Result - failure,
>
> I downloaded openal.gz (not openal.tgz) and extracted the archive - no
> problems as far as I can see.
>
Are you *sure* that your browser isn't mangling the file extension - it was a .tgz on
Norman's web page when I checked 30 seconds ago. One
David Luff wrote:
You have to admire Curt's methodology - fatally breaking the Cygwin build
has certainly created a momentum to fix it, and presumably saved the time
and hassle of riddling the sound code with ifdefs!
He has proven to be a good student >:-D
Erik
__
David Luff gave clear instructions
>
> On 4/28/04 at 10:09 AM Jon S Berndt wrote:
>
> >
> >This was all done under CygWin? Can someone summarize the process?
> >
>
> Yes, under Cygwin. Here goes...
>
> Download Norman's prebuilt Cygwin openal from:
> http://www.vso.cape.com/~nhv/files/fg
Andy Ross writes:
>
> Norman Vine wrote:
> > Unfortunately I do not have the time to support the libraries I port
> > so I do not submit them for inclusion with Cygwin but the official
> > method of doing this is here http://cygwin.com/setup.html
>
> I suspect the OpenAL people should be the firs
Norman Vine wrote:
> Unfortunately I do not have the time to support the libraries I port
> so I do not submit them for inclusion with Cygwin but the official
> method of doing this is here http://cygwin.com/setup.html
I suspect the OpenAL people should be the first ones to contact. I
doubt the C
On Wed, 28 Apr 2004 12:12:20 -0400
"Norman Vine" <[EMAIL PROTECTED]> wrote:
Nor was I, but usually one can find a way to compile Windows
code with gcc but it often requires digging into the depths of the
gnu linker documentation and studying the x86 specific link options
for creating DLLs for WIN
David Luff writes:
>
> On 4/28/04 at 10:16 AM Curtis L. Olson wrote:
> >
> >Cygwin is a little bit different nut to crack. As I understand it,
> >cygwin can link against any .dll out there so in theory it should be
> >able to work with the standard openal SDK.
This is only true for libraries
Jon S Berndt writes:
> >
> >You have to admire Curt's methodology - fatally breaking the Cygwin build
> >has certainly created a momentum to fix it, and presumably saved the
> >time and hassle of riddling the sound code with ifdefs!
>
> This approach works only when there is a solution somewhere.
On 4/28/04 at 10:16 AM Curtis L. Olson wrote:
>David Luff wrote:
>
>>Norman's latest openal build fixes it :-)
>>
>>You have to admire Curt's methodology - fatally breaking the Cygwin build
>>has certainly created a momentum to fix it, and presumably saved the time
>>and hassle of riddling the s
On Wed, 28 Apr 2004 16:00:20 +0100
"David Luff" <[EMAIL PROTECTED]> wrote:
On 4/28/04 at 9:04 AM Jon S Berndt wrote:
On Wed, 28 Apr 2004 13:29:08 +0100
"David Luff" <[EMAIL PROTECTED]> wrote:
For those using CygWin, it's fatal at the moment.
Norman's latest openal build fixes it :-)
You hav
On 4/28/04 at 10:09 AM Jon S Berndt wrote:
>
>This was all done under CygWin? Can someone summarize the process?
>
Yes, under Cygwin. Here goes...
Download Norman's prebuilt Cygwin openal from:
http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
and place it somewhere, in this example in your
David Luff writes:
>
> On 4/28/04 at 10:09 AM Norman Vine wrote:
> >
> >I have rebuilt the opeal dll and replaced the one on my site
> >http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
> >
> >This should export the required alut* funcs and it includes
> >the Makefile I used
> >
> >Note you will
David Luff wrote:
On 4/28/04 at 10:09 AM Norman Vine wrote:
I have rebuilt the opeal dll and replaced the one on my site
http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
This should export the required alut* funcs and it includes
the Makefile I used
Note you will need to use my headers instea
David Luff wrote:
Norman's latest openal build fixes it :-)
You have to admire Curt's methodology - fatally breaking the Cygwin build
has certainly created a momentum to fix it, and presumably saved the time
and hassle of riddling the sound code with ifdefs!
In my own defense, all indications
On Wed, 28 Apr 2004 15:57:55 +0100
"David Luff" <[EMAIL PROTECTED]> wrote:
Norman, this compiles, links, and produces the expected sound from
FlightGear :-)
Many thanks for sorting this - I certainly couldn't have got it
working otherwise.
Cheers - Dave
This was all done under CygWin? Can someo
On 4/28/04 at 9:04 AM Jon S Berndt wrote:
>On Wed, 28 Apr 2004 13:29:08 +0100
> "David Luff" <[EMAIL PROTECTED]> wrote:
>
>
>>I think the long term benefits should far outweigh
>>the short term pain.
>
>... for those _not_ using CygWin.
>
>For those using CygWin, it's fatal at the moment.
Nor
On 4/28/04 at 10:09 AM Norman Vine wrote:
>
>I have rebuilt the opeal dll and replaced the one on my site
>http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
>
>This should export the required alut* funcs and it includes
>the Makefile I used
>
>Note you will need to use my headers instead of the
Jon S Berndt writes:
>
> For those using CygWin, it's fatal at the moment.
AFAICT
It is fatal for those using any form of gcc on Win32.
Oh well I guess there is always MSVC < grin >
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http:/
David Luff writes:
>
> Norman's libopenal32.a contains these functions, my libopenal.a doesn't,
> and these errors are hence fixed with Normans .a. However, Norman's
> libopenal32.a doesn't contain any alut* functions, which my libopenal.a
> does, so hence these errors are replaced with the _alut
On Wed, 28 Apr 2004 13:29:08 +0100
"David Luff" <[EMAIL PROTECTED]> wrote:
The tests compile and link with ../src/libopenal.a, so unless you've
hacked their build script or replaced that lib with Norman's then you'll
still belinking (the tests) against the original.
I'll have to adjust that. Has
On 4/28/04 at 1:33 PM David Luff wrote:
>On 4/28/04 at 2:13 PM Frederic Bouvier wrote:
>
>>With MSVC, there is a library for ALut : ALut.lib.
>>_joyGetDevCaps should be in winmm.lib
>>
>
>OK, winmm fixes everthing except the alut stuff, I'm not sure why that
>broke right now but we've had that
Curtis L. Olson writes:
>
> Norman Vine wrote:
>
> >David Luff writes:
> >
> >
> >>On 4/28/04 at 4:10 AM Norman Vine wrote:
> >>
> >>
> >>>Have you tried my partial build of the openal / win directory
> >>>
> >>>http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
> >>>
> >>>probably best to
On 4/28/04 at 1:29 PM David Luff wrote:
>On 4/28/04 at 7:17 AM Jon Berndt wrote:
>>
>>Many of the rest of them seemed to simply hang, but no sound was ever
>>produced. I wonder, though, if your stuff was being used here, because I
>>already have libopenal32.a in /usr/local/lib. I recompiled all
David Luff writes:
>
> On 4/28/04 at 4:10 AM Norman Vine wrote:
> >
> >Have you tried my partial build of the openal / win directory
> >
> >http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
> >
> >probably best to install this into /usr/local
> >
> >i.e.
> >
> >cd /usr/local
> >tar -xzvf $PATH_TO
Norman Vine wrote:
David Luff writes:
On 4/28/04 at 4:10 AM Norman Vine wrote:
Have you tried my partial build of the openal / win directory
http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
probably best to install this into /usr/local
i.e.
cd /usr/local
tar -xzvf $PATH_TO/openal.tgz
On 4/28/04 at 2:13 PM Frederic Bouvier wrote:
>Erik Hofman wrote:
>
>> David Luff wrote:
>>
>> > ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout
>> > e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel
>-lsgtiming
>> > -lsgio -lsgscreen -lsgmath
>> > -lsgbucket -lsgprops
On 4/28/04 at 7:17 AM Jon Berndt wrote:
>
>Many of the rest of them seemed to simply hang, but no sound was ever
>produced. I wonder, though, if your stuff was being used here, because I
>already have libopenal32.a in /usr/local/lib. I recompiled all the tests.
>
The tests compile and link with
Norman wrote:
> Have you tried my partial build of the openal / win directory
>
> http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
>
> probably best to install this into /usr/local
>
> i.e.
>
> cd /usr/local
> tar -xzvf $PATH_TO/openal.tgz
-- test --
$ ./testdevice
got Windows native audio
--
Erik Hofman wrote:
> David Luff wrote:
>
> > ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout
> > e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel -lsgtiming
> > -lsgio -lsgscreen -lsgmath
> > -lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml
> > -lsgso
David Luff wrote:
../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout
e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel -lsgtiming
-lsgio -lsgscreen -lsgmath
-lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml
-lsgsound -lsgserial -lsgstruct
ure -lsgenvironmen
On 4/28/04 at 4:10 AM Norman Vine wrote:
>Jon Berndt writes:
>>
>> > You need to re run configure before make < I left this step out
>> > in my original msg :-( >
>> >
>> > % ./configure
>> >
>> > > > % make
>> > > > % make test
>> >
>> > Norman
>>
>>
>> I got a successful build. I tried run
Jon Berndt writes:
>
> > You need to re run configure before make < I left this step out
> > in my original msg :-( >
> >
> > % ./configure
> >
> > > > % make
> > > > % make test
> >
> > Norman
>
>
> I got a successful build. I tried running some of the
> also-successfully-built test programs:
> You need to re run configure before make < I left this step out
> in my original msg :-( >
>
> % ./configure
>
> > > % make
> > > % make test
>
> Norman
I got a successful build. I tried running some of the
also-successfully-built test programs:
--start--
$ ./testpitch2
got Windows native au
No idea if this will work or not
but here is a binary OpenAL distribution of the
core OpenAL files from the win directory
Note you will need a recent Cygwin DLL to use these
this is untested
http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz
HTH
Norman
EXPORTS
EAXGet @1
EAXSet @2
Here is a page where someone claims to have windows OpenAL building
under MinGW (strictly under a linux cross compiler, which is basically
the same thing). This will/should produce a GNU .a file which you can
use with cygwin.
http://omapi.sourceforge.net/extra/
I'll boot to windows and see if
e if
somebody's already done it)
Giles Robertson
> -Original Message-
> From: D Luff [mailto:[EMAIL PROTECTED]
> Sent: 27 April 2004 12:47
> To: FlightGear developers discussions
> Subject: RE: [Flightgear-devel] OpenAL
>
> On 27 Apr 2004 at 7:23, Jon Berndt wr
David Luff wrote:
> I also got that output from autogen.sh, also on Linux - it appears
> to be harmless. Make went fine on Cygwin. No audio output from the
> test programs on Cygwin though :-(
It's important to point out that the "linux/src/arch/windows"
directory in the OpenAL source distributi
I might have missed this part of the discussion, but OpenAL is not yet
a *required* part of FlightGear yet, is it? I mean, without OpenAL, I
can still do a checkout and build?
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flight
On 27 Apr 2004 at 7:23, Jon Berndt wrote:
> > Jon,
> >
> > I have *no* idea if it actually produces any sound as
> > I don't have a sound board on my development system
> > but
> >
> > after getting the OPENAL CVS files
> >
> > cvs
> > -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository lo
Jon Berndt writes:
> >
> > I have *no* idea if it actually produces any sound as
> > I don't have a sound board on my development system
> > but
> >
> > after getting the OPENAL CVS files
> >
> > cvs
> > -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login
> > (use password "guest")
>
> Jon,
>
> I have *no* idea if it actually produces any sound as
> I don't have a sound board on my development system
> but
>
> after getting the OPENAL CVS files
>
> cvs
> -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login
> (use password "guest")
> cvs
> -d:pserver:[EMAIL PROTECTE
David Luff wrote:
Hi folks,
The recent OpenAL change has broken voice ATIS (start up the default Cessna at KSFO and transfer the 118.85 standby freq on comm1 to be active - the program will segfault) and I can't seem to figure out a fix on my own. The segfault occurs in ATCVoice.cxx line 172, wh
Hi folks,
The recent OpenAL change has broken voice ATIS (start up the default Cessna at KSFO
and transfer the 118.85 standby freq on comm1 to be active - the program will
segfault) and I can't seem to figure out a fix on my own. The segfault occurs in
ATCVoice.cxx line 172, which is memcpy.
Greetings,
I can also confirm sound in FlightGear through OpenAL is working well (better
with arts support enabled rather than just alsa or oss emulation). Don't
quite understand why but it may be because I'm running under KDE.
I've finally got as far as I can with the ebuilds on Gentoo for Si
On Sunday 25 April 2004 23:31, Dave Perry wrote:
> Some feedback on OpenAL:
>
> I just updated plib, SimGear, and FlightGear from cvs. With the default
> Cessna 172, the sound does not change with throttle setings or RPM
> change. Also, the ident for the ADF does not go away when I turn off
> th
Some feedback on OpenAL:
I just updated plib, SimGear, and FlightGear from cvs. With the default
Cessna 172, the sound does not change with throttle setings or RPM
change. Also, the ident for the ADF does not go away when I turn off
the ident or change frequencies. The flap motion sounds an
Under Gentoo:
"emerge openal" then it built fine against CVS Simgear however I'm having
trouble getting autogen.sh to pick everything up correctly for building CVS
FlightGear. Is anyone here running CVS FlightGear under Gentoo? If not I
may have to look into how to construct an ebuild for port
I tried essentially what you suggested yesterday. I'll try again later
today, but following your explicit example. If needed I may re-checkout the
distro. I'll let you know what I get.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail
Norman Vine wrote:
>
> after getting the OPENAL CVS files
>
> cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login
> (use password "guest")
> cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal
>
OOPS I forgot the configure command
> then
% cd $OPENAL
% cd linux
Jon Berndt writes:
>
> > Jon, you might also search for "libopenal" along with cygwin ... if
> > cygwin packaged openal, I bet that is what they'd call it.
> >
> > Curt.
>
> That search appeared to be more productive initially, but nothing helpful
> has cropped up, yet.
>
> Jon,
> CygWin user -
On Sunday 25 April 2004 12:49, Chris Horler wrote:
> > Flightgear and Simgear builds ok on SuSE Linux 9.0, but when I try to run
> > Flightgear I get this error message:
>
> I'm also running SuSE 9.0 with the same default openal packages.
I have
VT8233/A/8235 AC97 Audio Controller
that's a mainbo
> Flightgear and Simgear builds ok on SuSE Linux 9.0, but when I try to run
> Flightgear I get this error message:
I'm also running SuSE 9.0 with the same default openal packages.
> Initializing OpenAL sound manager
> fgfs: pcm.c:1050: snd_pcm_writei: Assertion `pcm->setup' failed.
I don't get thi
Hi
Flightgear and Simgear builds ok on SuSE Linux 9.0, but when I try to run
Flightgear I get this error message:
Initializing OpenAL sound manager
fgfs: pcm.c:1050: snd_pcm_writei: Assertion `pcm->setup' failed.
I'm using openal version 20030811-83 and openal-devel version 20030811-83 as
der
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 crea
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
1 - 100 of 147 matches
Mail list logo
