Device not recognized.

[monospace]

Just got my eDrumIn 4 and was excited to try it, but I can’t get the software to recognize the device. I’m using an iPad. Device is connected to a 9V adapter. When I insert a USB cable, the orange LEDs light up, and in the software, when I click the rescan icon, they also light up. But I never get past the “Plug-in your eDrumIn” screen. Am I doing something wrong or did I get sent a dud? If the latter, how do I exchange it? Thanks.

[Rob]

It's been a while since I tested the iOS app. Sounds like there's a bug. Do you have a mac or PC to test with?

[Rob]

BTW, no need for the 9V connector. The device can be powered from the iPad.

[monospace]

Yeah must be a bug in the iOS app. Couldn’t get it up and running on my iPhone either, but works on my MacBook.
Which is a little annoying as I like to keep that tucked away, running my DAW, in a rack 8ft away from my drum kit. Being able to tweak things from my phone/pad while sitting at the kit would have been perfect.

I’m using the 9V plug because I’ll be running the device through my TD-9’s midi in, as a replacement for my hats, ride, and snare. That is, once get my head wrapped around the nitty gritty of this thing.

Thanks for the quick response, it’s much appreciated!

[Rob]

I need to update the iOS APP for ED10, so I'll do some thorough testing next week. Sorry for the inconvenience.

[monospace]

Update: I was able to get the iPad app to recognize the device. Not sure what I did, maybe just connecting it to the MacBook first?
Still, on iPad the app is way too sluggish to be usable. It also randomly quits at odd moments.

[Rob]

In version 1.2 I've made a bunch of UI optimizations that should speed things up considerably.

[monospace]

While I'm here, may I request a pony?

How about a way to access the control application WITHOUT a device being connected? This would allow me to work on an imaginary trigger and then save that as a user preset for later use when connected, or for exporting and sharing. Please and thank you.

[monospace]

Another thing I noticed with regards to the (desktop) app: changes I made to my pads didn't "stick" when I unplugged the USB cable, not even after waiting at least 5 seconds before doing so. The only way I was able to get the device to retain my changes was to quit the control application before unplugging. Is this the expected behavior? It seemed odd to me.

[Rob]

It's not the expected behavior, but might not entirely be a bug. It should save 5 seconds after the last edit. The reason I do this to prevent the non volatile memory from being written to too often and shorten its life. I'll look over the code and make sure everything is as it should be.