Jump to content

Help! - MB Kinect Crashing Immediately on Windows 8.1


Faceman09
 Share

Recommended Posts

Cynful

Kay Chef,

 

I've trained the HELL outta this profile now :)

Speech recognition working well and controling MB3 (Press Ctrl P and whatnot) thought he whole speech recognition listening to the movie and opening random programs behind remains problematic.

 

Keen to help out as the more I play with it the more I want it working as it should. Anything at all I can do to help just say.

 

Cyn

 

POSTSCRIPT: >> Anyone have any idea how to get a more natural voice than Anna for Win7 32bit? Doesn't seem to want to allow any SAPI5 voices and this chicky is bugging the hell outta me now.

Link to comment
Share on other sites

chef

Kay Chef,

 

I've trained the HELL outta this profile now :)

Speech recognition working well and controling MB3 (Press Ctrl P and whatnot) thought he whole speech recognition listening to the movie and opening random programs behind remains problematic.

 

Keen to help out as the more I play with it the more I want it working as it should. Anything at all I can do to help just say.

 

Cyn

 

POSTSCRIPT: >> Anyone have any idea how to get a more natural voice than Anna for Win7 32bit? Doesn't seem to want to allow any SAPI5 voices and this chicky is bugging the hell outta me now.

I will pm you. I have three possible voice to give you.

  • Like 1
Link to comment
Share on other sites

chef

Also, that is great news the recognizer has finally started working for you.

 

Just so I know.

 

This was the last version release we were working on that finally worked?

 

You are able to browse media browser using "go to" key words with the name of the media item following?

 

You are able to initiate playback of items by using the keywords "play media"?

 

Are you able to give commands such as "what time is it?"?

Link to comment
Share on other sites

Cynful

My bad @@chef.Didn't mean to mislead you on that.

 

Only WINDOWS speech recognition working, not the one built into MBKinect. Hence the standard system commands of "Move left" "Backspace", "Press Control P" etc.

 

Still RED LIGHT and lack of commands whenever I try to get it to work through MBKinect, which hates me.

538ff44b4343d_MBkinectGUIwhichhatesme.pn

Link to comment
Share on other sites

chef

My bad @@chef.Didn't mean to mislead you on that.

 

Only WINDOWS speech recognition working, not the one built into MBKinect. Hence the standard system commands of "Move left" "Backspace", "Press Control P" etc.

 

Still RED LIGHT and lack of commands whenever I try to get it to work through MBKinect, which hates me.

538ff44b4343d_MBkinectGUIwhichhatesme.pn

 

@@Cynful

 

Okay, so you are using the Designation "Media"

 

Also, make sure MBKinect is the only Speech recognition application open in windows. Shut down Windows Speech Recognition.

 

Try to use the Command:

 

 

"Media"

{the green light on the Kinect should start to blink}

"Start Listening"

 

 

Are you using the last updated version?  If you download this 32bit installer, and install it. It should install into the Proper directory, and save all you settings:

 

 

https://dl.dropboxusercontent.com/u/46151346/MBK32bit.zip

Link to comment
Share on other sites

Cynful

Annnnnd the long wekend has landed.

 

Okay @@chef :) Normally have the WINDOWS Speech Rec closed, was just playing around with it when I screenshot it.

 

Downloaded

Installed

Open MBKinect

Flashing Red-Yellow then solid Red as GUI opens.

Set designation as it appears to wipe it everytime I open MBKinect anew. (could this be problematic? It seems to hold the name as long as MBKinect is open ...)

 

"Media" ... "Media" ... "Media" ... ... "MEDia" ... "MeDIA" ... "MEdiA" ... "meDIa" "MehdEEA" ... "Maydayah" ...

 

Still no green Chef.

 

Playing around. All kinect LED.EXE thingies work to change state of kinect led. Just no love on listening :)

 

I might try and stay up till your time-ish tonight ;)

 

Cyn

Link to comment
Share on other sites

chef

Interesting how the system name is not saving.

 

When you restart the application, after a fresh install, does the designation save?

 

If you look in the folder structure at "\settings\global\Speech\Grammars" you will see an XML file called designation.

 

If you were to read this file, can you see at the bottom of the file nodes:

  <rule id="designationName">
    <one-of>
      <item>Media</item>
      <item>Start Listening</item>
      <item>Listen Up</item>
      <item>You there</item>
    </one-of>
  </rule>

Where the first "item" node in the "one-of";  holds the designation name,  which I have edited in the example to read "Media"?

 

If you where to change the designation name, and reopen this XML file, are you able to see the change save in the XML?

  • Like 1
Link to comment
Share on other sites

Cynful

Okay @@chef.. this may be part of the problem.

<rule id="designationName">
<one-of>
<item />
<item>Start Listening</item>
<item>Listen Up</item>
<item>You there</item>
</one-of>
</rule>

Open MBKinect

set designation

Designation shown on GUI

Check xml

NO CHANGE TO DESIGNATION NAME

 

.. have we found it?!?!?!?!!!!!!

 

Cyn

 

** EDIT:

Exit MBKinect

Made manual change to XML

Open MBKinect

Check xml

Empty name value again

 

Bastard wipes on open!

Edited by Cynful
Link to comment
Share on other sites

chef

Yes! We have found it!!! This is fantastic! When I get home I will immediately look at the code for this, and make the proper adjustments.

 

This is the last thing I would have thought it was. Very glad you brought it up.

Edited by chef
  • Like 1
Link to comment
Share on other sites

chef

Okay I am finding it hard to reproduce the missing grammar node in the XML file.

 

If that node is missing then there is no way for the speech recognizer to work.

 

 

@@Cynful, is it possible to try and load the application with the default designation name ("Kinect") and see if it shows up in the XML file?

 

The second test would be to see if you are able to speak to the recognizer using:   "Kinect" ... "Start Listening".

 

I will continue to work on possible reasons why the XML file is not being completed in the mean time.

  • Like 1
Link to comment
Share on other sites

Cynful

Chef. .. my noobishness is showing

 

Do you want me to try and

 

a ) run the app as it stands now and change the des to "Kinect"

b ) manually change the XML des to 'Kinect" and then run the app

c ) reinstall the mofo and hope the XML is set as "Kinect" to start with

 

On previous installations there is no designation set (on the GUI screen at least) on first load - as in there is no name above the tracking information on the left...

Edited by Cynful
Link to comment
Share on other sites

Cynful

Righty-o @@chef.

 

Changed in GUI to kinect. - value set in GUI but not XML

Changed manually to Kinect and run. - wipes on application run to no value.

Reinstall

Attempt "Kinect, start listening" - it's not.

 

Sorry none of these helped.

Link to comment
Share on other sites

chef

I wish I could reproduce this.

 

That particular node is really important. It is what tells the speech recognizer that you maybe asking it to start listening.

 

It was the only way to get around possible Mis recognitions with ambient noise and the kinect microphone array.

 

But, since this is a reoccurring issue, I may have to re think that process.

 

In the application xml (found in "settings\global") the designation is also held in a node.

 

Can you confirm that when you change the designation name that that node changes?

Link to comment
Share on other sites

Cynful

No designation in that XML @@chef.

 

Media Browser Kinect\settings\global\Application Settings.xml

<?xml version="1.0" encoding="utf-8"?>
<Global_Settings>
  <Server_Information>
    <MediaBrowserServerAddress>10.1.1.4</MediaBrowserServerAddress>
    <MediaBrowserServerPort>8096</MediaBrowserServerPort>
  </Server_Information>
</Global_Settings>

Ignore my ignorance :) But is there a reason the designation is wiped on restarting MBK? As in when I set the designation manually and then start MBK again... seems redundant that it clears it's own designation upon load.

Edited by Cynful
Link to comment
Share on other sites

chef

Well, the Designation is actually saved in the "Application Setting.XML" file.

 

Mine Looks like this:

<?xml version="1.0" encoding="utf-8"?>
<Global_Settings>
  <Server_Information>
    <MediaBrowserServerAddress>192.168.0.5</MediaBrowserServerAddress>
    <MediaBrowserServerPort>8096</MediaBrowserServerPort>
    <MediaBrowserServerMACAddress>--:--:--:--:--:--</MediaBrowserServerMACAddress>
  </Server_Information>
  <User_Options>
    <Override_Enabled>False</Override_Enabled>
    <Override_Name />
  </User_Options>
  <Designation>
    <Designation_Name>Kinect</Designation_Name>
    <Designation_Audio_Duration_Min>550</Designation_Audio_Duration_Min>
    <Designation_Audio_Duration_Max>750</Designation_Audio_Duration_Max>
  </Designation>
</Global_Settings>

(I manually edited out the MAC address of my computer in the example above)

 

 

The "Designation.XML" is a grammar (command list) to tell the speech recognizer what to listen for. It is created based on what is saved in the "Application Settings.XML" file.

 

This way we are loading the proper saved Name as a command to the speech recognizer.

 

 

However, in this case:  both the XML files are missing information. 

 

I am still looking for why this is happening, and I hope to have a fixed version some point today.

 

I really appreciate you hangin' in there and taking the time to test @@Cynful, you have been a great  help. A lot of things have been reconfigured are starting to work. 

Edited by chef
  • Like 1
Link to comment
Share on other sites

Cynful

Okay @@chef.

<User_Options>
    <Override_Enabled>False</Override_Enabled>
    <Override_Name />
  </User_Options>
  <Designation>
    <Designation_Name>Media</Designation_Name>
    <Designation_Audio_Duration_Min>550</Designation_Audio_Duration_Min>
    <Designation_Audio_Duration_Max>750</Designation_Audio_Duration_Max>
  </Designation>

I manually inserted those absent lines into the application setting.xml and gues what.

 

IT PHREAKING WORKS.

 

EDIT: Perhaps premature.

 

"Media" *blinking green light* "Start Listening" *solid green light*

 

Go To Movies

Go To Television

What Time Is It?

Go To Bloody Anything

 

*redlight*

GRRRRRRRRRRRRRRRRR

 

Soooooooo... in summary. WoooooT. Slowly getting there :D

Edited by Cynful
  • Like 1
Link to comment
Share on other sites

chef

@@travelmanics

 

We could really use your help here man if you have a couple minutes to spare. we need a second tester, because I can't reproduce what is happening here.

 

 

Here is a run down of what is happening so far. Cynful and I have narrowed down the reason why MBkinect hasn't been working. If we can squash this bug then MBKinect works!!

 

 

After the install of the kinect application a "first run setup" is started.

 

During this time Cynful and I seem to have been able to get control of the LED lights on the Kinect without issue.

 

However, there is an XML file that is created, which is very important, the "Application Settings.XML" file. (Found in "C:\ProgramData\Media Browser Kinect\settings\global" folder)

 

This file contains the designation name for the system. Without this the application will not work.

 

On cynfuls' computer, he in unable to create a full formed Application Settings document.  I have searched the code over and over and can not explain this bug.  

 

Is it possible for you to try and install the kinect app, run the First Run setup, and check the "Application Settings.XML" file to see if yours is complete.

 

in the end it should look like this:

<?xml version="1.0" encoding="utf-8"?>
<Global_Settings>
  <Server_Information>
    <MediaBrowserServerAddress>192.168.0.5</MediaBrowserServerAddress>
    <MediaBrowserServerPort>8096</MediaBrowserServerPort>
    <MediaBrowserServerMACAddress>--:--:--:--:--:--</MediaBrowserServerMACAddress>
  </Server_Information>
  <User_Options>
    <Override_Enabled>False</Override_Enabled>
    <Override_Name />
  </User_Options>
  <Designation>
    <Designation_Name>Kinect</Designation_Name>
    <Designation_Audio_Duration_Min>550</Designation_Audio_Duration_Min>
    <Designation_Audio_Duration_Max>750</Designation_Audio_Duration_Max>
  </Designation>
</Global_Settings>

If the file forms like the example above, then I will know weather or not I have to change code based on OS type (example 64bit or 32bit).

 

Currently I can't explain why this is happening.

 

Like i said, if we can squash this bug, then MBkinect is finally working.

 

Here is a 64bit download:

 

 

https://dl.dropboxusercontent.com/u/46151346/MBK64bit.zip

  • Like 1
Link to comment
Share on other sites

chef

@@Cynful

 

The only thing I can think of, to fix the issue, is to ship the installer, with the Application Settings XML file already complete.

 

Currently, the First Run setup handles creating the File, but apparently it is not able to write it properly.

 

If the installer writes the file automatically, it might fix all our issues.

Link to comment
Share on other sites

Cynful

Got a new issue for you @@chef.

 

In GUI>

 

"Media" - green light. YAY.

Change device to MEDAIONE\Mediaone\MB CLASSIC (or whatever it is) - Close

"Media" - NOTHING

"MEDIA" - Nudda

Designation tab - System name - leave as "Media" - Close

"Media" - green light.

 

 

Something seems to be cancelling the designation out when I choose the device...

 

So if you ship the file autocompleted ... changes will be made to the file during first run to align it to the specific system?

Edited by Cynful
  • Like 1
Link to comment
Share on other sites

chef

Got a new issue for you @@chef.

 

In GUI>

 

"Media" - green light. YAY.

Change device to MEDAIONE\Mediaone\MB CLASSIC (or whatever it is) - Close

"Media" - NOTHING

"MEDIA" - Nudda

Designation tab - System name - leave as "Media" - Close

"Media" - green light.

 

 

Something seems to be cancelling the designation out when I choose the device...

 

So if you ship the file autocompleted ... changes will be made to the file during first run to align it to the specific system?

 

 

Yes the First Run will make changes to the XML file, but won't create it.

 

As for the first question. If you change the device or open the side menu, the speech recognizer will automatically time out, so you will have to ask for the system name again, and then tell it to start listening.

 

Could you test one of the general context commands for me?

 

when you have the app listening to you could you ask it: "What time is it?"

 

Also, when it starts listening, could you ask it: "Stop Listening"

 

then request that is listens again?

  • Like 1
Link to comment
Share on other sites

Cynful

@@chef

 

Not problemo. Thee seems to be a short time gap between when you set the device and when you can say the name .. a slightly longer delay as my system had decided to slow down a bit.. problem fixed now it isn't chugging.

 

Soooo ... No general context commands work. :(

 

Nothing on either "What time is it?" or "Stop listening"

 

I get SPEECH RECOGNISED: MEDIA

        SPEECH RECOGNISED: START LISTENING

 

and nothin' else...

Edited by Cynful
Link to comment
Share on other sites

chef

HaHa! I figured it out! MBKinect HAS to be run as administrator in order to write the proper information to the "ProgramData" Folder.

 

What sucks about this is that I has built a MBClassic interface which started the Kinect application from inside MBClassic.

 

This is now irrelevant because the UAC prompt will popup and there is no way to click "Yes Run as Admin" while you are using MBlassics 10foot interface.

Link to comment
Share on other sites

Cynful

I recognised a WHOLE HEAP o' them words! :D

 

That said, I'm glad you're excited. I've tried running with Admin privs AND without .. guessing you're talking about something else though ;)

Link to comment
Share on other sites

chef

@@chef

 

Not problemo. Thee seems to be a short time gap between when you set the device and when you can say the name .. a slightly longer delay as my system had decided to slow down a bit.. problem fixed now it isn't chugging.

 

Soooo ... No general context commands work. :(

 

Nothing on either "What time is it?" or "Stop listening"

 

I get SPEECH RECOGNISED: MEDIA

        SPEECH RECOGNISED: START LISTENING

 

and nothin' else...

 

 

Well, at least we have taken a step closer to understanding why the app wasn't working.

 

Once we get general context commands working, then the real fun will start. Accessing Media Browser.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...