I have a Kinect 1414 and a MacBook Pro which has mac os sierra on it. I am trying to install the necessary things to run a sample in my mac. In order to do that, I strictly followed the steps shown in here. After completing each step, when I run the Sample-PointViewer, I am getting this output:
1628 INFO New log started on 2017-02-11 00:17:31
1709 INFO OpenNI version is 1.5.7 (Build 10)-MacOSX (Nov 12 2013 13:39:54)
1715 INFO --- Filter Info --- Minimum Severity: UNKNOWN
One or more of the following nodes could not be enumerated:
I am not sure if it is an important thing but I also noticed that even if I disconnect Kinect from mac, it gives the same output.
If anyone can help me, I will be really happy.
Thanks in advance.
Related
After installing jetpack 4.4 on the DJI manifold 2G (Nvidia jetson tx2 version), the internal Ubuntu software updater pings me for a 2.3GB sized update.
Following which, after completing the update, all USB ports are non-responsive, and the processor's fan will continuously run at full speed. Restarting the device does not improve nor make things worst. The only way out seemed to be re-flashing the firmware with jetpack 4.4.
The specs are, if they are helpful:
Processor: ARMv8 Processor rev 3 (v8l) × 4
Graphics: NVIDIA Tegra X2 (nvgpu)/integrated
Os type: 64-bit
Memory: 8gb
Any help, or similar experiences and work-arounds are greatly appreciated. Thank you !
Edit
-Attempting to use the Manifold 2G image provided by DJI returned this error when executing sudo tar -zxvf
gzip: stdin: invalid compressed data--format violated
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
As such, i am unable to downgrade back to the Jetpack 3.3 version
DJI mf2G uses a specifically modified version of the jetpack with DJI-preset serial port config.
Publicly, there is one standard version on the DJI website that you can restore to factory default. https://www.dji.com/sg/manifold-2/downloads
Privately, the DJI dev group also give out a Jetpack 4.3 version DJI image that can allow you to use docker(factory default does not allow). But I can not share it publicly. You may ask DJI support to release this version to you.
I'm using an Asus Chromebook with a CPU(I think).
This is what the Error says:
Warning: Could not find a matching GPU name. Things may not behave as expected.
Detected OpenGL configuration:
Vendor: Red Hat
Renderer: virgl
/run/user/1000/gvfs/ non-existent directory
found bundled python: /home/sekhong5417/blender/2.90/python
This works on my Friend's Chromebook who has a GPU.
Also I am kinda young so I can't replace anything or buy a new device.
There are images at the bottom
If anyone still runs into this issue, there is an incompatibility with Blender and Intel ChromeOS GPU drivers.
See https://developer.blender.org/T77651#1172666 for more details and an updated working build of v2.93.
Hopefully, the fix gets included in the next release.
I use Acer Chromebook spin 13 and I just met the same issue with you. I think it is maybe the Debian within Chromebook don't have the driver that matches the Intel GPU. My Chromebook uses Intel HD graphics 620. I tried many ways to install the driver but they all failed. Linux works easier with Nvidia GPU though. So my idea is you can try to find intel a drive which matches your Graphic card and try again.
i have just downloaded Xcode 11 beta and installed in a vm environment. When trying to start a new playground or project, xcode quits with following error code. Any idea how to solve ?
Process: Xcode [426]
Path: /Applications/Xcode-beta.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 11.0 (14855.18)
Build Info: IDEFrameworks-14855018000000000~13
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Xcode [426]
User ID: 501
Date/Time: 2019-06-08 08:13:37.785 -0700
OS Version: Mac OS X 10.14.5 (18F132)
Report Version: 12
Anonymous UUID: CB32DBDA-4F6E-4212-F810-C52C80FFD0CD
Link to full error:
https://pastebin.com/fFhcadtZ
This should probably be a comment, not an answer, but I lack the reputation to do so. Here is the xcode developer who developed the minimap indicating that while the minimap indeed does require metal, xcode should not crash when metal is not available. Hopefully he implements a patch to fail gracefully in one of the next builds. As of right now, there is no workaround. The reply to the thread:
defaults write http://com.apple .dt.Xcode DVTTextShowMinimap -bool NO
does not prevent the crash, as mentioned there.
It is fixed in XCode 11 beta 2, available on developer.apple.com !!!
June 17 2019.
You don't need MacOS Catalina, only Mojave 10.14.4 and up (current is 10.14.5).
I used VMware on Windows to install Mojave and XCode beta 2.
I attempted the same with Parallels (with tools installed), and also observed a crash. I suspect the problem is with the virtualization software lacking support for Metal. Notice the stack trace on the main thread:
0 com.apple.dt.SourceEditor 0x0000000120ccb5cb specialized
static MinimapMetalLinesLayer.defaultDevice() + 491 1
com.apple.dt.SourceEditor 0x0000000120cc959c
MinimapMetalLinesLayer.init() + 284
The "Minimap" is a new feature in Xcode 11, it's a birds eye view of the source code in a column on the right (similar to Sublime text edit). Also notice the mention of Metal, Apple's graphics API. To test this theory, I opened Xcode 10 (in the same VM) and attempted to build one of Apple's examples. I got the following error, which seems to confirm my suspicion that Parallels is unable to support apps using Metal.
2019-06-09 09:15:17.875253-0400 HelloTriangle[652:7547] *** Assertion
failure in -[AAPLViewController viewDidLoad],
/Users/ZestyMeta/Downloads/UsingARenderPipelineToRenderPrimitives/Application/AAPLViewController.m:27
2019-06-09 09:15:17.875403-0400 HelloTriangle[652:7547] Failed to set
(contentViewController) user defined inspected property on (NSWindow):
Metal is not supported on this device
I haven't attempted installing macOS Catalina / Xcode 11 in VirtualBox, VMWare, et al. but unless they support Metal then this crash will happen there as well. If you're testing out Catalina (which is required for SwiftUI on macOS), unfortunately it seems the solution at this time is to install on a spare device or dual boot.
I am struggling trying to use the FCD Pro with Linux.
With the 2.2 Qthid Funcube Dongle Controller software installed, I have segmentation fault issues, the program closes by itself after a few second but the device is detected by the software.
With the 4.1 version though, I don't see the device (FCD not detected) but I do see the device in my usb tree:
Bus 002 Device 015: ID 04d8:fb56 Microchip Technology, Inc.
I have updated the firmware to ver. 18j using Windows SW and the guide suggested http://www.funcubedongle.com/MyImages/FCDFirmwareUpdateGuide.pdf
But using Linux, I just can't make it work.
Of course I copied the rules in /etc/udev/rules, but nothing changed..
I am working with
Linux xxxxx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 16.04 LTS
any help? Tks
Like you I am seeing the segmentation fault with qthid-2.2 on Debian Buster (Testing at this time) while running qthid 4.1 just shows "No FCD detected" in the status bar.
Until I added my username to the "users" group as the recommended udev rule sets, qthid-2.2 would not seg fault and did show the FCD was not detected in the main pane.
At this time I've no solution except compiling qthid 4.0 from source as version 4.1 is explicitly noted as only working with the FCD+. See:
https://sourceforge.net/projects/qthid/files/4.1/README.txt/download
I have a rather common task for my NSIS installer - to find out if Firefox is running before the install, and ask the user to close it. But I haven't yet found a plugin that works for Windows 7 x64. I have tested Processes, FindProcDll, nsProcess - they all failed to detect the 32-bit firefox. I'd be grateful for any ideas where to look next.
Update: Actually, I couldn't detect the 64-bit firefox either with any of these plugins.
FindProcDLL worked fine for me on 32 and 64bit systems.
I tried to find 32bit process and 64 bit processes and both were fine.
nsProcess works just fine for me. It also seems to be the most recently updated of the plug-ins you listed, so that's why I tested with that one. I'm using Win 7 x64 and confirmed in Task Manager that Firefox showed as "firefox.exe *32"
!include nsProcess.nsh
...
${nsProcess::FindProcess} "firefox.exe" $R0
${If} $R0 == "0"
# it's running
${EndIf}
Possible return codes:
0 Success
603 Process was not currently running
604 Unable to identify system type
605 Unsupported OS
606 Unable to load NTDLL.DLL
607 Unable to get procedure address from NTDLL.DLL
608 NtQuerySystemInformation failed
609 Unable to load KERNEL32.DLL
610 Unable to get procedure address from KERNEL32.DLL
611 CreateToolhelp32Snapshot failed