I'm building a Kinect application in Unity (C#) that tracks multiple people. My stumbling block is how to test this without having several live 'actors' in front of the sensor.
I know Kinect Studio allows you to record live streams, but don't think this can be played back so that it feeds a Unity app. I am using the Kinect for Windows Unity package as a starting point.
https://dev.windows.com/en-us/kinect/tools
Any Kinect or Unity experts care to chime in?
Actually you can use recorded data to playback them without any "actors".
While you are running your app (and without the need of an actual Kinect device plugged in your PC), open Kinect Studio and chose Open (Read-Only) from File. Click then on the Connect icon under the Play tab:
After that, using the Play icon (the typical triangular-shaped one), your recordings will be send to the KinectService, so you can test your app without any actors.
Related
On the Instant Play Games site google recommends the following:
Integrate sign-in using Google Play Games Services and a cloud save
solution to preserve progress in the game.
However in this other document the following is stated:
If the player is using a device that runs Android 8.0 (API level 26)
or higher, and if your game specifies a targetSandboxVersion of 2,
then the player's progress is transferred automatically to the full
version of your game. Otherwise, you must transfer the data related to
player progress manually. To do so, use one of the following APIs...
So it seems that cloud saves are not needed, there exists a simple API for transferring progress to the main app. So why is cloud save recommended? Am I missing some aspect or restriction of instant apps?
I found at least one reason for this, which seems critical enough:
The instant app data does not persist over for example restarting the device. More info here.
Helloo all
I'm currently developing an app for surface pro 3 that should be capable of:
detecting whether touchscreen was tapped and where
getting device information (product ID, amount of RAM, CPu model etc.) done by launching console application first which is capable of getting this information and saves it to a specific folder, UWP app can read its results from there and log them.
accessing sensor data like: accelerometer, gyroscope and ambient light sensor
testing cameras as i can command an app to make picture using either front or rear camera
testing microphones (both front and back)
testing speakers (i made synthesizer that is able to make beeps at given frequency at given stereo mode (left or right if both)
testing wifi - so it can connect to desired wifi network
bluetooth (swill working on it...)
I have already figured out quite a lot and put out a lot of work into it already, all listed tests are already developed on that UWP application so switching to completely different platform means rewriting whole app which I don't have time anymore.
UWP was chosen because this can run on different windows 10 devices and after completing this app the same app (with minor modifications) will be used on other windows 10 devices (like other surfaces and many different windows 10 phones)
This app will be automatically installed on a factory-resetted surface pro 3 that has no special configurations enabled, so tinkering with its settings is resource-hungry and not recommended process at all.
Now I have some other serious issues regarding of device:
how can I test the functionality of all the buttons Surface pro 3 has ?
It has 3 buttons: Volume up, Volume down and power button
but pressing power button sets screen to clack and locks device.
Can I make app override basic functionality of a button so that if button is pressed it detects it and logs its result.
same question goes to volume up and down buttons.
Only similiar questions about this are here:
Another thread on StackOverflow
I also cannot use same solution as I did with getting device information because test must be repetitive while app is running. (and UWP app cannot launch console application by itself)
Any help regarding this topic is highly welcome.
First for the power button behavior try this :
https://www.windowscentral.com/how-customize-power-button-action-when-pressed-windows-10
I don't have a surface so I cannot test it
also, I do have some inputs and thoughts about your app:
it seems to me that you are doing some sort of sanity check software for pieces of hardware I'd suggest looking into this
https://support.microsoft.com/en-my/help/4037239/surface-fix-common-surface-problems-using-surface-diagnostic-toolkit
https://www.lovemysurface.net/surface-diagnostic-toolkit/
additional thoughts of mine :
Overriding hardware behavior programmatically ould be considered as a harmful action especially when it comes to prebuilt devices such as the surface and by extension, I don't foresee MS providing API's for such a capability also such button might be communicating to the hardware directly rather and doesn't go through the software, runtime or the OS at all, changing it manually using the link i provided might be reflecting some registry settings changes but since UWP apps run in containers and cannot directly edit registry there is a dirty workaround look into this
read/write registery key file in uwp
hope this would help
You can use SystemInformation helper class from windows community toolkit it gives you a lot of details about the device.
https://learn.microsoft.com/en-us/windows/communitytoolkit/helpers/systeminformation
I've been trying to run simple scripts on my Intel Edison to try the different Grove Seeed Studio sensors and cannot manage to make them work.
My board is configured correctly, its firmware is up to date, and all cables have been connected correctly as shown on different tutorials. I can connect to the board through the IDE, via SSH, and with serial.
I've been using mainly the templates provided by the Intel-XDK IDE because I'd like to develop using javascript and nodejs. The "Onboard LED Blink" template has worked perfectly. My board successfully blinked the onboard LED light so the board is clearly listening to my machine, but all the other templates have failed to make my sensors work. For example, running the "Local Temperature" template which aims to just retrieve the local temperature with the temperature sensor, just prints Sample Reading Grove Kit Temperature Sensor and stays there without printing any temperatures in the console. This has been the case for other sensors and other templates like the "Touch Notifier" template which when running also just prints Sample Reading Touch Sensor and performs no other actions when touching the touch sensor.
I tried moving away from the Intel XDK templates and trying some of Johnny-Five templates like this one and still no success. After running that particular script the console just printed Looking for connected device. I found a related post here but nobody was able to solve the issue.
It almost seems as if I am not being able to properly connect to the sensors. I get no errors on the console, just not the desired outcome. What am I doing wrong? How can I even debug this?
The samples in the XDK are at first glance a bit deceiving. The "Local Temperature" and "Touch Notifier" are designed to work with HTML5 companion apps on a phone for example (you can see this by reading the template description when you select it). Hench when you see the xdk printing the message out, it is first listening for a connection to the HTML5 app which is where it will send the temperature for display. There is an article about the "Local Temperature" app that goes into further detail and how to set everything up here: https://software.intel.com/en-us/creating-a-temperature-monitoring-app-using-intel-xdk-iot-edition
And if you want code for individual sensors, I recommend using this link here to search for code by sensor (each one should have code for c++, javascript, and python code samples): https://software.intel.com/en-us/iot/hardware/sensors
I want to create application where I can record video with audio and save it to disk.
When application start I detect all video and audio sources and show this list on the UI.
But when I disconnect one of webcams (or unplug mic), this device still remain in list.
How I can get notifications of device connect/disconnect, both for video devices(USB) and audio devices(jack 3.5).
Thank you.
WBR
Maxim
You might find some useful tips in this other question, here IOKit device adding/removal notifications - only fire once?
I also have an example of an app that uses the IOKit framework to detect adding and removing USB devices on my github account here: https://github.com/tjarratt/Panic-Button
Baring that, the apple developer site has a lot of documentation on using USB devices:
https://developer.apple.com/library/mac/documentation/devicedrivers/conceptual/USBBook/USBDeviceInterfaces/USBDevInterfaces.html
I have downloaded the Metro Style Application Sample that is available on the Microsoft Web Site. There are lots of examples that shows how you can interact with the hardware device (sensors,gps,etc). I have of course downloaded the Windows 8 Developer preview to execute those examples. My question is : how can I test those samples that uses the device hardware (gps, accelerometer) or that accesses to the phone features (sms,etc) using the emulator?
At the moment there are not devices that support windows 8 (the first phone will probably come out this autumn) ?
I'd like to start to develop some metro style applications to be ready when windows 8 store will be online but using just the emulator is a big limitation isn't it?
Yes and no. There are slate devices that can run the Windows 8 Dev Preview just fine.
If you are unable to get one of these, one option is to create your own interfaces for all the devices. Underneath you can have two implementations.
First one, you connect to the actual underlying devices via the Windows 8 APIs. Sure you won't be able to test these until you have a device but such is life.
The second implementation can be a dummy one. For example, you can have a thread running and every 2-3 seconds publishing some GPS event.
That way you at least have some dummy device data coming in that you can test with for the time being.