Im' trying to make an app with processing using kinect, and SimpleOpenNi. I tried to follow this tutorial http://www.creativeapplications.net/processing/kinect-physics-tutorial-for-processing/ , but i'm stuck at the very beginning : when i launch the first script processing returns me this error :
"The function enableScene() does not exist"
Also, the function sceneImage() doen't work.
I installed KinectSDK, OpenNi, NiTe, SimpleOpenNi lib, tried on 3 differents versions of processing (1.5.1, 2.0.1 x86, 2.0.2 x64) with win7&win8. I really can't find any solution on the web, if someone have some any clue, i'd be glad !
Thanks !
Change enableScene() to isInit() and replace draw() with
void draw() {
// update the SimpleOpenNI object
context.update();
image(context.rgbImage(), 0, 0);
}
What version of SimpleOpenNI are you using? The most recent addition to my knowledge lacks the enableScene() method. Use the wayback machine and download an earlier version.
Related
Trying to resuscitate an older project after the recent AKSampler updates. As per docs it would seem that the original AKSampler functionality would now reside in the new AKAppleSampler. Yet when I am trying any of the methods for loading soundfonts, I get an unfortunate "AudioKit.AKAppleSampler loadMelodicSoundFont:preset:error:]: unrecognized selector sent" before the try clause even catches.
let midiSampler = AKAppleSampler()
do {
try midiSampler.loadMelodicSoundFont("GeneralMidi", preset: i)
} catch { print("!! initSamplerBank failed with error: \(error)") }
Tried new projects with AudioKit 4.2, 4.2.3 and the current develop branch and am not really sure what I might be overlooking here. Any help appreciated.
Solved. Seems the project even though syntax highlighting all methods correctly was somehow still referencing an older AudioKit version's framework. After cleaning, emptying DerivedData and installing AK via Cocoapods as opposed to direct framework link the AppleMIDISampler now loads soundfonts as expected.
How do I upload firmware (microsemi) via the Spi port?
How do I then start, stop and check the status of said firmware?
Android Things Version: 0.4.1-devpreview (could not get the display to work on the newer builds)
Issue: I am a hardware noob. I have a python driver used for uploading firmware and a config file via the Spi port. My goal is to port this to Android Things leveraging the SpiDevice class.
The python version of the driver strips off headers and checks block size ect. I'm not sure if I need to do this with Android Things SpiDevice.Write(buffer, length) method.
Once I have uploaded the firmware and config, I will need to start it. In total I will need to upload firmware, start firmware, check if firmware is running and stop firmware.
I have started writing a SpiDeviceManager, and have naively began to flesh out the methods. (see below).
*public void LoadFirmware()
{
WriteFile(_firmwareFilePath);
WriteFile(_configurationFilePath);
}
private void WriteFile(string filename)
{
using (System.IO.Stream stream = _assetManager.Open(filename))
{
byte[] buffer = new byte[2048];
int bytesRead;
while ((bytesRead = stream.Read(buffer, 0, buffer.Length)) > 0)
{
_spiDevice.Write(buffer, bytesRead);
}
}
}*
If anyone can point me at some docs or examples I would really appreciate it.
Also, if anyone has any advice about getting the display drivers working for the latest version of Things I could really use your help. I have the device specs for the config.txt it just does not work.
Thanks,
Andrew
The SpiDevice just sends the data along.
Its up to me to pack the bytes in there in such a way that the chip can make sense of it.
I am sifting through the data sheet to that end.
#Nick Felker, thanks for the info about the Android Things display. Cant wait for the next release to drop.
After about 3 hours I found out that in universal Windows Phone 8.1 apps the AuthenticateAsync-method has been deprecated.
When using it in Visual studio, at first, it is silent. When you try to run it, it says:
AuthenticateAsync is unavailable for releases beginning with Windows
Phone 8.1. Instead, use AuthenticateAndContinue or
AuthenticateSilentlyAsync.
After another 2 hours, how hard I try, I cannot find a way to implement the example of the Single-sign on, it simply doesn't work.
AuthenticateAndContinue fails because the "remote procedure call failed"
SilentlyAsync returns the error, that the parameters are incorrect, but that is logical.
Do any of you guys know of a way to sign in, without using AuthenticateAsync?
Edit: When running anyway, it throws a not implemented Exception
I assumed "deprecated: was just a compiler warning saying "we suggest you shouldn't use this API anymore".
I was wrong - it's apparently a hard error with the OP's Windows Phone SDK. The new SDK doesn't support the old call; I doubt the Facebook SDK supports the new call.
SUGGESTED WORKAROUNDS:
1) Try using an older Windows Phone SDK (or, if possible, target your compile for an older version of the runtime).
2) Wrap your call in Dispatcher.RunAsync
WebAuthenticationBroken.AuthenticateAsync - NotImplementException
http://www.asp.net/web-api/overview/web-api-clients/calling-a-web-api-from-a-net-client
I'm trying to follow the basic cometd example here: http://dojotoolkit.org/reference-guide/1.7/dojox/cometd.html
It's using the old module loader so I tried the equivalent as follows:
require(["dojo/ready","dojo/io/script","dojox/cometd","dojox/cometd/callbackPollTransport"], function(ready, dontcare, cometd) {
ready(function(){
cometd.init('http://localhost:8080/MyCometD/cometd');
comted.subscribe("/test", function(msg){
console.debug(msg);
});
});
});
This doesn't work and I think it has to do with loading modules - there is some sort of silent error as the code within the ready function does not execute at all. What I found is that when the "dojox/cometd" require statement is present, the code within the ready function does not execute.
Running example: http://jsfiddle.net/Q9W8f/2/
Example with dojox/comted removed: http://jsfiddle.net/mMs2h/4/
I haven't worked with the new module loader that much so I bet I just have some simple misconception.
Help!
It seems like youre correct and that there is a 'wait-loop' for a module requirement that never gets loaded. This may be any of the requirements inside dojox.cometd and you'd need to rewrite the codebase for a fix.
I have had similar issue with the RollingListPane, also in dojox repository - and the developers are saying 'we are 100% AMD compliant with 1.7' however the X in dojox is short for experimental. The developement of dojox modules is not done by the core djtk team and there are still glitches..
Try for starters to avoid using CDN which has performed a >>built macro on every single module. This tends to fail at times whilst using AMD. Instead download the tarball and use a local copy - Not compressed (dojo-release-1.7.2-src)
You can find the hello world example in cometD and ExtJs at following link:
http://jksnu.blogspot.in/2013/08/network-reliability-by-cometd-hellow_16.html
Would anyone have an idea as to why an app would work on almost every phone that has 2.1 but not the Desire?
One of my apps uses voice input and the Desire is the only phone that force closes when the voice prompt comes up.
The worst part is that I don't know how to test this, I don't have one or know anyone who does.
Any ideas?
EDIT:
I finally found out that HTC disabled voice in the Desire and you have to do a work around to install it.
So if you are relying on voice input make sure you use the code in the google example to catch the error:
PackageManager pm = getPackageManager();
List<ResolveInfo> activities = pm.queryIntentActivities(
new Intent(RecognizerIntent.ACTION_RECOGNIZE_SPEECH), 0);
if (activities.size() == 0) {
noResults.setText("Voice input not found on this phone.");
}else{
//If voice is enabled
}
I think the most important thing to do first is to get the exception report. Since you can't test it by yourself, I would use a tool to get the exception report from your customers. In Android 2.2 the built-in tool can be used. If you have other targeting SDKs I would recommend this services: http://code.google.com/p/android-remote-stacktrace/ to get a remote stacktrace.
Then if you post the stacktrace here, I think somebody will be able to help you!