Re: [Flightgear-devel] Sound support broken by AI traffic
On Mon, 2011-12-12 at 22:58 +0100, ThorstenB wrote: Btw, is there a way to influence the audio level of AI sounds? Would be nice if sounds could be muffled in inside views (i.e. cockpit/inside view), while they should have normal/higher volume in outside views (and there should be no difference for aircraft without a canopy of course). Sorry, if that's another feature request ;-). Yes, just like all the other sound groups the sound groups of AI Models has it's own volume property (and enable/disable property). Erik -- Systems Optimization Self Assessment Improve efficiency and utilization of IT resources. Drive out cost and improve service delivery. Take 5 minutes to use this Systems Optimization Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
Erik On Mon, 2011-12-12 at 20:22 +0100, ThorstenB wrote: Hi Erik, Am 12.12.2011 13:31, schrieb Erik Hofman: I've implemented a mechanism to free OpenAL sources that are farther away than max-distance (3km for the current AI models). This might solve your problems, although it is not a one size fits all solution. I'm still getting many error messages at EHAM - but it's better now. It's starting ok and I'm hearing AI sounds. Nice :) However, XML conditions for AI aircraft have no effect. All AI sound samples are played unconditionally as soon as the aircraft is in range. That's the problem of the AIModel code that models hardly any properties suitable for sound playback. It should be extended and the config file should be updated to match the changes. play once AI sound samples are also played continuously. I think it's caused by an issue with your last update. Attached patch restores the effect of the XML conditions for me - and also play once samples work as expected. Not sure if that's the correct way to fix it though... Not entirely no.. it looks like the looping setting gets lost in the process, I'll take a look at it. As of this mornings Git with MSVC10 build and WinXP I'm getting this continuously repeated: Sound manager: No more free sources available! At KHAV with the traffic manager disabled. Frame rate is reduced to 4-5 and the system is unusable. Vivian -- Systems Optimization Self Assessment Improve efficiency and utilization of IT resources. Drive out cost and improve service delivery. Take 5 minutes to use this Systems Optimization Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Tue, 2011-12-13 at 09:17 +, Vivian Meazza wrote: As of this mornings Git with MSVC10 build and WinXP I'm getting this continuously repeated: Sound manager: No more free sources available! I'm working on it. It turned out testing with the UFO alone was not sufficient. Erik -- Systems Optimization Self Assessment Improve efficiency and utilization of IT resources. Drive out cost and improve service delivery. Take 5 minutes to use this Systems Optimization Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 09:50 +, James Turner wrote: I'm seeing something very similar on Mac at EHAM, except I get messages continuously during FGFS operation about 'no more sources', which I assumed was due to every AI aircraft at EHAM requesting a source :) I've implemented a mechanism to free OpenAL sources that are farther away than max-distance (3km for the current AI models). This might solve your problems, although it is not a one size fits all solution. For that there needs to be better source management to decide which sounds to drop (if any) if a new sample is set to playing. Erik -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
Hi Erik,
Am 12.12.2011 13:31, schrieb Erik Hofman:
I've implemented a mechanism to free OpenAL sources that are farther
away than max-distance (3km for the current AI models). This might solve
your problems, although it is not a one size fits all solution.
I'm still getting many error messages at EHAM - but it's better now.
It's starting ok and I'm hearing AI sounds. Nice :)
However, XML conditions for AI aircraft have no effect. All AI sound
samples are played unconditionally as soon as the aircraft is in range.
play once AI sound samples are also played continuously. I think it's
caused by an issue with your last update. Attached patch restores the
effect of the XML conditions for me - and also play once samples work
as expected. Not sure if that's the correct way to fix it though...
cheers,
Thorsten
diff --git a/simgear/sound/sample_group.cxx b/simgear/sound/sample_group.cxx
index bdc00ee..c24bb5b 100644
--- a/simgear/sound/sample_group.cxx
+++ b/simgear/sound/sample_group.cxx
@@ -414,8 +414,6 @@ void SGSampleGroup::update_pos_and_orientation() {
+ position[1]*position[1] + position[2]*position[2];
if (sample-is_playing() (dist2 max2)) {
sample-stop();
-} else if (!sample-is_playing() (dist2 max2)) {
-sample-play(sample-is_looping());
}
}
}
--
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at http://p.sf.net/sfu/ms-windowsazure___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Mon, 2011-12-12 at 20:22 +0100, ThorstenB wrote: Hi Erik, Am 12.12.2011 13:31, schrieb Erik Hofman: I've implemented a mechanism to free OpenAL sources that are farther away than max-distance (3km for the current AI models). This might solve your problems, although it is not a one size fits all solution. I'm still getting many error messages at EHAM - but it's better now. It's starting ok and I'm hearing AI sounds. Nice :) However, XML conditions for AI aircraft have no effect. All AI sound samples are played unconditionally as soon as the aircraft is in range. That's the problem of the AIModel code that models hardly any properties suitable for sound playback. It should be extended and the config file should be updated to match the changes. play once AI sound samples are also played continuously. I think it's caused by an issue with your last update. Attached patch restores the effect of the XML conditions for me - and also play once samples work as expected. Not sure if that's the correct way to fix it though... Not entirely no.. it looks like the looping setting gets lost in the process, I'll take a look at it. Erik -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
Am 12.12.2011 21:22, schrieb Erik Hofman: That's the problem of the AIModel code that models hardly any properties suitable for sound playback. Not in this case. I had experimented with the AI balloons. I have pushed this to fgdata now - you can use these for testing the issue I reported. Enable the balloon-demo: the balloons' burners now have a nice whoosh! sound. Burner light and sound are connected to the same property - so you should see the light come on and hear the sound at the same time. But currently the balloon's AI sound triggers all the time - so we just get a continuous roar (kind of worked with my patch - so I think the XML conditions are ok). cheers, Thorsten -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Mon, 12 Dec 2011 21:59:35 +0100 ThorstenB bre...@gmail.com wrote: Am 12.12.2011 21:22, schrieb Erik Hofman: That's the problem of the AIModel code that models hardly any properties suitable for sound playback. Not in this case. I had experimented with the AI balloons. I have pushed this to fgdata now - you can use these for testing the issue I reported. Enable the balloon-demo: the balloons' burners now have a nice whoosh! sound. Burner light and sound are connected to the same property - so you should see the light come on and hear the sound at the same time. But currently the balloon's AI sound triggers all the time - so we just get a continuous roar (kind of worked with my patch - so I think the XML conditions are ok). Ok the only thing the code you proposed to remove does (or should do) is active the sample again when in-range again (distance smaller than max_distance). I've had another report that I suspect has something to do with the same section. If some one want to comment it out (or apply the patch) in the code please go ahead. I'm not at the proper pc right now and won't be able to do anything before tomorrow mortning (EU time). -- Erik Hofman e...@ehofman.com AeonWave audio http://www.adalin.com -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On 12.12.2011 22:41, Erik Hofman wrote: Ok the only thing the code you proposed to remove does (or should do) is active the sample again when in-range again (distance smaller than max_distance). I've had another report that I suspect has something to do with the same section. If some one want to comment it out (or apply the patch) in the code please go ahead. I'm not at the proper pc right now and won't be able to do anything before tomorrow mortning (EU time). I think we can wait another day... And you may be right, without the line there seems to be an issue when flying back into the range of an AI aircraft - so looped sounds aren't (immediately) resumed. Still seems the current implementation triggers a bit too much... Btw, is there a way to influence the audio level of AI sounds? Would be nice if sounds could be muffled in inside views (i.e. cockpit/inside view), while they should have normal/higher volume in outside views (and there should be no difference for aircraft without a canopy of course). Sorry, if that's another feature request ;-). cheers, Thorsten -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Fri, 2011-12-02 at 22:44 +0100, Erik Hofman wrote: On Fri, 02 Dec 2011 20:44:06 +0100 ThorstenB bre...@gmail.com wrote: Hi Eric et al, With sg/fg git of yesterday also no sound here at KSFO - well one 'click' sound at beginning and one at end - on exit says deleting some 58 buffers... but no other obvious errors... But sound all ok at YGIL - no AI there yet ;=)) deleting just 4 Source(s) on exit... Did not try the tracker patch, which just chops the AI sound code... And trying the openal tests - .../build/simgear/sound $ ./openal_test1 - ok, hear jet sound fine... But openal_test2, 3, and 4 - hear the same 'click' or 'pop' sounds only, but that is all... Advise any other tests I should try, or more information than given below... Regards, Geoff. ~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION=Ubuntu 10.04.3 LTS ~$ dpkg -l | grep -i openal ii libalut-dev1.1.0-2 ii libalut0 1.1.0-2 ii libopenal-dev 1:1.12.854-0ubuntu1~lucid1 rc libopenal0a1:0.0.8-7 ii libopenal1 1:1.12.854-0ubuntu1~lucid1 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On 2 Dec 2011, at 21:44, Erik Hofman wrote: sound support is broken here (GIT of today). When I start with the UFO at an airport with AI traffic, e.g. KSFO, then I hear a roar for a few seconds during start-up - but then there is silence for the rest of the simulation. No sound when the UFO moves. On shutdown, I do get a few error messages like these: AL Error (sound manager): Invalid Operation at release buffer AL Error (sound manager): Invalid Operation at release buffer Hm, this migh be an OpenAL incompatibility since obviously I didn't notice this. I'll try to test it with OpenAL-Soft tomorrow. I'm seeing something very similar on Mac at EHAM, except I get messages continuously during FGFS operation about 'no more sources', which I assumed was due to every AI aircraft at EHAM requesting a source :) James -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 09:50 +, James Turner wrote: I'm seeing something very similar on Mac at EHAM, except I get messages continuously during FGFS operation about 'no more sources', which I assumed was due to every AI aircraft at EHAM requesting a source :) This seems like a hardware limit to me. I was already wondering if (and when) it would show up. I'll take a look at this also. Luckily I can limit the number of source emitters in my own implementation. This probably requires some clever source management to be added. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Fri, 2011-12-02 at 20:44 +0100, ThorstenB wrote: Hi Erik et al, sound support is broken here (GIT of today). When I start with the UFO at an airport with AI traffic, e.g. KSFO, then I hear a roar for a few seconds during start-up - but then there is silence for the rest of the simulation. No sound when the UFO moves. On shutdown, I do get a few error messages like these: AL Error (sound manager): Invalid Operation at release buffer AL Error (sound manager): Invalid Operation at release buffer It's working fine when I start at some remote location which doesn't have AI traffic, i.e. ENSD. I commented out the new code in AIBase::update - and then sound is back to normal. However, the error messages (see above) are still there - so these could be unrelated. Alright, this is confirmed with OpenAL-Soft but it works with my own implementation. This gives me a hunch though. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Fri, 2011-12-02 at 20:44 +0100, ThorstenB wrote: Hi Erik et al, sound support is broken here (GIT of today). When I start with the UFO at an airport with AI traffic, e.g. KSFO, then I hear a roar for a few seconds during start-up - but then there is silence for the rest of the simulation. No sound when the UFO moves. With default airport KSFO, I am unable to get past the splash screen. Starting at my local EGPF, FG starts OK, but hangs with log(info) showing: Traffic manager: Creating AIModel from:EGPF-EGKK.xml Route from EGPF to EGKK. Set leg to : 1 SpeedBird2961 Reading sound sound from /opt/FlightGear/fgdata/AI/Sounds/737-sound.xml Neither a condition nor a property specified Neither a condition nor a property specified Then hangs. Kind regards to all, Alasdair -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 03 Dec 2011 10:47:45 +0100, Geoff wrote in message 1322905665.1833.16.camel@DELL02: /media/Disk2/FG/fg19$ ./run_fgfs.sh --show-sound-devices run_fgfs.sh: Running: ./fgfs --fg-root=/media/Disk2/FG/fg18/fgdata --show-sound-devices OpenAL Soft provided by OpenAL Community No. Device 0. PulseAudio Software 1. ALSA Software on default 2. ALSA Software on HDA Intel [STAC92xx Analog] (hw:0,0) 3. ALSA Software on HDA Intel [STAC92xx Digital] (hw:0,1) 4. ALSA Software on HDA ATI HDMI [ATI HDMI] (hw:1,3) 5. OSS Software 6. PortAudio Software ..how exactly are we supposed to explicitly pick one of these with the --sound-device option? --sound-device=0. PulseAudio Software Explicitly specify the audio device to use? Yes, I have tried quite a few variants of this on my devices: OpenAL Soft provided by OpenAL Community No. Device 0. PulseAudio Software 1. ALSA Software on default 2. ALSA Software on HDA Intel [ALC269 Analog] (hw:0,0) 3. PortAudio Software ..the normal way I see elsewhere, is like ' --sound-device=0 or ' --sound-device=0 ' or --sound-device=PulseAudio Software ', for the PulseAudio alternative. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 13:13 +0100, Arnt Karlsen wrote: ..how exactly are we supposed to explicitly pick one of these with the --sound-device option? --sound-device=0. PulseAudio Software Explicitly specify the audio device to use? Yes, I have tried quite a few variants of this on my devices: OpenAL Soft provided by OpenAL Community No. Device 0. PulseAudio Software 1. ALSA Software on default 2. ALSA Software on HDA Intel [ALC269 Analog] (hw:0,0) 3. PortAudio Software ..the normal way I see elsewhere, is like ' --sound-device=0 or ' --sound-device=0 ' or --sound-device=PulseAudio Software ', for the PulseAudio alternative. You select one of the devices like this: --sound-device=ALSA Software on HDA Intel [STAC92xx Digital] (hw:0,1) Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 10:30 +, Alasdair Campbell wrote: With default airport KSFO, I am unable to get past the splash screen. Starting at my local EGPF, FG starts OK, but hangs with log(info) showing: Traffic manager: Creating AIModel from:EGPF-EGKK.xml Route from EGPF to EGKK. Set leg to : 1 SpeedBird2961 Reading sound sound from /opt/FlightGear/fgdata/AI/Sounds/737-sound.xml Neither a condition nor a property specified Neither a condition nor a property specified Then hangs. Ok this message should be fixed. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 11:21 +0100, Erik Hofman wrote: Alright, this is confirmed with OpenAL-Soft but it works with my own implementation. This gives me a hunch though. I have it sort of working now (using the code in git) but this requires the master sound switch to be disabled and enabled again. Unfortunately I am still struggling my way through the code. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 03 Dec 2011 13:28:56 +0100, Erik wrote in message 1322915336.5715.1.camel@Raptor: On Sat, 2011-12-03 at 13:13 +0100, Arnt Karlsen wrote: ..how exactly are we supposed to explicitly pick one of these with the --sound-device option? --sound-device=0. PulseAudio Software Explicitly specify the audio device to use? Yes, I have tried quite a few variants of this on my devices: OpenAL Soft provided by OpenAL Community No. Device 0. PulseAudio Software 1. ALSA Software on default 2. ALSA Software on HDA Intel [ALC269 Analog] (hw:0,0) 3. PortAudio Software ..the normal way I see elsewhere, is like ' --sound-device=0 or ' --sound-device=0 ' or --sound-device=PulseAudio Software ', for the PulseAudio alternative. You select one of the devices like this: --sound-device=ALSA Software on HDA Intel [STAC92xx Digital] (hw:0,1) ..ok, this is the _only_ acceptable --sound-device syntax??? Erik ..thanks, Erik, my !303 should have worked, I'll try it somewhere else than KSFO to see what happens. 303 ./run_fgfs.sh --enable-fullscreen --sound-device=ALSA Software on HDA Intel [ALC269 Analog] (hw:0,0) --log-level=bulk ' -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
I've sorted out where things go wrong (last update in git, which basically disables aimodel sounds again). But I have to go and will not be back until tomorrow morning so as far as I can tell the sound is in a working state again. If someone feels brave, please go ahead and take a look if you can find the exact problem otherwise I need to find some time again. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 15:31 +0100, Arnt Karlsen wrote: On Sat, 03 Dec 2011 13:28:56 +0100, Erik wrote in message You select one of the devices like this: --sound-device=ALSA Software on HDA Intel [STAC92xx Digital] (hw:0,1) ..ok, this is the _only_ acceptable --sound-device syntax??? Yes, the parser hands over the string directly to OpenAL. ..thanks, Erik, my !303 should have worked, I'll try it somewhere else than KSFO to see what happens. 303 ./run_fgfs.sh --enable-fullscreen --sound-device=ALSA Software on HDA Intel [ALC269 Analog] (hw:0,0) --log-level=bulk ' Yes. that should work, sound wise that is. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Sat, 2011-12-03 at 15:35 +0100, Erik Hofman wrote: I've sorted out where things go wrong (last update in git, which basically disables aimodel sounds again). But I have to go and will not be back until tomorrow morning so as far as I can tell the sound is in a working state again. Hi Eric, Thanks. Would confirm sound is back, but now I get the exit messages - AL Error (sound manager): Invalid Operation at release buffer AL Error (sound manager): Invalid Operation at release buffer AL lib: ALc.c:1420: alcDestroyContext(): deleting 5 Source(s) AL lib: ALc.c:1818: alcCloseDevice(): deleting 4 Buffer(s) Regards, Geoff. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
Am 02.12.2011 20:44, schrieb ThorstenB: sound support is broken here (GIT of today). When I start with the UFO Sorry, only checking the bug tracker now (yes, should have done that first :) ). Someone reported a related issue, different effect though: http://code.google.com/p/flightgear-bugs/issues/detail?id=501 cheers, Thorsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Fri, 02 Dec 2011 20:44:06 +0100 ThorstenB bre...@gmail.com wrote: Hi Erik et al, sound support is broken here (GIT of today). When I start with the UFO at an airport with AI traffic, e.g. KSFO, then I hear a roar for a few seconds during start-up - but then there is silence for the rest of the simulation. No sound when the UFO moves. On shutdown, I do get a few error messages like these: AL Error (sound manager): Invalid Operation at release buffer AL Error (sound manager): Invalid Operation at release buffer Hm, this migh be an OpenAL incompatibility since obviously I didn't notice this. I'll try to test it with OpenAL-Soft tomorrow. Erik -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
