That getyouratom link makes me think of those portable car battery jumpers. A lot of those have outlets on them. plus they can, you know, jump your car battery if need be. For example- http://m.harborfreight.com/12-volt-jump … 38391.html

Just be aware not to fully discharge them.

Really digging most of this stuff! I wouldn't sell short some of the earlier tunes, there is some good stuff back there. It certainly is "gamey", but i tend to to prefer it that way. I guess this is more encouragement than constructive criticism, but I signed up for soundcloud for the first time just so I could have easier access to some of those songs you posted. Some of the more boss battle/peril sections do get a bit repetitive in the slow build, like rise of the ravebots, but I get what you're going for.

So no dice with din-usb adapter cable? I use one with my micro korg to control soft synths on pc and ios. And it works great. Do arduino and teensyboy require a daw? I thought they could pair with midi keyboard as standalone synth.

Got it to compile with some help from the pjrc forum, now it is blinking correctly for startup. However, the switch doesn't seem to be working, and each time I plug it in it settles on a different mode led at random. Haven't been able to get any sounds out, and I'm really only looking to use it for mGB.
Am I right in assuming it requires a powered midi keyboard? Has anyone got it working with a microkorg as the controller? Anyone else face this situation?

My mods have gone fine with wire from a sacrificed phone line. Have also used salvage from otherwise broken usb and Ethernet cables.

being the first time I copied and pasted it, I noticed the "verbose" option, so here is the entirety with that box checked:

 Arduino: 1.0.6 + Td: 1.22 (Windows XP), Board: "Teensy 2.0"
C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mmcu=atmega32u4 -DF_CPU=16000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=106 -DTEENSYDUINO=122 -felide-constructors -std=c++0x -DUSB_MIDI -DLAYOUT_US_ENGLISH -IC:\Program Files (x86)\Arduino\hardware\teensy\cores\teensy -IC:\Program Files (x86)\Arduino\libraries\MIDI -IC:\Program Files (x86)\Arduino\libraries\EEPROM C:\Users\Joseph\AppData\Local\Temp\build3689661298163637741.tmp\Arduinoboy1_2_3_teensy.cpp -o C:\Users\Joseph\AppData\Local\Temp\build3689661298163637741.tmp\Arduinoboy1_2_3_teensy.cpp.o 

Led_Functions_teensy.ino: In function 'void updateBlinkLight(int)':
Led_Functions_teensy.ino:97: warning: comparison between signed and unsigned integer expressions
Led_Functions_teensy.ino: In function 'void updateStatusLight()':
Led_Functions_teensy.ino:109: warning: comparison between signed and unsigned integer expressions
Mode_LSDJ_SlaveSync_teensy.ino: In function 'void RealTimeLSDJSlave(byte)':
Mode_LSDJ_SlaveSync_teensy.ino:46: warning: suggest parentheses around && within ||
Mode_MidiGb_teensy.ino: In function 'void modeMidiGb()':
Mode_MidiGb_teensy.ino:37: warning: unused variable 'sendByte'
C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mmcu=atmega32u4 -DF_CPU=16000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=106 -DTEENSYDUINO=122 -felide-constructors -std=c++0x -DUSB_MIDI -DLAYOUT_US_ENGLISH -IC:\Program Files (x86)\Arduino\hardware\teensy\cores\teensy -IC:\Program Files (x86)\Arduino\libraries\MIDI -IC:\Program Files (x86)\Arduino\libraries\EEPROM -IC:\Program Files (x86)\Arduino\libraries\MIDI\utility C:\Program Files (x86)\Arduino\libraries\MIDI\MIDI.cpp -o C:\Users\Joseph\AppData\Local\Temp\build3689661298163637741.tmp\MIDI\MIDI.cpp.o 

In file included from C:\Program Files (x86)\Arduino\libraries\MIDI\MIDI.cpp:14:
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:76: error: expected identifier before numeric constant
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:76: error: expected `}' before numeric constant
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:76: error: expected unqualified-id before numeric constant
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:95: error: expected declaration before '}' token 

Also, I've never used this {code} trick before hopefully it embedded correctly, and is more helpful this way

sorry for not posting the error straight away, I was at work posting from my phone in frustration. here is the entirety of the error message:

  This report would have more information with
  "Show verbose output during compilation"
  enabled in File > Preferences.
Arduino: 1.0.6 + Td: 1.22 (Windows XP), Board: "Teensy 2.0"
In file included from C:\Program Files (x86)\Arduino\libraries\MIDI\MIDI.cpp:14:
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:76: error: expected identifier before numeric constant
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:76: error: expected `}' before numeric constant
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:76: error: expected unqualified-id before numeric constant
C:\Program Files (x86)\Arduino\libraries\MIDI\/MIDI.h:95: error: expected declaration before '}' token

I replaced the lib mod files as directed and have tried new and old  versions of the arguing ide on both xp and windows 7, all with teensyduino installed, but just can't get past the verifying of the code. I have the device selected and set to midi. I've tried Borge the first and second versions of the code.

Closest I've come is still giving an error that seems related to the lib modifications, but it only gets that far when I've replaced them.

I'm super new to arduino. Has anyone else run into this problem getting the code loaded? Am I supposed to add copies of the lib mods instead of overwriting them?

I know this thread is a bit old, but I did manage to combine a variable, half, and normal speed clock with one switch, hot switchable. I started a thread on here last year when I was struggling with the wiring, but it turned out that the only problem was an invisible solder bridge on my Ltc module.

It required removing the original crystal, and using a dp3t on-on-on make before break toggle selecting between the ltc and kitch's hot switchable 1/1 to 1/2 clock, "easy-clk" I think it's called.

Helpful tip for bennvenn's awesome gen2 linker- if you've loaded his lsdj patch to an ems64 usb, you need to hold start while turning on the system in order to get to the transfer screen and be visible to the computer. It's the equivalent of pressing start from the boot menu on the bennvenn flash carts, which I'm also pretty stoked about.

Also, a huge thanks to benn in helping me get my setup sorted out, responding to my multiple/ annoying emails super fast for the better part of a day.

any tips on a source,  other than a  donor? I  saw an older thread where kitsch mentioned working on a replacement ribbon,  but haven't heard of anything coming of it  quite yet.

a cruel turn,  but all  looks to end well.

with some tips  from Justin on where to look, I tweaked,  cleaned,  and got  the vc working.  then I  made the leap to a single switch (dp3t)  and got it to work as I hoped in conjunction with easyclk!

however.

the months of wiring and rewiring,  checking ,  taking apart,  and rechecking have  caught up to my little fella.  though I  tried my level best to be careful with the ribbon connector each and  every single time, I  have found that it has given up the ghost and will not allow me to close the unit without freaking out.  it works if you leave it juuuust so,  but breath on that ribbon and it gets nasty.

so. I thank  everyone for the help. I'll be hitting ebay for  another dmg  for the transplant. maybe I'll order some glow in the dark silicone buttons in the meantime.  hopefully pictures and a video sooner than later.

yep,  that was me via email.  you and kitsch have been really cool about helping me out so far, I  definitely appreciate it. I am indeed using the v1,  so that may be the problem.  I'll shoot you an email.

well, I  can't seem to  figure out how to post the pic I  took of my direct  variable clock wiring. I'll try to figure that  out  later.

however,  on following the drawing that Justin just posted, I have some change.

the easyclk  still works perfectly  as it had been.  whereas before engaging the ltc  would cause the system to freeze completely  requiring a  reboot,  now when I  engage the variable clock  the screen goes blank  but can be revived by disengaging the variable clock.  this occurs the same with the potentiometer checked across the spectrum.

well. new pot- still no dice.

as it stands, I cannot get the variable clock to function properly,  even when  wired with a new pot  and no switch.  at this point should I  assume that the ltc  itself is funky?

fair enough. my linear pot was a salvage,  so at this point I'm hoping  that it was just damaged  or unreliable,  causing a  ruckus.  the multimeter seemed to say it was good,  but I'm no great shakes at this stuff so I  could have been wrong. fingers crossed that a fresh  shiny new pot   exactly to spec does the trick