Infinite Wave Reco Complete after starting XBMC

[squatingyeti]

Awesome on the sound setup. I'm gonna mess with that today. I'll test and see what caused the VC freeze and if I can duplicate it.

[squatingyeti]

Ok, the freeze was not actually a freeze at all, just a bit of a hang. Also, not caused by VC, but rather when vera decides it wants to act up and take too long to respond to a status check of a device. I'm guessing this is more of a UI7 issue still as those on UI5 don't seem to run into this very much, but it seems to happen after messing with stuff like PLEG a bit and can be resolved by a precautionary reboot of the vera after several changes are made.

On another note, I read where you said kinect can't interpret numbers correctly and needs a payload iirc. Is there a quick way to do this or will I literally have to go through each number connecting one-1 and so on?

[jitterjames]

It isn't the Kinect itself that has the number limitation so just because you are using the Kinect as a microphone does not mean it will affect you.  It is only a problem if you are running the SP version of VC and you select a specific recognizer such as Microsoft Server Speech Recognition Language - Kinect (en-US) in the main options tab.

Actually, all of the SP engines seem to have difficulties with numbers, but the Kinect engines completely reject numbers.

I'm pretty sure that when Microsoft releases any kind of speech api, they never actually use it and never fix any of the bugs that people report.  There are still major bugs in the speech API (SAPI) left over from Vista.  In most cases I have had to create workarounds to try to cope with them.  And in some cases I ended up with something better anyway.  The speech platform version 11 has a new set of issues for us to discover and have fun with.

But you know, it's only version 11 of the Windows Speech Platform, so we can still consider it a beta for now. 

[squatingyeti]

  They only realize they've made a mistake when they skip version numbers. I patiently await the jump from 11 to 13 (13 being bad luck we might get straight to 14 if we're lucky).

So am I correct in the understanding I need to make a payload tying each word with each number i.e one - 1 to the highest number I'll likely need? Dear god, 2001 A Space Odyssey will be the death of me. HAL!

[nime5ter]

Since VC supports partial matching of payload phrases, maybe you can just try saying commands like "Play movie 2001" as "Play movie Space Odyssey"? (Make sure that "submatch" is checked in those payload xml files, of course.)

Stick to using a digit ->phrase payload xml file just for things where you really do want to use a number value -- e.g. for turning volume to a particular level between 1 and 100, or light levels etc. Then hopefully a list from 0 to 100 will cover most situations . Actually, since in those cases you're most likely to use larger increments "dim light to (10/50/80) percent", "set volume to 20/25/30", you might be able to get away with a list of multiples of five or ten or whatever.

[jitterjames]

So am I correct in the understanding I need to make a payload tying each word with each number i.e one - 1 to the highest

I don't know.  It depends on your setup.  Which version of VC are you using and which speech engine?

[squatingyeti]

Yeah nime5ter, I think I can get away with using increments like that and just catch special cases like 21/22 jump street.

James, I'm using the latest VC 2.1.2.9 and the MS speech recognition for kinect-us

[jitterjames]

as Nime5ter said you can probably just say "jump street" instead of "21 jump street".

Actually, with SP and a Kinect engine, when using payloadRanges and payloadLists VC will automatically convert numbers to phrases for you (as though you had created a payloadXML with words for the phrases and integers for the values.  It only does this in English though.  You can try it.  The problem then arises (and I think you have seen this), that if you have too many similar commands with payload ranges in the same group, then one of the MS bugs will surface and your groups will not load.  You will get an error about a rule reference not found or something to that effect.

Personally (I think I'm repeating myself),  I would try the non-SP version first to see if it can work for you.  Far less headaches.  It still works with Kinect though *possibly* not as well.  You should try it to make sure.

[squatingyeti]

Yeah, I'll give the regular version a shot and see how it goes. Do I need to still use the kinect speech recognition or do I switch to the regular one and not worry about the kinect beam forming and whatnot?

[jitterjames]

It's up to you. See what works best for you.

Beam forming etc. is still supported with the standard engine.  The SP recognizers were apparently tuned to the Kinect's audio profile.