Hello all from new teensy 3.1 user, and I will say in advance that these questions may seem a bit naive/reduntant/stoopid in nature, but I'm trying to wrap my head around a little project I've been considering, and it looks like the Teensy 3.1 is going to be able to accomplish the following:
I have a Korg nanokey2 USB midi controller that I would like to turn into a standalone midi workstation of sorts by hooking it up to the Sparkfun VS1053 based musical instrument shield, and routing the resultant audio to a small 2 watt amp and slimline enclosed speakers.
Enlarging the case for the needed boards/hardware is simple enough by adding a plastic ring in the center. Power is an issue but I will ask that question in a minute.
My first thoughts are that monitoring the nanokey2's output via the Teensy3.1 is a relatively simple matter via the usb midi read function detailed in Paul's examples. It also looks like including callback methods to then send the required midi data out the serial port to the musical instrument shield is doable as well, and I've already tested the audio portion of the circuit by directly streaming midi from a DIN-based controller to the shield and thru the amp/speaker combo.
It looks to me like this will all work okay, but I am not sure as to how I will:
a) Provide power to the nanokey2, as it usually is powered by the usb connection
b) Provide power to the Teensy3.1 - ideally I would like to power both boards with a high capacity lipoly pack and charge same via USB, but I'm not sure how to go about sequencing/controlling all of these different usb connections (nanokey2, teensy3.1, lipoly charger).
Suggestions and advice are actively sought and welcomed, including advice that gives me good reason for avoiding this project altogether...this is a very busy time in my life and if this is not doable, I would rather spend the time on something that is more realistic.
So a less wordy version of the above looks like this:
nanokey2 usbmidi -> teensy3.1 -> serialmidi instrumentshield -> audiochain
and the power considerations ?s
By the way, the instrument shield maxes at 3.7v, thus the lipoly choice.
Thanks for any comments, and please let me know if this should have been posted elsewhere,
Steve
I have a Korg nanokey2 USB midi controller that I would like to turn into a standalone midi workstation of sorts by hooking it up to the Sparkfun VS1053 based musical instrument shield, and routing the resultant audio to a small 2 watt amp and slimline enclosed speakers.
Enlarging the case for the needed boards/hardware is simple enough by adding a plastic ring in the center. Power is an issue but I will ask that question in a minute.
My first thoughts are that monitoring the nanokey2's output via the Teensy3.1 is a relatively simple matter via the usb midi read function detailed in Paul's examples. It also looks like including callback methods to then send the required midi data out the serial port to the musical instrument shield is doable as well, and I've already tested the audio portion of the circuit by directly streaming midi from a DIN-based controller to the shield and thru the amp/speaker combo.
It looks to me like this will all work okay, but I am not sure as to how I will:
a) Provide power to the nanokey2, as it usually is powered by the usb connection
b) Provide power to the Teensy3.1 - ideally I would like to power both boards with a high capacity lipoly pack and charge same via USB, but I'm not sure how to go about sequencing/controlling all of these different usb connections (nanokey2, teensy3.1, lipoly charger).
Suggestions and advice are actively sought and welcomed, including advice that gives me good reason for avoiding this project altogether...this is a very busy time in my life and if this is not doable, I would rather spend the time on something that is more realistic.
So a less wordy version of the above looks like this:
nanokey2 usbmidi -> teensy3.1 -> serialmidi instrumentshield -> audiochain
and the power considerations ?s
By the way, the instrument shield maxes at 3.7v, thus the lipoly choice.
Thanks for any comments, and please let me know if this should have been posted elsewhere,
Steve
Last edited: