An experimental setup simulation for a RASPBERRY Pi LAN PARTY using 6 Raspberry Pi cw ops - all connected to the Ethernet switch/router local area network...sending and receiving morse code MIDI DATA to each other, using QmidiNet with LINUX NATIVE REAPER providing all the morse code software to convert cw audio to midi messages for transmit, and convert midi messages back to cw audio tones for receive.
Raspberry Pi using AUTOSTATIC REPO's for jack audio apps:
1. jack audio connection kit
2. LINUX NATIVE REAPER
audio to midi is used for transmitting to QmidiNet's inputs...FLdigi sending its qsk rt channel audio output into the Reaper audio input on one of the Reaper tracks....it is then converted to a MIDI MESSAGE NOTE ON/ note off UDP DATA PACKETS output by Reaper's Reagate plugin, and then sent out to everyone else on the local area network via the QmidiNet APP. Upon receiving the qmidiNET midi data packets..for every RazPi CW op connected and listening to QmidiNet's activity...the midi data packets are in turn, converted to cw audio tones by Reaper's plugin called Reasynth...Reasynth has adjustable rise/fall times, pitch, and volume on its sliders...
One possible advantage of using QmidiNet to have multiple CW OPS all sending and receiving cw is that MIDI DATA does not take up a lot of bandwidth on the LOCAL AREA NETWORK ...compared to audio...which does have a lot of bandwidth....
You can also adjust how you like to receive CW, what pitch, how loud, rise and fall times ...all inherit in the settings for Reasynth.
LINUX NATIVE REAPER, works very well with the Raspberry Pi....
see here for more info: http://forum.cockos.com/showthread.php?t=85588
NOTE: you can have up to 32 individual QmidiNet Channels for grouping cw ops together in certain "cw rooms"
NOTE: there are a few audio/timing glitches heard due to the simplescreenrecorder max'N out the CPU of the RazPi.. without the recording software running, they are very rare and few..depending on how "good" your NETWORK setup is with your router/switches and cabling ...etc...NOTE: WIRELESS will have more issues with packet delays and packet losses than straight wired Ethernet connections