eDRUMin 1.3 BETA now available (again)

[monospace]

Changes in build 23

• Optimizations for devices connected to USB host port.
• Fixed some possible crashes with ED4 in the USB host port of ED10.

I'll post and iOS Tesflight update shortly that fixes a whole host of issues.

Updated both my devices to build 23 and installed the latest Testflight app.

ED4 plugged in to USB host on ED10, ED10 connected via MIDI out to computer; and USB out to iPad control app.

The rotary control display is fixed. Numbers now update in real time.

I played for roughly a half hour, making small adjustments here and there. Got only two crashes, way less than yesterday. Both seemed to occur approximately 5 seconds after my last interaction, so possibly related to writing changes to the device?
After powercycling from the last crash, my hihat pedal input had reset (see screenshot). Selecting pedal style #3 restored everything to where it was.

No other issues as far as I can tell.

IMG_2280.JPG (99.95 KiB) Viewed 1102 times

[Rob]

I played for roughly a half hour, making small adjustments here and there. Got only two crashes, way less than yesterday.

I take it that the app itself didn't crash, is that correct? Instead that hardware locked up, right?

[monospace]

Correct, same as before.

[monospace]

I played for roughly a half hour, making small adjustments here and there. Got only two crashes, way less than yesterday. Both seemed to occur approximately 5 seconds after my last interaction, so possibly related to writing changes to the device?

Tested this a bit more methodically and it doesn’t appear to be related. I got another device lock-up without touching the app, just having it open. Again the app didn’t crash; I would have sent a crash report if it did. Merely interacting with the controls also doesn’t necessarily lead to a lock-up.

[Rob]

Ya, I'll be testing here all day, too. I got through 20 minutes of playing and then the device locked up. It's some sort of race condition that's not a part of my code, but rather some very low low level USB MIDI stuff that's a part of a 3rd party library which I haven't updated in years. When using the iOS app, all data is sent as sysEx messages, whereas using the PC or Mac Control application, the data is sent using an HID interface which is much more efficient (iOS forbids the use of HID interfaces). I'll compare newer versions of the 3rd party library and see if there were any changes that might be fix this issue.

[dsteinschneider]

No problems here. Windows only, I always give the unit 5 seconds after making changes with the control program before playing. I'm working on Booker T and the MG's tunes - the hi-hat is playing like a dream.

[Rob]

Changes in build 24

• Fixed an issue that could crash the device when connected to iOS.

Should be rock solid now. I'm going to update the iOS app, but there are no changes. just incremented the build number.

[monospace]

Sooo close. I managed to get a solid 20 minutes of playing in (I timed it) and was about ready to call it done when the device locked up again. Powercycle fixed that, got the "please plug-in" screen but the app didn't see the device. App crashed when I force-quit it to start afresh. I sent the crash report.

[monospace]

So after writing the previous note, I went back in. Again, after 20 minutes of the app being open (& me playing some rudiments on and off & sipping a beer), the device locked up. Something's up with that.

EDIT: if I quit the app before the powercycle, everything starts up & works fine again.

[Rob]

I refuse to believe it. My hands are too sore to play more today, but I will try again tomorrow.