no module named freenect

[seawolf82]

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

[petermoz]

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3 .

[seawolf82]

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ... Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton notifications@github.com:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420 .

[seawolf82]

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ... Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton notifications@github.com:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420 .

[petermoz]

Hi Andrea,

Sorry, I have neither a Kinect or an ubuntu install to play with at the moment, so I can't try this out myself.

It sounds like freenect is working, can you try out the python wrappers from that project? Try running some of the examples at https://github.com/OpenKinect/libfreenect/tree/master/wrappers/python. If the python interface works there, but not in display_kinect.py then we can narrow it down.

Peter

On 2 April 2014 17:47, seawolf82 notifications@github.com wrote:

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix:

sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ... Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton notifications@github.com:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420

.

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39293716 .

[seawolf82]

Hi Peter, in this week, i tried wrapper python examples to look the python interface works there. So this works there, but not in display_kinect.py then we can narrow it down :) It would be nice if your project works with new release of ubuntu for example 14.04LTS with new library and new how-to step by step to recreate your project :) is very nice keyboard_anywhere.

Let you know

Andrea

2014-04-02 22:50 GMT+02:00 Peter Morton notifications@github.com:

Hi Andrea,

Sorry, I have neither a Kinect or an ubuntu install to play with at the moment, so I can't try this out myself.

It sounds like freenect is working, can you try out the python wrappers from that project? Try running some of the examples at https://github.com/OpenKinect/libfreenect/tree/master/wrappers/python. If the python interface works there, but not in display_kinect.py then we can narrow it down.

Peter

On 2 April 2014 17:47, seawolf82 notifications@github.com wrote:

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix:

sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ...

Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton notifications@github.com:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420

.

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39293716

.

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39381666 .

[seawolf82]

HI Peter,

i've got replicated your project in my netbook with ubuntu 14.04LTS

I've got downloaded:

PyQGLViewer-0.12 libQGLViewer-2.5.1 pyFluidSynth-1.2.4

I've installed all dependencies and freenect from repository, this is the same of neurodebian.org

To Compile PyQGLViewer-0.12, I've follow the istructions of the website but when i tried to testing PyQGLViewer examples i received the following error:

from PyQGLViewer import *

ImportError: /usr/lib/libQGLViewer.so.2: undefined symbol: gluCylinder

I've verified into /usr/lib/libQGLViewer.so.2 and it was found. When i tried to run display_kinect.py and keyboard_anywhere.py i received the same error.

Please can you help me?

Kind regards

Andrea

2014-04-03 8:59 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

Hi Peter, in this week, i tried wrapper python examples to look the python interface works there. So this works there, but not in display_kinect.py then we can narrow it down :) It would be nice if your project works with new release of ubuntu for example 14.04LTS with new library and new how-to step by step to recreate your project :) is very nice keyboard_anywhere.

Let you know

Andrea

2014-04-02 22:50 GMT+02:00 Peter Morton notifications@github.com:

Hi Andrea,

Sorry, I have neither a Kinect or an ubuntu install to play with at the moment, so I can't try this out myself.

It sounds like freenect is working, can you try out the python wrappers from that project? Try running some of the examples at https://github.com/OpenKinect/libfreenect/tree/master/wrappers/python. If the python interface works there, but not in display_kinect.py then we can narrow it down.

Peter

On 2 April 2014 17:47, seawolf82 notifications@github.com wrote:

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix:

sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ...

Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton notifications@github.com:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420

.

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39293716

.

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39381666 .

[petermoz]

Yep - this is a bug in the latest PyQGLViewer In setup.py on line 77, change

return [lib] to return [lib, 'GLU']

Then rerun python setup.py install. For some reason the GLU library needs to be explicitly linked

On 10 April 2014 04:33, seawolf82 notifications@github.com wrote:

HI Peter,

i've got replicated your project in my netbook with ubuntu 14.04LTS

I've got downloaded:

PyQGLViewer-0.12 libQGLViewer-2.5.1 pyFluidSynth-1.2.4

I've installed all dependencies and freenect from repository, this is the same of neurodebian.org

To Compile PyQGLViewer-0.12, I've follow the istructions of the website but when i tried to testing PyQGLViewer examples i received the following error:

from PyQGLViewer import *

ImportError: /usr/lib/libQGLViewer.so.2: undefined symbol: gluCylinder

I've verified into /usr/lib/libQGLViewer.so.2 and it was found. When i tried to run display_kinect.py and keyboard_anywhere.py i received the same error.

Please can you help me?

Kind regards

Andrea

2014-04-03 8:59 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

Hi Peter, in this week, i tried wrapper python examples to look the python interface works there. So this works there, but not in display_kinect.py then we can narrow it down :) It would be nice if your project works with new release of ubuntu for example 14.04LTS with new library and new how-to step by step to recreate your project :) is very nice keyboard_anywhere.

Let you know

Andrea

2014-04-02 22:50 GMT+02:00 Peter Morton notifications@github.com:

Hi Andrea,

Sorry, I have neither a Kinect or an ubuntu install to play with at the moment, so I can't try this out myself.

It sounds like freenect is working, can you try out the python wrappers from that project? Try running some of the examples at https://github.com/OpenKinect/libfreenect/tree/master/wrappers/python. If the python interface works there, but not in display_kinect.py then we can narrow it down.

Peter

On 2 April 2014 17:47, seawolf82 notifications@github.com wrote:

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix:

sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ...

Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton notifications@github.com:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420

.

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39293716

.

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39381666

.

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-40000178 .

[seawolf82]

Hi Peter,

i followed your istructions but not work, I tried to run python interface.py into example folder but received the same error:

from PyQGLViewer import *

ImportError: /usr/lib/libQGLViewer.so.2: undefined symbol: gluCylinder

Have you any ideas?

Please can you help me?

Thank you very much

Andrea

2014-04-10 1:44 GMT+02:00 Peter Morton notifications@github.com:

Yep - this is a bug in the latest PyQGLViewer In setup.py on line 77, change

return [lib] to return [lib, 'GLU']

Then rerun python setup.py install. For some reason the GLU library needs to be explicitly linked

On 10 April 2014 04:33, seawolf82 notifications@github.com wrote:

HI Peter,

i've got replicated your project in my netbook with ubuntu 14.04LTS

I've got downloaded:

PyQGLViewer-0.12 libQGLViewer-2.5.1 pyFluidSynth-1.2.4

I've installed all dependencies and freenect from repository, this is the same of neurodebian.org

To Compile PyQGLViewer-0.12, I've follow the istructions of the website but when i tried to testing PyQGLViewer examples i received the following error:

from PyQGLViewer import *

ImportError: /usr/lib/libQGLViewer.so.2: undefined symbol: gluCylinder

I've verified into /usr/lib/libQGLViewer.so.2 and it was found. When i tried to run display_kinect.py and keyboard_anywhere.py i received the same error.

Please can you help me?

Kind regards

Andrea

2014-04-03 8:59 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

Hi Peter, in this week, i tried wrapper python examples to look the python interface works there. So this works there, but not in display_kinect.py then we can narrow it down :) It would be nice if your project works with new release of ubuntu for example 14.04LTS with new library and new how-to step by step to recreate your project :) is very nice keyboard_anywhere.

Let you know

Andrea

2014-04-02 22:50 GMT+02:00 Peter Morton notifications@github.com:

Hi Andrea,

Sorry, I have neither a Kinect or an ubuntu install to play with at the moment, so I can't try this out myself.

It sounds like freenect is working, can you try out the python wrappers from that project? Try running some of the examples at https://github.com/OpenKinect/libfreenect/tree/master/wrappers/python . If the python interface works there, but not in display_kinect.py then we can narrow it down.

Peter

On 2 April 2014 17:47, seawolf82 notifications@github.com wrote:

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix:

sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi <andrea.finessi@gmail.com :

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ...

Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton <notifications@github.com :

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420

.

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39293716

.

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39381666

.

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-40000178

.

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-40029553 .

[seawolf82]

Hi Peter,

ignore my last email, I've got delete and unzip PyQGLviewer again and i'vegot modify setup.py with your istructions, then I run python setup.py install and now in the folder examples if i try to run python interface.py works!!!

afterwards i tried to run display_kinect.py and keyboard_anywhere.py but I received again the same error:

File "display_kinect.py", line 91, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0]

instead in keyboard_anywhere received the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 286, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable

Can you help me to resolve this issue?

Let me know

Regards

Andrea

2014-04-10 21:20 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

Hi Peter,

i followed your istructions but not work, I tried to run python interface.py into example folder but received the same error:

from PyQGLViewer import *

ImportError: /usr/lib/libQGLViewer.so.2: undefined symbol: gluCylinder

Have you any ideas?

Please can you help me?

Thank you very much

Andrea

2014-04-10 1:44 GMT+02:00 Peter Morton notifications@github.com:

Yep - this is a bug in the latest PyQGLViewer

In setup.py on line 77, change

return [lib] to return [lib, 'GLU']

Then rerun python setup.py install. For some reason the GLU library needs to be explicitly linked

On 10 April 2014 04:33, seawolf82 notifications@github.com wrote:

HI Peter,

i've got replicated your project in my netbook with ubuntu 14.04LTS

I've got downloaded:

PyQGLViewer-0.12 libQGLViewer-2.5.1 pyFluidSynth-1.2.4

I've installed all dependencies and freenect from repository, this is the same of neurodebian.org

To Compile PyQGLViewer-0.12, I've follow the istructions of the website but when i tried to testing PyQGLViewer examples i received the following error:

from PyQGLViewer import *

ImportError: /usr/lib/libQGLViewer.so.2: undefined symbol: gluCylinder

I've verified into /usr/lib/libQGLViewer.so.2 and it was found. When i tried to run display_kinect.py and keyboard_anywhere.py i received the same error.

Please can you help me?

Kind regards

Andrea

2014-04-03 8:59 GMT+02:00 Andrea Finessi andrea.finessi@gmail.com:

Hi Peter, in this week, i tried wrapper python examples to look the python interface works there. So this works there, but not in display_kinect.py then we can narrow it down :) It would be nice if your project works with new release of ubuntu for example 14.04LTS with new library and new how-to step by step to recreate your project :) is very nice keyboard_anywhere.

Let you know

Andrea

2014-04-02 22:50 GMT+02:00 Peter Morton notifications@github.com:

Hi Andrea,

Sorry, I have neither a Kinect or an ubuntu install to play with at the moment, so I can't try this out myself.

It sounds like freenect is working, can you try out the python wrappers from that project? Try running some of the examples at

https://github.com/OpenKinect/libfreenect/tree/master/wrappers/python. If the python interface works there, but not in display_kinect.py then we can narrow it down.

Peter

On 2 April 2014 17:47, seawolf82 notifications@github.com wrote:

Hi Peter,

I tried to recreate your project on ubuntu 10.04 and 14.04. in the 10.04 after installed all libraries and compiled freenect,libQLglViewer, PyQlGlviewer and pyfluidsinth, if you launch the command freenect-GLview, a window divided into 2 parts properly initializes the kinect. Then when launch from terminal sudo python display_kinect.py and keyboard_anywhere.py, the last crash, reports the following error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

while the window at the display_kinect.py remain grey.

Moreover, i've added udev rules into /etc/udev/rules.d

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

file name's rule its: 51-kinect.rules

and i restarted udev service: sudo service udev restart

Afterwards I tried to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

In the release debian-7 and 14.04 if you launch the command freenect-GLview, window are black and the kinect not work. In the web i found that new kernel when started, gspca_kinect module has been loaded, afterwards i removed the gspca_kinect with: sudo modprobe -r gspca_kinect

and Permanent fix:

sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I tried again to unplug/plug-in the kinect into usb port and I retried to restart the two components, but the issue still occours again.

Can you help me to resolve this issue at least on ubuntu 10.04 ??

Thank You

Kind Regards

Andrea

2014-03-30 12:57 GMT+02:00 Andrea Finessi < andrea.finessi@gmail.com>:

HI peter, i found kinect 360 to try your project, but i've got another problem

Step 1.) Plug in the Kinect, both into the wall and into your USB port. Both the front LED, and power adapter plug LED, should be green (sometimes you need to plug and unplug several times for this). lsusb should show the device is connected: lsusb ... lots of other devices ...

Bus 001 Device 058: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 001 Device 059: ID 045e:02ad Microsoft Corp. Xbox NUI Audio Bus 001 Device 060: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

Step 2)

I've added udev rules into /etc/udev/rules.d as following:

ATTR{product}=="Xbox NUI Motor"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02b0", MODE="0666"

ATTR{product}=="Xbox NUI Audio"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ad", MODE="0666"

ATTR{product}=="Xbox NUI Camera"

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02ae", MODE="0666"

Kinect for Windows

SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02c2", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02be", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="045e", ATTR{idProduct}=="02bf", MODE="0666"

file name's rule his: 51-kinect.rules

Then i try the follow command into terminal to restart udev rules: sudo /etc/init.d/udev restart

Now when i try to launch display_kinect.py, the window are grey and not running instead in the keyboard_anywhere.py, I receive this error:

Traceback (most recent call last): File "keyboard_anywhere.py", line 287, in animate depth, timestamp = freenect.sync_get_depth() TypeError: 'NoneType' object is not iterable Could not claim interface on camera: -6 Error: Invalid index [0] Error: Can't open device. 1.) is it plugged in? 2.) Read the README

I search to web this error and i found this:

Could not claim interface on camera: -6 Could not open device -> The problem: modern kernels have a video driver for Kinect. Temporary fix: sudo modprobe -r gspca_kinect

Permanent fix: sudo nano /etc/modprobe.d/blacklist.conf Add this line anywhere: blacklist gspca_kinect

I have read the istructions and i've got tried the temporary fix and then permanent fix but the issue still again.

Please can you help me to resolve this issue?

Thank You

Kind Regards

Andrea

2014-03-20 11:43 GMT+01:00 Peter Morton < notifications@github.com>:

Hey Andrea,

Regarding the fluidsynth error - did you install the python bindings as well? Looks like I might have omitted that from the readme. It's been a while since I've used this, but I'm guessing I got it from http://code.google.com/p/pyfluidsynth/

When you start the GUI the grey screen is expected (see the usage section of the readme). Press ENTER to start processing Kinect data. To check that the GUI is working, press "g" and it will display a grid that you can move around with the mouse.

I think you'll probably have to install some udev rules (although installing libfreenect might take care of this for you). If the script runs with "sudo" but not without, then that's a sign to fix up udev. Check out the libfreenect project for instructions

Cheers, Peter

On 14 March 2014 02:12, seawolf82 notifications@github.com wrote:

Hi,

i've tried to replicate your project on my debian testing. Her name's urania :) I read all your istructions, but I have some difficult to run your project. Actually when i try tu run display_kinect.py and keyboard_anywhere.py i received this error for keyboard_anywhere.py : Import error No module named fluidsynth, but fluidsynth is installed on the system, instead when i run display_kinect.py i see the window grey but the application does nothing. Regarding the kinect you just attach it to the system or do I have to change the udev rules?

Please can you help me?

Let me Know.

Andrea

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3> .

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-38153420

.

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39293716

.

Reply to this email directly or view it on GitHub<

https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-39381666

.

Reply to this email directly or view it on GitHub< https://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-40000178

.

Reply to this email directly or view it on GitHubhttps://github.com/petermoz/keyboard-anywhere/issues/3#issuecomment-40029553 .