stayup Posted December 29, 2017 Report Posted December 29, 2017 I don't have audio for GPWS, Mach Air Speed Warning, and altitude call outs when landing, most of the time. On occasion it all works. I can't figure out how to correct this so I get a consistent audio for all operations. I would appreciate help with this. For the GPWS I get an inop notice. Thanks Quote
Ben Russell Posted December 29, 2017 Report Posted December 29, 2017 1 minute ago, stayup said: I don't have audio for GPWS, Mach Air Speed Warning, and altitude call outs when landing, most of the time. On occasion it all works. I can't figure out how to correct this so I get a consistent audio for all operations. I would appreciate help with this. For the GPWS I get an inop notice. Thanks Please attach a copy of Log.txt from the X-Plane folder. IXEG is heavy on sound resources... when it works it's magic but the team may have over stretched the sound resources budget, especially when paired up with additional content and plugins that the sim might have loaded. The Log.txt will help me see a bit more about what's going on in that regard. Quote
stayup Posted December 29, 2017 Author Report Posted December 29, 2017 3 hours ago, Ben Russell said: Please attach a copy of Log.txt from the X-Plane folder. IXEG is heavy on sound resources... when it works it's magic but the team may have over stretched the sound resources budget, especially when paired up with additional content and plugins that the sim might have loaded. The Log.txt will help me see a bit more about what's going on in that regard. Ben, Thanks for the response. I'm enclosing my Log.txt. If you want a Log.txt of when the sound is all on let me know. Log.txt Quote
Ben Russell Posted December 29, 2017 Report Posted December 29, 2017 1 hour ago, stayup said: Ben, Thanks for the response. I'm enclosing my Log.txt. If you want a Log.txt of when the sound is all on let me know. Log.txt Thanks for the Log.txt file. I see two things of interest; 1. OpenAL devices: Bose Quietcomfort 35 2 This looks to be some kind of surrond sound headset? If possible, try setting it to standard stereo 2 channel rendering mode. Just yesterday I had another user with a 5.1 setup that was causing trouble. Setting to stereo resolved it. 2. An error string I never see; G64: 497.571: OpenAL: Closing context and device. G64: 497.572: OpenALHooks->restoreContext: FAIL, previous context handle is NULL G64: 497.836: Plugin Disabled. This indicates a pretty serious clash or failure of the sound system. Looking at your list of plugins I can see a few items loading before Gizmo. Most of them I've seen before and have no known problems with. One of them, "AIRPORTVS", I have not seen before and is possibly the source of conflict. Please try disabling "AIRPORTVS" by moving it out of the X-Plane / Resources / plugins / folder and test loading the sim. I would also like to see the Log.txt from that sim session to see if the error string above is still present. The other two items loading before Gizmo and thus capable of conflicting with sound resources are "AutoGate" and "EZPushBack". If AVS is not the source of conflict you could try and move those around for testing too. I still suspect it might simply be the Bose Multi Channel sound system though... Hope that helps! Quote
stayup Posted December 29, 2017 Author Report Posted December 29, 2017 34 minutes ago, Ben Russell said: Thanks for the Log.txt file. I see two things of interest; 1. OpenAL devices: Bose Quietcomfort 35 2 This looks to be some kind of surrond sound headset? If possible, try setting it to standard stereo 2 channel rendering mode. Just yesterday I had another user with a 5.1 setup that was causing trouble. Setting to stereo resolved it. 2. An error string I never see; G64: 497.571: OpenAL: Closing context and device. G64: 497.572: OpenALHooks->restoreContext: FAIL, previous context handle is NULL G64: 497.836: Plugin Disabled. This indicates a pretty serious clash or failure of the sound system. Looking at your list of plugins I can see a few items loading before Gizmo. Most of them I've seen before and have no known problems with. One of them, "AIRPORTVS", I have not seen before and is possibly the source of conflict. Please try disabling "AIRPORTVS" by moving it out of the X-Plane / Resources / plugins / folder and test loading the sim. I would also like to see the Log.txt from that sim session to see if the error string above is still present. The other two items loading before Gizmo and thus capable of conflicting with sound resources are "AutoGate" and "EZPushBack". If AVS is not the source of conflict you could try and move those around for testing too. I still suspect it might simply be the Bose Multi Channel sound system though... Hope that helps! Thanks Ben, enclosed is the Log.txt with the working sound elements. Log.txt Quote
Ben Russell Posted December 30, 2017 Report Posted December 30, 2017 4 hours ago, stayup said: Thanks Ben, enclosed is the Log.txt with the working sound elements. Log.txt Definitely related to the Bose surround(?) sound. Second Log indicates a generic sound output device; OpenAL devices: Built-in Output Open AL default device:Built-in Output OpenAL vendor : Apple Computer Inc. OpenAL renderer : Software OpenAL version : 1.1 OpenAL hardware : Built-in Output Good to know that the plugins aren't the problem. As for a resolution.... XP11 brings the new FMOD sound engine so we need to carefully evaluate where and how to spend our efforts. Up until now we had to create our own custom sound engine. With the coming focus on VR it's probably going to need to be ported to FMOD to take full advantage of all the spacial audio features and optimizations. This is no small task so I can't really comment on when it might happen. Quote
stayup Posted December 30, 2017 Author Report Posted December 30, 2017 1 hour ago, Ben Russell said: Definitely related to the Bose surround(?) sound. Second Log indicates a generic sound output device; OpenAL devices: Built-in Output Open AL default device:Built-in Output OpenAL vendor : Apple Computer Inc. OpenAL renderer : Software OpenAL version : 1.1 OpenAL hardware : Built-in Output Good to know that the plugins aren't the problem. As for a resolution.... XP11 brings the new FMOD sound engine so we need to carefully evaluate where and how to spend our efforts. Up until now we had to create our own custom sound engine. With the coming focus on VR it's probably going to need to be ported to FMOD to take full advantage of all the spacial audio features and optimizations. This is no small task so I can't really comment on when it might happen. Hi Ben, The problem seems to be AirportVS-SASL. I like AVS, but if I want all the sound on the 737 I'm going to have to remove the plugin. I hope that this will be corrected in future updates. Thanks again, Irv Quote
Ben Russell Posted December 30, 2017 Report Posted December 30, 2017 15 minutes ago, stayup said: Hi Ben, The problem seems to be AirportVS-SASL. I like AVS, but if I want all the sound on the 737 I'm going to have to remove the plugin. I hope that this will be corrected in future updates. Thanks again, Irv You'll have to take this up with the AVS team. I was literally banned from the org for resolving sound issues. (Can't find the thread today or I'd put a link here..) Gizmo has had zero sound+plugins clash bugs for probably five years or more. Quote
Ben Russell Posted December 30, 2017 Report Posted December 30, 2017 I'd be interested in seeing a Log.txt without AVS loading to see if that Gizmo "OpenAL context" error message goes away..G64: 497.571: OpenAL: Closing context and device.G64: 497.572: OpenALHooks->restoreContext: FAIL, previous context handle is NULLG64: 497.836: Plugin Disabled. Quote
stayup Posted December 30, 2017 Author Report Posted December 30, 2017 39 minutes ago, Ben Russell said: I'd be interested in seeing a Log.txt without AVS loading to see if that Gizmo "OpenAL context" error message goes away..G64: 497.571: OpenAL: Closing context and device.G64: 497.572: OpenALHooks->restoreContext: FAIL, previous context handle is NULLG64: 497.836: Plugin Disabled. Ben, I think this is what you want....my last flight without AVS. Let me know. Log.txt 1 Quote
Ben Russell Posted December 30, 2017 Report Posted December 30, 2017 4 minutes ago, stayup said: Ben, I think this is what you want....my last flight without AVS. Let me know. Log.txt Definitely looks "cleaner" on exit; [AVS INFO]: Disabling... EZPushback: reset state EZPushback: disabled G64:6096.566: Plugin Disabled. EZPushback: prefs written to /Users/Irving/Desktop/X-Plane 11/Resources/plugins/EZPushback/ezpushback.ini EZPushback: stopped Clean exit from threads. No errors at all. Just a clean disable from Gizmo. (G64 in the Logs...) I'm going to log a conflict bug against this; [AIRPORTVS INFO]: Starting X-Plane SASL plugin v3.1.2+d19f937 [Commercial Edition] [AIRPORTVS INFO]: AirportVS | Global | StartFull Loaded: /Users/Irving/Desktop/X-Plane 11/Resources/plugins/AirportVS-SASL/64/mac.xpl (1-sim.com AirportVS #3). Many thanks for your help! Quote
stayup Posted January 1, 2018 Author Report Posted January 1, 2018 On 12/30/2017 at 1:00 AM, Ben Russell said: Definitely looks "cleaner" on exit; [AVS INFO]: Disabling... EZPushback: reset state EZPushback: disabled G64:6096.566: Plugin Disabled. EZPushback: prefs written to /Users/Irving/Desktop/X-Plane 11/Resources/plugins/EZPushback/ezpushback.ini EZPushback: stopped Clean exit from threads. No errors at all. Just a clean disable from Gizmo. (G64 in the Logs...) I'm going to log a conflict bug against this; [AIRPORTVS INFO]: Starting X-Plane SASL plugin v3.1.2+d19f937 [Commercial Edition] [AIRPORTVS INFO]: AirportVS | Global | StartFull Loaded: /Users/Irving/Desktop/X-Plane 11/Resources/plugins/AirportVS-SASL/64/mac.xpl (1-sim.com AirportVS #3). Many thanks for your help! Ben, I believe that the conflict actually relates to Gizmo and the AirportVS-SASL rather than the IXEG 737 and AirportVS-SASL. My reason for saying this is that the only aircraft that I have sound issues with both use Gizmo and when flying other aircraft with AVS active that do not require Gizmo there are no sound issues, all sound is normal. Thanks and Happy New Year Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.