lightbuzz / vitruvius Goto Github PK

Hello, I have used Gesture Controller for WPF application.

When using it on theGestureController_GestureRecognized(object sender,GestureEventArgs e) method e.Name returns right value but e.Type is remains None always.

Can somebody please help me with that issue.

Hi
In the sample project, raises an "null" error on [GreenScreenBitmapGenerator.cs]

line 196
Marshal.Copy(Pixels, 0, Bitmap.BackBuffer, _displayPixels.Length);

for Pixels

regards

I'm looking for some library that allows me to track simple arm/hand gestures to use as UI for some visualizations. Is this project still maintained? If not, is there any other similar? I'm using Kinect v1.

I see under Kinect v2/WPF/VitruviusTest folder just a .csproj and a .xaml.cs file (not any .xaml or other files). I see the .xaml.cs contains Kinect v2 related-code (MultiFrameSourceReader is Kinect v2 only I think) so it shouldn't be just a remainder from the VitruviusTest folder of the Kinect v1 solution

I there a chance you've forgotten to push some files from that folder to the repository?

was comparing the WPF and WinRT versions of Joint selector (I know you've told me they've been merged now, but I don't see the merged version uploaded yet) and did some code cleanup there and noticed two things:

1. there are some foreach loops that seem to be useless (have marked them with comments if you merge the pull request that is pending). Most probably those should be removed or add code to them if they need indeed to do something for each selector (if they all need to do the same then move the loop in some protected method and call it from everywhere)

2. the WinRT version misses the BodyBackground property of the WPF one and I see in the winrt XAML it binds the background of the body path to the Background property of the UserControl instead (that property isn't used at all by UserControl [doesn't paint its background] as I have found out some time ago talking to some VS program manager after related feedback I had sent). Not sure what you opted for in the merged version.

I think it is cleaner to have a BodyBackground property and maybe bind the Background property of the UserControl to the Background property of your layout grid (which is now transparent).

Care should be taken though with propagation of mouse events on the background of the control (if somebody might care about them), they differ if a control has Null to when it has Transparent Background property. In such a case one might have to set a default value to the background of the UserControl in the XAML (say set it explicitly to Transparent and then bind to it from the layout grid's Background property [and have the path's background bind to BodyBackground in WinRT version too as I write above])

I downloaded version 04/26/2014. In WPF constants.cs not found.
PS - Great job making this library for others to use and learn. I'm doing a summer project with my son and his friends with 6 roombas, 6 kinects and 6 Asus T100 laptops for them to learning robotics and programming.

I believe it would be better to reuse code between WPF and WinRT versions of the Kinect v2 version of the library, using shared projects (and conditional compilation blocks) as shown near the end of this article:
http://mtaulty.com/CommunityServer/blogs/mike_taultys_blog/archive/2014/11/17/shared-projects-common-libraries-on-kinect-for-windows-v2-sdk-bits.aspx

btw, a very nice free extension for Visual Studio to compare/merge code files is Code Compare (you get intellisense etc. while editing/merging stuff)

i am already working on a project with kinect and now i want to use your library in that project. I am new to kinect so can you guide me through steps need to be done to add your library in my project.

It seems the https://www.nuget.org/packages/Vitruvius/ package has older version of the Kinect v1 library, that is it doesn't contain the WPF control

I guess the https://www.nuget.org/packages/lightbuzz-vitruvius/ version is for Kinect v2 only

is it possible to update the Kinect v1 NuGet package and also add some note at the above two URLs that says for which Kinect sensors each NuGet package is?

giving warning on using code of hand tracking from your blog and using it in other programme.
Severity Code Description Project File Line Suppression State
Warning "There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "LightBuzz.Vitruvius, Version=1.0.0.0, Culture=neutral, processorArchitecture=AMD64", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project." rahul_1

on using release this warning is coming and there are no errors in code but the colour image in not appearing in the window, it is coming blank
on using debug this warning is not coming but still no colour image is coming.
kinect sensor is not starting in either case

can I stream real time data from kinect to mobile phone through internet and control kinect from mobile using arduino??.....thnx in advance

When toggling off skeleton at Kinect v2 WPF demo (don't remember if WinRT demo does it), it leaves back the old skeleton "frozen". It would be more consistent if it removed the old skeleton when toggling it off

I added FlipHorizontally and FlipVertically to KinectViewer control at Kinect V1 solution (see outstanding pull request). You may want to copy that code to the v2 WPF and WinRT controls if they don't have such functionality

The documentation for Axis Enumeration says it "Represents an axis from the 3D space"; is this body coordinates, camera coordinates or perhaps gravity/floor aligned coordinates? I'm trying to understand what effect passing in an Axis should have on the Angle.

I think it would be better if the solutions (.sln files) were renamed to be for example
Vitruvius.WPF and Vitruvius.WinRT instead of both being called Vitruvius. For example at the Start page of Visual Studio at recently opened (or at pinned there) solutions you then see two Vitruvius entries which is a bit confusing.

also maybe the solution for Kinect v1 could be renamed to Vitruvius.Kinect1 or something like that

I'm geting this error on XAML file:

Error 2 Unknown type 'KinectViewer' in XML namespace 'clr-namespace:LightBuzz.Vitruvius.Controls;assembly=LightBuzz.Vitruvius'

Can someone tell what i'm doing wrong?

Please pull-in #12 - fixed a bug at _SizeChanged event handler of WPF KinectViewer control

Have done the fix at Kinect v1 version only since I don't have a v2 Kinect device yet to try it out. Probably the same fix is needed to v2 WPF and WinRT controls if they share similar logic

the bug was that when you resize you were setting two width value to 0 which would cause next frame to get again the Kinect frame size - but if the canvas size isn't also reset in the _SizeChanged event, then at the next frame event an if clause skips the recalculation of ratio parameter, so the skeleton is smaller / not aligned with the person.

Note that in the V1 test app have also done XAML changes to allow KinectViewer (that I've added to it) to take all empty space when resizing

have also added commented block at XAML of the v1 test app and conditional compilation checks at codebehind, so that one can switch to using a viewbox>grid>image,canvas block instead of the KinectViewer control with almost identical code. However, I noticed that the code in KinectViewer control is producing a bit better aligned results than the extensions to Canvas after resizing the application window. It might be my impression, but I've noticed they use quite different code. Haven't checked the v2 version if it has unified such code (e.g. I'd expect all that drawing code from KinectViewer control in v1 version to be in the Canvas extensions instead of being inside the WPF control's code)

When using the Test app with Kinect for Xbox 360, have noticed that at Depth mode, when I move backwards (I'm seated and Kinect is on my desk at first) the display freezes. When I move near again it unfreezes

hello guys, how are you doing today.Actually i've a problem the project you are given is not open in compile in visual studio. it gives me a error. it says add an executable project to this solution which reference the library project. Please help me how i slove this..!!!