Transfer HID & audio between Raspberry Pi and Windows over LAN?

Question

4.00/5 (2 votes)

See more:

, +

My Google-Fu only gave me results like Synergy[^], which all on is own is a neat app, but not what I'm looking for. Nor is any of the "remote desktop" applications I've looked at.

What I'm looking for:
I'm either looking for an application, or some information to get me on the right track to make an application that can do the following:
1. Transfer keyboard and mouse input from a Raspberry Pi running Linux to an app or service on a windows PC (full USB functionality for the Raspberry Pi's 2 ports would be even better)
2. Transfer "audio output" from a Windows 7 PC to the aforementioned Raspberry Pi
3. Everything sent over LAN/WAN (I am aware of the bandwidth limitations of LAN/WAN versus USB, but I'm not hooking up a storage medium to it)
4. IS NOT A REMOTE DESKTOP! (too high latency)

Background:
I have my quite noisy computer set up in another room, transferring HDMI video to my projector in my living room. So far, due to limitations on the HDMI transfer device, my audio needs to be transmitted separably, which I have done with a small device so sensitive to interference that it's harmful to my home theater system, (crackling, the 'SMS'-sound and it suddenly cuts out). I've been using three 5 meter USB cables with "repeaters", (AKA powered USB hubs), to be able to use a keyboard and mouse from my living room, but my significant other is not happy about it, and it's no solution at all.

Summary:
Using one of my Raspberry Pi mod B, auto-load an app in Linux to send its HID-input to an application/service running in windows, at the same time receive audio from said windows app using LAN. I need information on existing app(s), or some pointers to what I'll need to do this in C/C++. So to nerd it up abit: I need "USB over IP" from the Pi to WinPC, and "sound over IP" from the WinPC to the Pi.

Posted 14-Apr-13 22:21pm

Frank R. Haugen

Updated 14-Apr-13 23:59pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Marco Bertschi · Answer 1 · 2013-04-15T01:27:00

Solution 1

Even though I have not a great experience in remote service thingies, I'd suggest you to use
Socket programming[^] if you want to do it by yourself.

If you need software, use a VNC client[^] on the Pi and a a VNC server[^] on your Windows PC.

IMO a great thing which will work out fine if your Pi has enough power to process all the VNC data. Edit: Not capable due to the Pis limited power.

cheers,
Marco

Posted 15-Apr-13 1:27am

Marco Bertschi

Updated 15-Apr-13 1:50am

v2

Comments

Frank R. Haugen 15-Apr-13 7:34am

Problem with VNC is the sheer data amount due to the transfer of image data. (I have yet to find one that's non-visual). It's the latency in remote desktop and VNCs that's the problem, considering that this is for gaming, and video is already transmitted separably.

Thanks anyway!

Marco Bertschi 15-Apr-13 7:49am

I thought that this could be the problem.
I striked out the non-good part. You might want to try to do something yourself, sockets are always a good solution.
Maybe you can setup VNC on your localhost and use WireShark to sniff for some tricks you might discover when you see what is actually happening on the network?