Raspberry Pi 2 with Raspbian is laggy - performance

I am having some issues with my RPi2. As I said in the title I have Raspbian installed. The system runs smoothly when I navigate files etc. But when I try to use the Internet Browser OR Navit (I am working on a project and I want to use the RPi as a navigator) then the system gets laggy and very very slow. I also notice that in the right top corner the cpu usage goes about 30% (sometimes more).
Raspbian is installed in a 16Gb Class 10 SD Card. I have expand the system via raspi-config and I have about 9 gigabytes of free space. I also have HDMI, keyboard and a wireless mouse connected.
Any ideas/suggestions?
Thanks in advance!

Related

Realsense Viewer / SDK does not open

I bought a Intel NUC Hades Canyon VR NUC8i7HVK PC and added an 8gb Kingston ValueRAM and 120GB Kingston UV500 SSD, running Windows 10, together with an Intel Realsense Depth Camera
I have tried to install the Realsense SDK, Realsense Viewer and Realsense Depth Quality tool aren't working.
They literally don't open without any error messages.
I have reinstalled it numerous times.
I'm intending to use it with the Nuitrack library and Unity for Skeleton tracking and have successfully done so with my regular computer.
However, now nothing seems to work anymore.
I have no idea how to go about it, since I don't know where to look. Any ideas?

OSX Yosemite + Crossover (Wine) = Sporadic MIDI Sync

The setup:
OSX Yosemite.
Ableton Live 9 (Suite).
Crossover/Wine (14.0.3).
Connected device is a Novation Launchpad Mini (USB).
The problem:
The install of Ableton and most of its use work well. I have compiled and successfully installed wineasio.dll (wineasio.dll.so) to obtain low latency audio, again this works extremely well.
But what I am finding is the communication between the LP and Live is somewhat sporadic. examples of this are, having to list the LP in the midi in/out section of live multiple times just to get it to behave correctly (mostly), pads/lights randomly lighting/becoming non responsive, active tracks not showing (lighting up)
There is no pattern in all this. bug what i can say this setup works without problems in windows and OSX (obviously)
before you ask I'm having to use WINE as one of my favourite VST's is only windows based.
if someone can recommend a VM based solution (with low latency audio/ Midi) i will welcome it.

How to use DirectX 9 with multi- GPU on windows7

I‘ve got multiple nVidia GPU Cards (Q2000) on a Windows 7 system,without SLI, only one monitor.
Now what I'm trying to do is make a Direct3D9 device runing on a specific GPU.
I can use the [Adapter] parameter in IDirect3D9::CreateDevice to choose a GPU, but unless I connect a second monitor on that GPU card, it will not work (if I've only got one desktop on Windows).
If I click the "Detect" button in Resolution Control Panel, it can make a "fake" desktop on the side of my primary desktop, and CreateDevice(1, ...) works well - but this is not what I want.
For OpenGL, it's easy because the WGL_NV_gpu_affinity, It can make a OpenGL device runs on the second GPU with only one monitor connected, one desktop on windows.
I wonder if there is any API can use for Directx 9 work as "WGL_NV_gpu_affinity".
Any hint will be very appreciated. Thanks in advance!
IDirect3D9::CreateDevice uses at 1st parametr "Adapter", which not GPU, just monitor adapter

Kinect for Windows - PC Incompatibility

I'm working for an University of Applied Sciences and we want to buy some Kinects together with some PCs for future research as well as student projects and we are currently in a stage where we want to define which hardware to use.
We have a Kinect for Windows sensor and we are testing it with a Dell PC (Inspiron 15r 7520; Windows7 64bit, Intel i5-3210M #2.5GHz; 6GB RAM; USB 3.0).
We installed all the drivers for the 1.6 Version of the Kinect SDK but the PC only detects the Kinect camera once in a while.
In the device manger the "Kinect for windows Audio Array Control" and the "Kinect for Windows Security Control" show up but the "Kinect for Windows" Camera only shows up once in a while. If we plug and unplug the Kinect 10 (or 20 or 30 or 5) times the Camera is not detected 9 times. Then suddenly the camera is detected once and we are able to use it.
The next time we have to plug and unplug the camera 20 or 30 (or 2 or 5 or 10) times until the Camera is detected again. Then, we can plug and unplug the Camera 5 or 6 times and it is detected every single time.
Every time the camera is not detected a Windows USB Information (yellow triangle) pops up stating that a USB device was not detected.
We are quite sure that the Kinect sensor is not the problem because it works on 5 other PC without any problems. Then we thought about an USB Controller problem but after replacing the Mainboard and the USB Controller of the PC the error persists.
Are there any known PC - Kinect incompatibilities or can anybody think of a reason for this strange behavior?
Any help is greatly appreciated.
I'm not sure whether this includes recognising the camera, but there are known issues with certain USB host controllers and version 1.6. If you haven't already, take a look at this MSDN page under the "USB host controller compatibility" subheading.
It does mention two USB 3.0 controllers which are known to have issues. If you are using either the "Etron USB 3.0 Extensible Host Controller" or the "Renesas Electronics USB 3.0 Controller" you might have your answer.

QEMU: Slow video performance with Windows 7 guest

I'm running a Windows 7 guest virtualised under QEMU/virt-manager on a Fedora 17 host and video performance seems poor. Mouse movement is laggy and unresponsive.
The guest is using a qxl video adapter and a Spice display. The guest Windows 7 has the latest spice tools installed. Changing spice to VLC in virt-manager doesn't improve things, neither does switching to a different display adapter (vga/cirrus). I've tried upping video memory, also didn't help.
I'm guessing this is video related as connecting to the Windows box directly via RDP is much more responsive.
Any ideas?
I try run qemu with win7 trough:
1. sdl -> fbdev
2. sdl -> nouveaufb(not work for me)
3. sdl -> directfb(not work for me)
4. sdl -> ggi(mouse not work) -> fbdev(or nouveaufb)
5. sdl(with USE="opengl") -> xorg(with nouveau opengl).
It all works same) video is smoothing, no luck)

Resources