I've got my pi two weeks ago and there are a lot of things I'd like to try with it. Actually it is connected to my tv and the internet and acts as a XBMC media server, remote controlled by my phone with an android app...

I had the same idea of a raspberry pi sound controller for rc models as described in the first post. But there's a big difficulty: the pi isn't a simple microcontroller but a complex system running a multitasking OS. This makes it quite difficult to do handle time critical problems which are easy to handle with a microcontroller.
An example: measuring the length of a signal coming from the rx. With a microcontroller you track the rising and falling edge of the signal with an interrupt and you are done.
But with the standard linux kernel on the pi the are no interrupts available to the user. So you would have to poll the input pin value as often as possible to track it's change. This costs a lot of cpu time and can be disturbed by other tasks using the cpu (and there are a lot of them in a linux system). So you aren't able to measure the correct signal length you might need to control a speed dependent sound.
The same problem appears when you want to generate signals for servos. Without a timer triggering interrupts this can't be done reliably.
There are mainly two ideas how to overcome this problem: the first is making system interrupts accessible to the user with some linux kernel patches. This works for inputs already but there are no timers available. The second is to attach an additional PCB to the pi which contains a microcontroller for these time critical task (e.g. the GertBoard). This microcontroller is connected via I2C or SPI interface to the pi to communicate with.
I guess there will be suitable solutions in the near future with the growing number of pis in the wild and the growing community of clever people working with it.