Electronic – What would it take to add Bluetooth capability to a digital (musical) keyboard

You'll find this is often the case, when you try to build something from off the shelf parts that duplicates an existing product, almost always the parts alone will cost more than the existing product. The reason being that they can mass produce their product, buying parts in bulk cuts down on costs etc.

Look closely at the 'serial-over-Bluetooth boards', some of them do in fact support different profiles. What you are looking for is a module that supports the Bluetooth HID profile (Human Interface Device, aka mouse, keyboard, joystick, wii remote, etc).

Check out this previous question, it lists several bluetooth modules, which you can buy in single quantities for fairly reasonable prices, some or all of them should support HID.

I've never had an issue with I2C being audible in a circuit including using I2C adjustable resistors in a 60dB gain microphone pre-amp so i doubt you'll have much issue but here are some thoughts.

Avoid using multiple ground planes unless you really need it. You can easily cause more noise problems than you solve if your not very careful to avoid routing any signal over the split in the plane. Unless your goal is very high fidelity, use a single solid ground plane. In general you will find almost every mixed signal IC will call for separate analog and digital grounds/supplies. While this is great in an ideal world, if you don't have the space to do this properly, you will cause more noise problems than you will solve. For instance your better off using a single power supply with an LC filter in front of the analog input than you are running a separate supply across the board on a 15mil trace.

Other thoughts:

• Use an I2C clock above the audio range, 40khz or higher. Use the largest pull up resistors you can given your bus speed. This limits the current and hence noise generation. Also make sure the I2C bus isn't ringing, if it is use series termination at all devices (40-50ohm resistor should be fine). Match the I2C traces to 50ohm if you can and make 1 long run through all devices rather than T-ing off the bus.
• A single, solid ground plane. Remember that high frequency signals will follow the path of least inductance to ground, not the path of least resistance. With this in mind lay out the PCB such that ground currents from the digital portions are not traveling under the analog portions.
• Proper decoupling, do not use resistors. You have to calculate this for your particular design but a 0.1uF and a 10nF ceramic cap per power pin and larger, 10uF caps per major IC or section is generally a safe bet. Always place caps as close as possible to the power pin and get to ground ASAP. Don't be stingy with the vias, even using multiple vias to ground for each decoupling cap is not a bad idea if you have the space.
• Use either a separate regulated power supply or use an LC filter to segment off an analog supply from the digital supply. If you use a split plane, you again can't cross this split on an adjacent layer with ANY traces.
• Use protection around any sensitive analog components or pins. Ground rings around op amp inputs, etc. In fact a ground pour on the surface of the analog section is not a bad idea as long as its properly coupled to the ground plane (lots of vias) and doesn't have orphaned copper.