Hi Charles,>About the only >downside was my wife laughing her head off as I repeatedly >used the MS microphone setup to set the volume. I'm still >getting hit with "This Papaya taste Perfect" everytime she >walks by.... Oh, and I thought I was the only one who had to go through this ... ;)Dirk

Dear CharlesA bunch of thanks for your very useful and refreshing advises!!Yes, I also got caught by my girlfriend while going thru those testing phrases *LOL*. She started to accept me spending hours and hours on that machine before she saw me talking to it....! :-DI know that the PSS Airbus uses different keys for a number of commands, such as the autopilot, altitude, heading, speedbrakes and speed functions, however, I managed to control the flaps, gears and some panels, just as you did! I assume that it won't be possible to assign these keys to speechbuddy with the PSS aircrafts. We could maybe email each other those commands that we find working with the Airbus, as I wouldn't go back to any default aircraft for sure. Would you mind to forward that RC file? [email protected] .Now, since my girlfriend is asleep I will go back for the SAPI and Papaya testing now! Ttyl, Sam (LSZH, Switzerland)

Dirk, no matter how many places I update my email there always seems to be another I have forgotten. Thanks for trying, and thanks for the post. Bob

Thank you very much, Dirk! I just noticed that you replied already when I went thru the thread once more...If I understood you correctly, after copying and pasting I added in my RC software the "Ctrl-Key" from 1 to 7, as I haven't done that before. (or would I just change 1 AND 7)How would I find a key to create a rule? E.g. "Space" button...So far, thank you once again, I will start testing!!Sam

Hi Sam,>If I understood you correctly, after copying and pasting I >added in my RC software the "Ctrl-Key" from 1 to 7, as I >haven't done that before. (or would I just change 1 AND 7) Yep, for the above rules to work you have to change ALL number key definitions (0-9) in RC3 to use the Ctrl key. It also has the advantage that it doesnt conflict with the FS ATC ...>How would I find a key to create a rule? E.g. "Space" >button... All special keys are listed in the file "sendkeys.txt" which came with SpeechBuddy (e.g. BACKSPACE, CAPSLOCK, etc.).The 'Space' key is just an ordinary key which is denoted by " ", so an example for such a rule would be : Item checkedI assume it is for the checklist in FDC, right ... ? :)I used "Item checked" (and not just 'check') in the example because I would avoid such short phrases, the recognition is always more accurate if you have longer ones ...Dirk

Hi Dirk>I assume it is for the checklist in FDC, right ... ? Very true! I indeed thought of including FDC into speechbuddy's (later "SpBu") command!! How did you guess???After your posting my enthusiasm can't be held back anymore! I fiddled last night and tried to add RC's command as you explained. It took me some minutes to find out that I have to alter the ".xml" to ".txt" in order to paste phrases... ;-) I changed the key commands in RC's soft and copied the phrases as you explained. However, my speechbuddy wouldn't recognice my voice, but it still did when calling "Select 7". I'd might have to do some more "Papaya training classes"? :-) Very nice of you to add the FDC's phrase in your previous posting. I also found the Keylist as you mentioned. Would I have to copy that "Check"-rule into the "xml-File"? FDC starts it's checklist by the "Ctrl-Space" command, which I solved as of today by a minipanel I recently created. However, to do that with SpBu would be much more realistic. Am I getting this right? To start the checklist I would have to call "Check" and must set FDC's checklist to "manual" in order to confirm myself with "Item checked"?I bytheway often get an error message stating "address... and restart", however SpBu would still answer when "testing". I reckon, I just live that way as long it doesn't shut down.Many thanks!!Sam, LSZH

Hi Sam,>After your posting my enthusiasm can't be held back anymore! >I fiddled last night and tried to add RC's command as you >explained. It took me some minutes to find out that I have >to alter the ".xml" to ".txt" in order to paste phrases... Did you just double-click on the .xml file ? Yeah, I guess then your browser will probably open it. But you can edit the XML file directly by openening it with Notepad ...>;-) I changed the key commands in RC's soft and copied the >phrases as you explained. However, my speechbuddy wouldn't >recognice my voice, but it still did when calling "Select >7". I'd might have to do some more "Papaya training >classes"? :-) Hmmm, try to change the phrase to something simpler, maybe just try "Roger" (just to see if the problem is the complexity of the phrase or something else). Also change to developer mode and debug mode while testing, this way SB displays in its main window if and which rule it recognized. And last but not least, it of course also depends on the quality of your microphone...>Very nice of you to add the FDC's phrase in your previous >posting. I also found the Keylist as you mentioned. Would I >have to copy that "Check"-rule into the "xml-File"? FDC >starts it's checklist by the "Ctrl-Space" command, which I >solved as of today by a minipanel I recently created. >However, to do that with SpBu would be much more realistic. >Am I getting this right? To start the checklist I would have >to call "Check" and must set FDC's checklist to "manual" in >order to confirm myself with "Item checked"? For the FDC setting I'm not sure (I dont use it anymore), but I think you got it right. The rule I gave as an example (yep, you have to copy this into the XML file) only does the confirmation part ("Item checked" -> "Space" in FDC). For starting the checklist you would need another rule, like this :Start checklistThis will recognize the phrase "Start checklist" and send a Ctrl-Space to FDC>I bytheway often get an error message stating "address... >and restart", however SpBu would still answer when >"testing". I reckon, I just live that way as long it doesn't >shut down. Mhh, never had that one ...Dirk

Dear DirkI am delighted!!!!!! I went for some more papaya test speaches and all of a sudden everything seems to work correct!! You have set all correct!!!! Can't tell you how much I appreciate your patient support!! Thank you very much, Dirk!! My next flight I dedicate to you! ;-)The only item missing is a decent headset!If you don't mind, I might come up some time later with some minor issues.... :-DBest wishes and happy flying!Sam, LSZH

Hello Sam, I'll send those files asap. Tried the RC files last night with limited success. For the Airbus, I'm finding the commands "panel three and four work well for bringing up the FMC and Throttle Quadrant respectively, as well as just using the Throttle Quadrant command by itself. Using Set current altimeter in speechbuddy did reset the Airbus's altimeter to standard and back. Gear and flap commands work as you pointed out. Could not get the regular view commands to respond but I did get the IFR/VFR view to change using "panel one". For RC3 I did as Dirk has in his instructions, copied them initially to the stock 2k2 files for speechbuddy and made sure the combo "cntrl/number" was enable in the RC3 setup. I could only got the initial weather briefing to work:( Tried many times but the request combination for clearance delivery just wouldn't register. I tried the testing call after each none response and never did lose the program though. It just wouldn't do anything. Dirk, if you see this, I took a short primer in XML and noticed that one of the rules had a lower case "p" at the start of the rule but finished with an upper case "P" to end the rule set. Since the primer said XML was case sensitive I corrected it to match. Havn't had the opportunity to see if that made a difference. Speechbuddy didn't have a problem with the mismatch but would appreciate any help. Maybe I had some hidden spaces or something. Sam, please let me know how things work for you. Charles

Hi CharlesIn fact, I managed to set up everything to work perfectly by now! Dirk gave me the missing hints! I also went through some more Papaya testings, which solved the shut downs I suffered before!I am able to operate almost all commands in the Airbus by speach now! I fiddled hours and hours and got it right. (check my other posting...) The Airbus, FDC and RC work like a treat! I am able to arm and disarm spoilers, flaps, gears, speedbrakes, autopilot, call fmc, overhead, pedestal and the same time I acknowledge RC's key 7 by "Roger, Swiss 615 heavy" or "Roger and switch, Swiss.... for Key 1. FDC always confirms every command! I am also able to change views or zoom by speach. The only missing issue is that I can't change headings, speed or altitudes. It probably relies to different key commands PSS uses in their software. Nevertheless, I am quite satisfied with the result! If it would be of any help, I could forward the two essential files.Best wishes form Zurich, Sam (extremely tired after to nights pondering... ;-D)

Hi Charles,>For RC3 I did as Dirk has in his instructions, copied them >initially to the stock 2k2 files for speechbuddy and made >sure the combo "cntrl/number" was enable in the RC3 setup. I >could only got the initial weather briefing to work:( Tried >many times but the request combination for clearance >delivery just wouldn't register. I tried the testing call >after each none response and never did lose the program >though. It just wouldn't do anything. You should switch SB to developer and debug mode and say the phrases again (no need to start FS2K2 for that). If SB recognizes them, it will print some feedback (which rule fired) in the main window, and then there seems to be a problem with the keycodes sent to RC3. If it doesnt, than there is either a problem with the rules, or a problem with the voice recognition itself (hardware?)>Dirk, if you see this, I took a short primer in XML and >noticed that one of the rules had a lower case "p" at the >start of the rule but finished with an upper case "P" to end >the rule set. Since the primer said XML was case sensitive I >corrected it to match. Havn't had the opportunity to see if >that made a difference. Speechbuddy didn't have a problem >with the mismatch but would appreciate any help. Maybe I had >some hidden spaces or something. Yeah, you are right, I didnt notice that. But it doesnt make any difference on my system either, it recognizes the rule with lower or uppercase tags ...Dirk

Hi Sam,>The only missing issue is that I can't change headings, >speed or altitudes. It probably relies to different key >commands PSS uses in their software. The rules for changing heading, speed and altitude use FSUIPC to set the corresponding values in FS2K2 directly, not via keystrokes. I could imagine that sophisticated panels like the PSS don't use the standard FS facilities and thus are not accessible through FSUIPC ...Dirk

Sam, Dirk, Thanks to both you guys for the help! Sam great job! please send me what you have when you get a chance. Looking at Dirk's post below yours I have a few things to try. All in all I'm happy with the use of speechbuddy:) I may end up learning a lot more about XML. It's about nine here in the St. Louis area and I've got to give up for the night, have to be at work at 4:00 am and it's the wife telling me to get to dinner/bed or else. Sometime she up for the long nights but I don't think so tonight. If you could send me the files Sam, I'd be grateful. again, thanks to you both. Charles

@ Dirk>The rules for changing heading, speed and altitude use FSUIPC to set >the corresponding values in FS2K2 directly, not via keystrokes. I >could imagine that sophisticated panels like the PSS don't use the >standard FS facilities and thus are not accessible through FSUIPC ...I think you're right on that. Most probably that's the case... I will therefore have to adjust the main MCD

Thanks Sam! Just got home and downloaded your files, appreciate the quick turnaround. Will give them a go in the next few hours. I did get the zoom in/out command working and finally got the RC3 commands to move on. Must have just not been speaking clearly enough. May head back for training sessions but need to get a flight in tonigh for my VA. Will post some feedback later tonight or tomorrow depending on the length of tonights flight, again thanks to both you and Dirk for all the help:) Charles