Compatibility / Create image generator failed

[FernandoFr]

I'm usign AS3OpenNI with the Asus XtionPro, but anything beyond
version 1.0.0 gives me the same error "Create image generator failed".

I've tried version 1.0.9 and 1.3.0 of AS3OpenNI with no different
results.

This is the log/trace:
nite_session_socket - Bound to: 127.0.0.1:9501
nite_session_socket - Connection from: 127.0.0.1:52605
Console: Gesture feature turned on
Create image generator failed: Can't create any node of the requested
type!

Maybe its an incompatibility with the XtionPro? Or the software
combination?

Currently i have:
- PrimeSense driver package 3.1.2.0
- PrimeSense Sensor 5.0.2.3
- PrimeSense NITE 1.3.1.6
- OpenNU 1.2.0.7

Should uninstall and upgrade, maybe?

Thanks in advance! Keep up!

[Homer]

Hi

This is an error which can has several explanations.
Does the NIViewer C++ sample work ?
If not, try to fix that first, it is probably a driver issue.

Does the kinect display the IR light when the server is running ?

Let me know

Homer.

[FernandoFr]

NIViewer runs, showing only the depth map.

The IR camera only doesn't even light when the error occurs, only
lights using version 1.0.0 of AS3OpenNI.exe.

Do I need to keep the server running before lauching the AIR samples?

On Aug 23, 3:04 pm, Homer <homer.co...@gmail.com> wrote:
> Hi
>
> This is an error which can has several explanations.
> Does the NIViewer C++ sample work ?
> If not, try to fix that first, it is probably a driver issue.
>
> Does the kinect display the IR light when the server is running ?
>
> Let me know
>
> Homer.
>

[Homer]

No, you don't.
The as3openni lib runs the server and terminates it when the flash app is closed (but sometimes there is a bug and you have to kill the process with the task manager by yourself. The IR camera is still on and the next launch doesn't work till you stop the server manually)

Maybe there is something wrong with your configuration or your platform, hard to say, sorry.

Homer

[FernandoFr]

> The as3openni lib runs the server and terminates it when the flash app is closed (but sometimes there is a bug and you have to kill the process with the task manager by yourself. The IR camera is still on and the next launch doesn't work till you stop the server manually)

I've noticed this behaviour. It keep AS3OpenNI and XNSensorServer
running. Both must be killed manually.

> Maybe there is something wrong with your configuration or your platform, hard to say, sorry.

Anyone ever reported this problem with Asus Xtion?

The error "Create image generator failed" is sent from OpenNI /
PrimeSense Nite, not from AS3OpenNI?

Should I try OpenNI groups? I've already searched, but haven't found
"Create image generator..." issues...

[Homer]

Unfortunately, platform and drivers issues are hard to resolve.
The best thing would be to post that on openni groups.
And yes, it is this API (or the primesense implementation) which outputs your message, typically "could not create any node...." occurs when you give bad parameters to initialize the sensor.

Another solution would be to debug the server part with a visual studio (express works very well) if you have enough courage ;)

This is what I did when I discovered the primesense framework and I discovered some useful information. Put a breakpoint into the source (you can use the nite samples provided by primesense, they are pretty simple to understand) and see what happens more precisely near the initialization part of the sensor.

Hope this helps...
Homer

[FernandoFr]

That's ok.

I'll try OpenNI groups before anything more advanced ;)

Thanks, Homer!

On Aug 23, 5:42 pm, Homer <homer.co...@gmail.com> wrote:
> Unfortunately, platform and drivers issues are hard to resolve.
> The best thing would be to post that on openni groups.
> And yes, it is this API (or the primesense implementation) which outputs your message, typically "could not create any node...." occurs when you give bad parameters to initialize the sensor.
>
> Another solution would be to debug the server part with a visual studio (express works very well) if you have enough courage ;)
>
> This is what I did when I discovered the primesense framework and I discovered some useful information.  Put a breakpoint into the source (you can use the nite samples provided by primesense, they are pretty simple to understand) and see what happens more precisely near the initialization part of the sensor.
>
> Hope this helps...
> Homer
>

[Homer Simpson]

Hey I think I've found your problem.

Night is the mother of counsel ;)

I read some stuffs about the Asus XtionPro sensor and it seems it supports only depth camera, not RBG camera.

So, if you read the documentation about the configuration of the NITE/OpenNI middlewares, more precisely the XML file part, you will find information about concept called productionNodes.

In these XML configuration files, you have to define which node you want to enable to initialize your sensor.

Example (in the Sample-Tracking.xml file under your NITE installation, folder "Data" )

...

<ProductionNodes>

<Node type="Depth">

<Configuration>

<MapOutputMode xRes="640" yRes="480" FPS="30"/>

<Mirror on="true"/>

</Configuration>

</Node>

<Node type="Gesture" />

<Node type="Hands" />

</ProductionNodes>

...

So, like I said yesterday, check on your XML file to see if the Image ProductionNode is enabled, and try to comment it.

I should have known when you said that your sensor displayed only the infrared part...

This should work !

This is the first step to see NITE working, and then you will have to modify the CPP sources of the AS3OpenNI project to add more compatibility for other devices than Microsoft Kinect. 

Hope this helps

Homer.

2011/8/24 FernandoFr <fernando...@gmail.com>

[FernandoFr]

> Night is the mother of counsel ;)

Absolutely. It's an understimated resource of solutions!

Fantastic. I'll try it right now!

Thank you again, Homer!

[Homer]

You're welcome !

Homer

[FernandoFr]

In my SamplesConfig.xml I have the following production nodes:

<ProductionNodes>
<Node type="Depth" name="Depth1">
<Configuration>

<Mirror on="true"/>
</Configuration>
</Node>

<Node type="Image" name="Image1" stopOnError="false">

<Configuration>
<MapOutputMode xRes="640" yRes="480" FPS="30"/>
<Mirror on="true"/>
</Configuration>
</Node>

<!--
<Node type="Audio" name="Audio1"/>
-->
</ProductionNodes>

That means that my Node Image is enabled...
Excluding the Node "Image" doesn't cause any different behaviour.
NiViewer shows only the depth map. The right area show the message
"Image stream is OFF".

I've tried to change the values of Node Image OutputMode to lower
values (320x240) but nothing changed.

I can use 640x480 on the Node Depth, anything higher than this causes
an "The value is invalid!" error.

Any clue? I'll try the OpenNI groups tomorrow.

Thanks, man!

On Aug 24, 4:18 am, Homer Simpson <homer.co...@gmail.com> wrote:
> Hey I think I've found your problem.
>
> Night is the mother of counsel ;)
>
> I read some stuffs about the Asus XtionPro sensor and it seems it supports
> only depth camera, not RBG camera.
>
> So, if you read the documentation about the configuration of the NITE/OpenNI
> middlewares, more precisely the XML file part, you will find information
> about concept called productionNodes.
>
> In these XML configuration files, you have to define which node you want to
> enable to initialize your sensor.
>
> Example (in the Sample-Tracking.xml file under your NITE installation,
> folder "Data" )
>

> *...*
> *<ProductionNodes>*
> * <Node type="Depth">*
> * <Configuration>*
> * <MapOutputMode xRes="640" yRes="480" FPS="30"/>*
> * <Mirror on="true"/>*
> * </Configuration>*
> * </Node>*
> * <Node type="Gesture" />*
> * <Node type="Hands" />*
> *</ProductionNodes>*
> *...*
>
> So, like I said yesterday, check on your XML file to see if the *Image
> *ProductionNode

> is enabled, and try to comment it.
>
> I should have known when you said that your sensor displayed only the
> infrared part...
>
> This should work !
>
> This is the first step to see NITE working, and then you will have to modify
> the CPP sources of the AS3OpenNI project to add more compatibility for other
> devices than Microsoft Kinect.
>
> Hope this helps
>
> Homer.
>

> 2011/8/24 FernandoFr <fernandodefra...@gmail.com>

[Homer Simpson]

Yep, depth camera resolution can't be higher than 640x480.

Ok it seems that the NIViewer sample works well but commenting the
image node should disable the rgb camera initialization. it's
strange.. but nevermind.

Now, try the NITE sample instead.
AS3OpenNI is based on that implementation, so if these samples doesn't
work, AS3OpenNI won't work too.

If you have troubles when running the samples, try to edit the XML
config files under your NITE installation "data" folder.
Then, (like I said a few days ago), you will have to compile the C++
server side of the AS3OpenNI project to exclude the Image node.

Let me know.

Homer.

[FernandoFr]

I've tested the NITE samples, all but Sample-SingleControl are
working, which gives me this output:

1286 INFO OpenNI version is 1.2.0 (Build 7)-Win32 (May 9 2011
12:20:55)
1874 INFO Filter Info - minimum severity: ERROR, masks: NONE
Setting resolution to VGA
Please perform focus gesture to start session
Hit any key to exit

All XMLs don't use an Image Node, only Depth, Scene, User and Hands
Nodes.

My C++ knowledge is still poor, I'm considering buying a real Kinect.
Asus Xtion is turning things more complicated... It seems that most
people are experimenting with the real one... so the compatibility
issues start to get in the way.

Thanks for the insight, Homer!

On Aug 25, 3:48 am, Homer Simpson <homer.co...@gmail.com> wrote:
> Yep, depth camera resolution can't be higher than 640x480.
>
> Ok it seems that the NIViewer sample works well but commenting the
> image node should disable the rgb camera initialization. it's
> strange.. but nevermind.
>
> Now, try the NITE sample instead.
> AS3OpenNI is based on that implementation, so if these samples doesn't
> work, AS3OpenNI won't work too.
>
> If you have troubles when running the samples, try to edit the XML
> config files under your NITE installation "data" folder.
> Then, (like I said a few days ago), you will have to compile the C++
> server side of the AS3OpenNI project to exclude the Image node.
>
> Let me know.
>
> Homer.
>

[Farshid Tavakoly]

Hey Guys,
I have the same problem with my camera also "Asus Xtion Pro" it would be nice to get this camera also works with this server. The camera works very well and is stable and you can mount it anywhere.
Would appreciate that together we could come up with the solution and perhaps in the future have the solution in the XML where you can choose which camera you want to use.
Many thanks
Farshid

[Homer Simpson]

Hey Frashid, 

I don't understand, in the Asus Xtion Pro page specification, I don't see there is a RGB camera, only depth sensor.

Is that true ? You say your camera works well, do you mean like any webcam ?

I don't know this product very well, but I read several wiki/pages which indicate no RGB camera...

Maybe I'm wrong.

I advise you to read the openni documentation, specifically the Sensor-Related Production Nodes part.

http://www.openni.org/documentation

I think your problem occurs while trying to initialize Image production node which doesn't exist...

Homer.

2011/8/26 Farshid Tavakoly <fars...@gmail.com>

[Farshid Tavakoly]

Hello Homer,

Apologize that I am not so clear at times but what I meant was that I have tested all the samples files that came with when you installed OpenNi for the developer but still I get problems running the server.

However, I have the latest OpenNi and Prime's drivers that can cause problems. I followed the topic and you are right that you should probably take away some of the xml where there are RGB, and I also think we should take away what you have for the resolution of the camera.

As soon as we get a new update server on the PC side maybe I can get this to work.

Have you openNi version as it is required to run this server or does it work for you with the latest update from OpenNi ? 

Is that possible you can provide me this files that I can try it?

Im Flash developer and it should be nice to get some sample working only with Flash and not with Flex. 

My skills in C and C++ is very bad so if someone can even recompile the server it would be great.

Many thanks.

[Homer Simpson]

No problem man, I tried to understand in order to help you as best I can ;)

When a was working with openNI and NITE (I'm now working with the Microsoft Kinect SDK, so no OpenNI installation anymore), I never upgade my framework version of both midllewares and it worked fine !

I read some stuffs about latest version of openNI and I saw several guys who had problem with that.

My versions were 1.0.0 for OpenNI, 1.3.0 for NITE and I stayed in 1.0.9 for AS3OpenNI.

I've identified the C++ code part which initialize rhe RBG part and probably which causes the crash of the application.

I can try to comment this part and recompile the server but I'm not sure of the result...

Which version of AS3OpenNI do you use ?

Homer

2011/8/26 Farshid Tavakoly <fars...@gmail.com>

[Farshid Tavakoly]

Hi Homer,

Great thanks,

I use the recent verion of AS3OpenN which that is 1.3.0

Many thanks

[Homer]

I'm busy with my job but I will find some time to do that, evenings or
week end.

Homer.

On Aug 26, 11:43 am, Farshid Tavakoly <farsh...@gmail.com> wrote:
> Hi Homer,
> Great thanks,
> I use the recent verion of AS3OpenN which that is 1.3.0
> Many thanks
>

> On Fri, Aug 26, 2011 at 11:23 AM, Homer Simpson <homer.co...@gmail.com>wrote:
>
>
>
>
>
>
>
> > No problem man, I tried to understand in order to help you as best I can ;)
>
> > When a was working with openNI and NITE (I'm now working with the Microsoft
> > Kinect SDK, so no OpenNI installation anymore), I never upgade my framework
> > version of both midllewares and it worked fine !
> > I read some stuffs about latest version of openNI and I saw several guys
> > who had problem with that.
> > My versions were 1.0.0 for OpenNI, 1.3.0 for NITE and I stayed in 1.0.9 for
> > AS3OpenNI.
>
> > I've identified the C++ code part which initialize rhe RBG part and
> > probably which causes the crash of the application.
> > I can try to comment this part and recompile the server but I'm not sure of
> > the result...
> > Which version of AS3OpenNI do you use ?
>
> > Homer
>

> > 2011/8/26 Farshid Tavakoly <farsh...@gmail.com>

>
> >> Hello Homer,
> >> Apologize that I am not so clear at times but what I meant was that I have
> >> tested all the samples files that came with when you installed OpenNi for
> >> the developer but still I get problems running the server.
> >> However, I have the latest OpenNi and Prime's drivers that can cause
> >> problems. I followed the topic and you are right that you should probably
> >> take away some of the xml where there are RGB, and I also think we should
> >> take away what you have for the resolution of the camera.
> >> As soon as we get a new update server on the PC side maybe I can get this
> >> to work.
> >> Have you openNi version as it is required to run this server or does it
> >> work for you with the latest update from OpenNi ?
> >> Is that possible you can provide me this files that I can try it?
>
> >> Im Flash developer and it should be nice to get some sample working only
> >> with Flash and not with Flex.
> >> My skills in C and C++ is very bad so if someone can even recompile the
> >> server it would be great.
> >> Many thanks.
>

> >> On Fri, Aug 26, 2011 at 10:17 AM, Homer Simpson <homer.co...@gmail.com>wrote:
>
> >>> Hey Frashid,
>
> >>> I don't understand, in the Asus Xtion Pro page specification, I don't see
> >>> there is a RGB camera, only depth sensor.
> >>> Is that true ? You say your camera works well, do you mean like any
> >>> webcam ?
>
> >>> I don't know this product very well, but I read several wiki/pages which
> >>> indicate no RGB camera...
> >>> Maybe I'm wrong.
>
> >>> I advise you to read the openni documentation, specifically
> >>> the Sensor-Related Production Nodes part.
> >>>http://www.openni.org/documentation
>
> >>> I think your problem occurs while trying to initialize Image production
> >>> node which doesn't exist...
>
> >>> Homer.
>

> >>> 2011/8/26 Farshid Tavakoly <farsh...@gmail.com>

>
> >>>> Hey Guys,
> >>>> I have the same problem with my camera also "Asus Xtion Pro" it would
> >>>> be nice to get this camera also works with this server. The camera works
> >>>> very well and is stable and you can mount it anywhere.
> >>>> Would appreciate that together we could come up with the solution and
> >>>> perhaps in the future have the solution in the XML where you can
> >>>> choose which camera you want to use.
> >>>> Many thanks
> >>>> Farshid
>

> >>>> On Thu, Aug 25, 2011 at 6:47 PM, FernandoFr <fernandodefra...@gmail.com

> ...
>
> read more »

[Homer Simpson]

Hey it's your lucky day :)

I spent a few minutes to recompile the server without handling the RGB camera.

I've not tested because I haven't the device but the binary seems to run correctly.

Can you try this and give me a feedback ?

(For security reasons, I removed the extension of the attached file. Just open it with WinRar or other soft you like, you will find the binary inside.)

Homer

2011/8/26 Homer <homer...@gmail.com>

[Farshid Tavakoly]

Great thanks Homer you are the man :-),

I will try it later tonight when I at home.

Mant thanks and best regards!!

[Homer Simpson]

I hope this will work...

2011/8/26 Farshid Tavakoly <fars...@gmail.com>

[Homer Simpson]

Hey Fernando, can you test with your config, too ?

Thx.

Homer.

2011/8/26 Homer Simpson <homer...@gmail.com>

[FernandoFr]

Testing right now!

On Aug 26, 9:04 am, Homer Simpson <homer.co...@gmail.com> wrote:
> Hey Fernando, can you test with your config, too ?
> Thx.
>
> Homer.
>

> 2011/8/26 Homer Simpson <homer.co...@gmail.com>

>
>
>
>
>
>
>
> > I hope this will work...
>

> > 2011/8/26 Farshid Tavakoly <farsh...@gmail.com>

>
> >> Great thanks Homer you are the man :-),
> >> I will try it later tonight when I at home.
> >> Mant thanks and best regards!!
>

> >> On Fri, Aug 26, 2011 at 1:44 PM, Homer Simpson <homer.co...@gmail.com>wrote:
>
> >>> Hey it's your lucky day :)
> >>> I spent a few minutes to recompile the server without handling the RGB
> >>> camera.
> >>> I've not tested because I haven't the device but the binary seems to run
> >>> correctly.
>
> >>> Can you try this and give me a feedback ?
> >>> (For security reasons, I removed the extension of the attached file. Just
> >>> open it with WinRar or other soft you like, you will find the binary
> >>> inside.)
>
> >>> Homer
>

> >>> 2011/8/26 Homer <homer.co...@gmail.com>

> ...
>
> read more »

[FernandoFr]

Homer, you're THE MAN!

Depth map, Hand gestures and tracking are working.

Awesome! Many thanks!!!

On Aug 26, 9:04 am, Homer Simpson <homer.co...@gmail.com> wrote:
> Hey Fernando, can you test with your config, too ?
> Thx.
>
> Homer.
>

> 2011/8/26 Homer Simpson <homer.co...@gmail.com>

>
>
>
>
>
>
>
> > I hope this will work...
>

> > 2011/8/26 Farshid Tavakoly <farsh...@gmail.com>

>
> >> Great thanks Homer you are the man :-),
> >> I will try it later tonight when I at home.
> >> Mant thanks and best regards!!
>

> >> On Fri, Aug 26, 2011 at 1:44 PM, Homer Simpson <homer.co...@gmail.com>wrote:
>
> >>> Hey it's your lucky day :)
> >>> I spent a few minutes to recompile the server without handling the RGB
> >>> camera.
> >>> I've not tested because I haven't the device but the binary seems to run
> >>> correctly.
>
> >>> Can you try this and give me a feedback ?
> >>> (For security reasons, I removed the extension of the attached file. Just
> >>> open it with WinRar or other soft you like, you will find the binary
> >>> inside.)
>
> >>> Homer
>

> >>> 2011/8/26 Homer <homer.co...@gmail.com>

> ...
>
> read more »

[FernandoFr]

One difference I've noticed is an increase in the initialization time,
before being able to receive events.

My previous reference is version 1.0.0.

Now it takes about 7 seconds to receive events and depth camera info.

I'm getting the folowing output:
640
480
Info (AS3OpenNI :: Alpha 1.3.0)
AS3OpenNI :: NITE Session Socket - Bound to: 127.0.0.1:9501
AS3OpenNI :: NITE Point Socket - Bound to: 127.0.0.1:9500
AS3OpenNI :: NITE Session Socket - Connection from: 127.0.0.1:52335
AS3OpenNI :: NITE Point Socket - Connection from: 127.0.0.1:52336
Setting resolution to VGA
< big delay here >
AS3OpenNI :: Capture Socket Connected
AS3OpenNI :: Server Connected
Session Progress
Session Started
Setting resolution to QQVGA

Other issue I've noticed was a slowdown with depth output, and in one
case a crash.
I'll try to replicate the scenario to tell what caused the issue.

Thanks!
Fernando

On Aug 26, 8:44 am, Homer Simpson <homer.co...@gmail.com> wrote:
> Hey it's your lucky day :)
> I spent a few minutes to recompile the server without handling the RGB
> camera.
> I've not tested because I haven't the device but the binary seems to run
> correctly.
>
> Can you try this and give me a feedback ?
> (For security reasons, I removed the extension of the attached file. Just
> open it with WinRar or other soft you like, you will find the binary
> inside.)
>
> Homer
>

> 2011/8/26 Homer <homer.co...@gmail.com>

> ...
>
> read more »
>
>  AS3OpenNI_XtionCompatibility_1.3.0
> 31KViewDownload

[FernandoFr]

Here is my report ;)

There's some delay initializing the sensor, about 7 seconds.

This is the output of NITesting:

640
480
Info (AS3OpenNI :: Alpha 1.3.0)
AS3OpenNI :: NITE Session Socket - Bound to: 127.0.0.1:9501
AS3OpenNI :: NITE Point Socket - Bound to: 127.0.0.1:9500

AS3OpenNI :: NITE Session Socket - Connection from: 127.0.0.1:52344
AS3OpenNI :: NITE Point Socket - Connection from: 127.0.0.1:52345
Setting resolution to VGA
< ### big delay here ### >

AS3OpenNI :: Capture Socket Connected
AS3OpenNI :: Server Connected

In one specific situation AIR crashed and in other occasion there was
some kind of slowdown in Depth output.

The most important aspects are working as intended, which is
excellent.

Thanks!

> ...
>
> read more »

[Homer Simpson]

Yes !

A blind-coded app which works the first time, that's so cool ;)

For the slowdown issue, which depth quality value did you set ? (I mean the AS3OpenNI switch you pass in the arguments)

Setting a too high value can cause this but I'm not sure.

Glad to help you, guys.

Homer.

2011/8/26 FernandoFr <fernando...@gmail.com>

[FernandoFr]

Sure shot.

I dont see any depth quality parameter. Where whould I set this?

This is my AS3OpenNI initialization, almost identical to the original
examples.

this._as3OpenNI = new AS3OpenNI();
this._as3OpenNI.binaryPath = "Bin/
AS3OpenNI_XtionCompatibility_1.3.0.exe";

this._as3OpenNI.singlePoint = true;
this._as3OpenNI.gestures = true;
this._as3OpenNI.circle = false;
this._as3OpenNI.slider = false;
this._as3OpenNI.trackPad = false;
this._as3OpenNI.userTracking = true;
this._as3OpenNI.convertRealWorldToProjective = false;

this._as3OpenNI.mirrorModeOff = false;
this._as3OpenNI.depthMap = true;
this._as3OpenNI.depthMapBackground = true;
this._as3OpenNI.depthMapSnapOff = false;
this._as3OpenNI.video = false;
this._as3OpenNI.init();

There's other way to set parameters? I'm using the compiled swc.

On Aug 26, 4:40 pm, Homer Simpson <homer.co...@gmail.com> wrote:
> Yes !
> A blind-coded app which works the first time, that's so cool ;)
>
> For the slowdown issue, which depth quality value did you set ? (I mean the
> AS3OpenNI switch you pass in the arguments)
> Setting a too high value can cause this but I'm not sure.
>
> Glad to help you, guys.
>
> Homer.
>

> 2011/8/26 FernandoFr <fernandodefra...@gmail.com>

> ...
>
> read more »

[Homer]

I advise you to import the library project too, to have the sources
under your workspace.
If you look in the AS3OpenNI.as file, you will see vars about
DEPTH_MAP quality

Default is AVERAGE (=1).
In your MXML, you can try the 0 value (identified by the constant
JPEG_QUALITYBAD)

like that :

this._as3OpenNI.depthMapQuality = AS3OpenNI.JPEG_QUALITYBAD;

Homer.

> ...
>
> plus de détails »

[FernandoFr]

Nice, more control.

> ...
>
> read more »

[Farshid Tavakoly]

Hi Homer,

I appreciated your help and thanks a lot. Can you please send me the code that you changed and describe where you uncomment the code?

Many thanks and best regards

[Homer Simpson]

I give you the 3 files I've modified.

Look the differences with Windiff or other comparison file tool, I just removed all reference to RGB vars & initialization. No really hard stuffs ;)

It seems to work but a best choice would be to handle both Kinect and no-RGB devices. 

For example, displaying a warning message when no RGB node without making the application crash, or something like that.

I you want still more explanation about these modifications I'll do them !

Homer.

By the way, the only man of the situation is AMB which provide us a so great framework !

2011/8/27 Farshid Tavakoly <fars...@gmail.com>

[Farshid Tavakoly]

Thanks a lot!!! Yes I agree that we need to do a real solution for that!!

Many thanks and best regards 

[Homer Simpson]

yep.

good luck for your devs and don't hesitate to share your creations ;)

Homer

2011/8/28 Farshid Tavakoly <fars...@gmail.com>

[Farshid Tavakoly]

Yes no problem :-)

[Farshid Tavakoly]

One last questions,

No I try to recompile the code and I get  following error without your changes you did with following. ver 1.3.0

Error 69 error C2664: 'XnVSteadyDetector::RegisterSteady' : cannot convert parameter 2 from 'void (__stdcall *)(XnFloat,void *)' to 'XnVSteadyDetector::SteadyCB' C:\Program Files (x86)\PrimeSense\NITE\Samples\AS3OpenNi\main.cpp 1178 1 AS3OpenNI

70 IntelliSense: argument of type "void (__stdcall *)(XnFloat fVelocity, void *cxt)" is incompatible with parameter of type "XnVSteadyDetector::SteadyCB" c:\program files (x86)\primesense\nite\samples\as3openni\main.cpp 1178 41 AS3OpenNI

Do you know why?

[Farshid Tavakoly]

I solved this when I change this method parameter to

void XN_CALLBACK_TYPE Steady_OnSteady(XnUInt32 nId, XnFloat fVelocity, void* cxt)

instead of

void XN_CALLBACK_TYPE Steady_OnSteady(XnFloat fVelocity, void* cxt)

Now the server works and the camera is on so I have to see if I can fixed the rest :-)

Many thanks Homer for your support!!

[FernandoFr]

Hey, Farshid.

Are experiencing random crashes with your test environment?

On Aug 28, 3:12 pm, Farshid Tavakoly <farsh...@gmail.com> wrote:
> I solved this when I change this method parameter to
> void XN_CALLBACK_TYPE Steady_OnSteady(XnUInt32 nId, XnFloat fVelocity, void*
> cxt)
>
> instead of
> void XN_CALLBACK_TYPE Steady_OnSteady(XnFloat fVelocity, void* cxt)
>
> Now the server works and the camera is on so I have to see if I can fixed
> the rest :-)
> Many thanks Homer for your support!!
>

> On Sun, Aug 28, 2011 at 5:10 PM, Farshid Tavakoly <farsh...@gmail.com>wrote:
>
>
>
>
>
>
>
> > One last questions,
> > No I try to recompile the code and I get  following error without your
> > changes you did with following. ver 1.3.0
>
> > Error 69 error C2664: 'XnVSteadyDetector::RegisterSteady' : cannot convert
> > parameter 2 from 'void (__stdcall *)(XnFloat,void *)' to
> > 'XnVSteadyDetector::SteadyCB' C:\Program Files
> > (x86)\PrimeSense\NITE\Samples\AS3OpenNi\main.cpp 1178 1 AS3OpenNI
> >  70 IntelliSense: argument of type "void (__stdcall *)(XnFloat fVelocity,
> > void *cxt)" is incompatible with parameter of type
> > "XnVSteadyDetector::SteadyCB" c:\program files
> > (x86)\primesense\nite\samples\as3openni\main.cpp 1178 41 AS3OpenNI
>
> > Do you know why?
>

> > On Sun, Aug 28, 2011 at 4:47 PM, Farshid Tavakoly <farsh...@gmail.com>wrote:
>
> >> Yes no problem :-)
>

> >> On Sun, Aug 28, 2011 at 4:43 PM, Homer Simpson <homer.co...@gmail.com>wrote:
>
> >>> yep.
> >>> good luck for your devs and don't hesitate to share your creations ;)
>
> >>> Homer
>

> >>> 2011/8/28 Farshid Tavakoly <farsh...@gmail.com>

>
> >>>> Thanks a lot!!! Yes I agree that we need to do a real solution for
> >>>> that!!
>
> >>>> Many thanks and best regards
>

> >>>> On Sat, Aug 27, 2011 at 9:38 PM, Homer Simpson <homer.co...@gmail.com>wrote:
>
> >>>>> I give you the 3 files I've modified.
> >>>>> Look the differences with Windiff or other comparison file tool, I just
> >>>>> removed all reference to RGB vars & initialization. No really hard stuffs ;)
> >>>>> It seems to work but a best choice would be to handle both Kinect and
> >>>>> no-RGB devices.
> >>>>> For example, displaying a warning message when no RGB node without
> >>>>> making the application crash, or something like that.
>
> >>>>> I you want still more explanation about these modifications I'll do
> >>>>> them !
>
> >>>>> Homer.
>
> >>>>> By the way, the only man of the situation is AMB which provide us a so
> >>>>> great framework !
>

> >>>>> 2011/8/27 Farshid Tavakoly <farsh...@gmail.com>

>
> >>>>>> Hi Homer,
> >>>>>> I appreciated your help and thanks a lot. Can you please send me the
> >>>>>> code that you changed and describe where you uncomment the code?
> >>>>>> Many thanks and best regards
>

> >>>>>> On Fri, Aug 26, 2011 at 1:44 PM, Homer Simpson <homer.co...@gmail.com

> >>>>>> > wrote:
>
> >>>>>>> Hey it's your lucky day :)
> >>>>>>> I spent a few minutes to recompile the server without handling the
> >>>>>>> RGB camera.
> >>>>>>> I've not tested because I haven't the device but the binary seems to
> >>>>>>> run correctly.
>
> >>>>>>> Can you try this and give me a feedback ?
> >>>>>>> (For security reasons, I removed the extension of the attached file.
> >>>>>>> Just open it with WinRar or other soft you like, you will find the binary
> >>>>>>> inside.)
>
> >>>>>>> Homer
>

> >>>>>>> 2011/8/26 Homer <homer.co...@gmail.com>

> ...
>
> read more »

[Farshid Tavakoly]

Hey Fernando!
I had the same problem as you and I also notice that there is very low FPS with the sample we had. I work a lot and did a lot of different solutions and finally I came up with a solution but it still needs to improve. The server works much better than before and Ihave also updated the server with the latest updates "Nite", so I attach the new serverto you.
Before you run it, uninstall the old OpenNi and Nite and sensor and update the "stable version" from OpenNi and you will notice the difference.

[Farshid Tavakoly]

Hi Fernando,

How it works for you withe the new server, is that better or you have same issue?

On Tue, Aug 30, 2011 at 4:58 PM, FernandoFr <fernando...@gmail.com> wrote:

[FernandoFr]

Sorry, I didn't notice your responses.

I'm gonna try it today ASAP.

Thanks, Farshid!

On Sep 1, 7:58 am, Farshid Tavakoly <farsh...@gmail.com> wrote:
> Hi Fernando,
> How it works for you withe the new server, is that better or you have same
> issue?
>

> ...
>
> read more »

[FernandoFr]

Hi, Farshid!

I've re-installed all software, using newer versions.
FPS performance is good, movements are very precise and no crashes.
It seems to be the best version yet.

Thanks, man!

On Sep 1, 7:58 am, Farshid Tavakoly <farsh...@gmail.com> wrote:
> Hi Fernando,
> How it works for you withe the new server, is that better or you have same
> issue?
>

> ...
>
> read more »

[Farshid Tavakoly]

It sounds great!

Sent from my iPhone