I didn't make any changes in that area, but I've seen times when it's been slow to program as well. It should still work though. You can try power cycling the unit. I'll investigate tomorrow.
For what it's worth, it updated fine on my machine.
eDRUMin 1.3 BETA now available (again)
- dsteinschneider
- Posts: 411
- Joined: Sun Sep 15, 2019 11:17 pm
Re: eDRUMin 1.3 BETA now available (again)
My Pedal 2 is correctly set as a momentary switch (QuickLok PS-25) that is working for program changeRob wrote:Can you check iland make sure pedal 2 isn't linked to the first input?
My Pedal 1 is setup for the hi-hat and is Linked to Input 1. How would I change it so it's linked to Input 3?
EDIT - I figured this out by reading the updated manual section for hi-hats. I clicked the Link Button - then all the inputs looked selected - then I clicked input 3 and it's icon changed to the hi-hat. I had tried to do this before reading the manual and didn't notice that the inputs all selected after clicking the Link button. I'm mentioning this as a potential UX issue. Maybe a pop up dialog box when you click Link that lets you know to select one of the inputs would help new users.
I think what I was expecting was:
1. Click LInk button
2. Icon of currently selected Input is highlighted
3. Click a different input which then becomes the only highlighted icon (switches to the hi-hat icon)
4. Done
I see why you did it the way you did - basically in my expected method you click Link and nothing happens because the current input stays with the hi-hat icon.
Thanks,
Last edited by dsteinschneider on Sun Aug 23, 2020 1:15 am, edited 1 time in total.
Re: eDRUMin 1.3 BETA now available (again)
The 1.3.0.7 beta is a very good upgrade from the 1.2.0.10. The hi-hat pedal problems I faced before are basically gone. The cy5 is much improved, and the cy12r/c is showing signs of working with bell sense on a single input. My Roland TD9 still triggers SD3 better overall. The ED4 does better on the snare (pd105), the KT10 is even, the TD9 better on everything else (pd85, cy5, cy12r/c). But the difference between the two is closing quickly.
In the event I was forced to upgrade my module (if it died), I had previously been unsure of whether I would go with a TD27 (especially for the digital snare) or the eDRUMin. But with the advances in the 1.3 beta and the continual improvements, the release of the ED10, and the massive price difference, I would have to go with the ED10 for my purposes of home practice and recording.
In the event I was forced to upgrade my module (if it died), I had previously been unsure of whether I would go with a TD27 (especially for the digital snare) or the eDRUMin. But with the advances in the 1.3 beta and the continual improvements, the release of the ED10, and the massive price difference, I would have to go with the ED10 for my purposes of home practice and recording.
Re: eDRUMin 1.3 BETA now available (again)
I actually ditched my TD-9 after a mere two weeks of messing with this device. The improved dynamic range on all my pads made it a no brainer. The hihat especially was a gamechanger for me. I'm still a bit mystified by the peculiarities of the rimshot control, especially on my crappy tom pads, but everything else has been a spectacular improvement, and it's still getting better, at a fraction of the cost of a higher end Roland module. (I doubt an expensive Roland would be any better, plus I really, really don't care about Roland's sound.)
Miscellaneous Roland triggers. ED-10 + ED-4. MacBook Pro (2015), 16G RAM, Big Sur. Superior Drummer 3. Logic Pro.
Re: eDRUMin 1.3 BETA now available (again)
Yeah, this process isn't clear. Took me a while to get my head around it.monospace wrote:I'm still a bit mystified by the peculiarities of the rimshot control
Rob, any chance of labelling the sections on the visual adjuster please? Even just 'RS' & 'SS' labels that sit in their respective black and green areas would really help.
Re: eDRUMin 1.3 BETA now available (again)
Ya, that's probably doable, it just gets awkward when the individual areas get small.
Re: eDRUMin 1.3 BETA now available (again)
I think the manual could be a bit more clear on this. If I widen any particular area, do I get more of that sound? What does the horizontal line mean? Is it a threshold, or is it a limit? How do they work together?
I've got it dialed in pretty well on my snare, through trial and error, but similar adjustments on the toms don't seem to yield comparable results.
I've got it dialed in pretty well on my snare, through trial and error, but similar adjustments on the toms don't seem to yield comparable results.
Miscellaneous Roland triggers. ED-10 + ED-4. MacBook Pro (2015), 16G RAM, Big Sur. Superior Drummer 3. Logic Pro.
Re: eDRUMin 1.3 BETA now available (again)
+ 1monospace wrote:I think the manual could be a bit more clear on this.
Apologies if this sounds patronising...monospace wrote: If I widen any particular area, do I get more of that sound? What does the horizontal line mean? Is it a threshold, or is it a limit? How do they work together?
Your snare drum hits (white lines) are displayed essentially like a graph. You use these positions on the graph to draw the areas where you want certain notes to be triggered. (Rob, this visual approach is genius)
Line height = velocity (how hard)
Line position left/right = difference between head and side sensors (or something like that)
You have 3 coloured sections overlaying this graph, yellow(ish), green and black. Yellow = snare head trigger, green = rimshot and black = side stick.
Hit a rim shot, and pull the green area left to just where the white line is. Hit a few side sticks and pull the black area up so that the top of the white lines all fall in the black.
Re: eDRUMin 1.3 BETA now available (again)
The 1.3.0.6 beta crashed mid playing yesterday and had to be restarted.
Is it possible to export a log report to send through?
Is it possible to export a log report to send through?
Re: eDRUMin 1.3 BETA now available (again)
I think I fixed an issue in build 6 that was causing a crash, so it might be fixed already in build 7. Unfortunately there's no way to export a crash log.MWJT42 wrote:The 1.3.0.6 beta crashed mid playing yesterday and had to be restarted.
Is it possible to export a log report to send through?