eDRUMin 1.6.1 BETA

[monospace]

So this is just an app update, not a firmware update?

[monospace]

Anyway, got this crash, within minutes of sitting down to play.

edrumin_crash_110121.txt.zip

(21.09 KiB) Downloaded 122 times

[monospace]

And another, this one after I engaged a foot switch pedal on the ED10.

edrumin_crash_110121-2.txt.zip

(20.79 KiB) Downloaded 120 times

[hang12]

For reference maybe...
eDRUMin 1.6.1b4 with two eDRUMin10's, running 10.12.6 on a 2012 MacMini, internal SSD running 3.7GB worth of two instances of SD3 kits on DP9.51.
Trying to hold off upgrading this machine until the Mac mini M1+ pro model shows up...

No eDRUMin app crashes at all. knock on wood...
Only current glitches I get are audio - i.e. when the main kit SD3 GUI window is open, the Mac mini is trying to keep up on a lot of ride cymbal graphics.
Close that window - works fine.

Great work, Rob! Everything is snappy.
This is so much better (and more fun) than triggering SD3 thru a combo of ancient Roland TD-20/TD-10 brains.
(will hold off on these newer 1.6.1 builds until the dust has settled)

[Rob]

Same here. I've stress tested the application so many times. I've checked an rechecked all my pointers. I'm really at a loss. Unless some others can also confirm crashes, I think this might ultimately come down to an issue with monospace's machine. Perhaps a driver conflict or something. I've spent about 50 hours looking for an issue that doesn't seem to exist and it's tiring and killing my drive.

[jacko]

I'll try and find time to download and run the latest beta in the next few days. perhaps ironically, I've been delaying because of monospace's issues - maybe that's the case with many of us which is why you haven't got a broader base of testers this time around?

will report back

[monospace]

If nobody else is reporting crashes, then it would seem obvious that the problem is on my end. I don't think people should hold off upgrading because of that. it's still sold hardware and software.

[Dadwrshpdrum]

I have not seen a crash. I’ve stayed up to date with 1.6.1 betas. My machine is similar to monospace but a bit older. Also I’m still on Catalina. I leave the unit and app running day and night, but I only get to play a few minutes a day.

I did have another glitchy software update today. My update process is always the same. I close the app and then run the installer. Before I open the app after the install I unplug the ED4 from USB hub. Then I open the app and only the ED10 should be present. Normally at this point I update the ED10, unplug the ED10 and plug in the ED4 in its place and update ED4. For the last two betas this does not work. When I open the app the screen shows what looks like a grayed out ED4, but the ED10 is connected. I have to power cycle the ED10 before the app recognizes the device. Then no problems.

Software is very stable for me and the unit continues to play super well.

[Rob]

I finally found a crash today--related to having a sustain/footswitch connected. I will keep looking.

[Rob]

Fixed a potential crash related to having a sustain / footswitch connected. Footswitches have two switches and the index of the switch is encoded in data from the device. Well, occasionally the device is saying it's switch number 255, which of course doesn't exist -> crash. I've fixed it in build 7 (no firmware update). The real source of the issue is in firmware however, so I still need to track that down and sort it out. I also fixed some macOS wierdness when plugging in and unplugging devices.

https://www.audiofront.net/eDRUMin_Cont ... .6.1.7.zip
https://www.audiofront.net/eDRUMin_Cont ... .6.1.7.zip