LinuxMusicians

It seems that you have found a bug in the MuldjordKit3. The sample: MuldjordKit3/RideL/samples/3-RideL.wav seems to contain two crash strikes but should contain only one: Bildschirmfoto vom 2023-02-15 17-19-10.png I don't know who is in charge of fixing bugs in the kits but this should definitely be...

> When a DG version appeared with the option to "normalize samples", I assumed this feature was created to address this problem, and I imagined it would be just one single checkbox to let you either normalize all samples/leave them at their original volume. But it turns out it's not, it's ...

A short update on my investigations: I created an Octave file where I ported the power mapping function from Drumgizmo to Octave and tried to tune the power map parameters to match the Roland curve as closely as possible (https://github.com/corrados/edrumulus/blob/main/tools/misc/calibrate_drumgizmo...

> It's not as bad as the Tchackpoum hats on version 19, but there is a delay in the choke that is pretty noticeable. I assume that the following commit is responsible for the behavior: http://git.drumgizmo.org/drumgizmo.git/commit/?h=develop&id=380213d0a092a874182f1cf9c8d0cf828a624511 It was int...

> I also mess around with each drum's sensitivities and velocity curves in the Alesis "brain" - I'm still not sure whether that translates to the output I am pretty sure that it translates to the output. The problem of changing the curve in the edrum module is that MIDI velocities can only...

The only explanation I have that the ghost notes work for you in Drumgizmo is that your Nitro module may output lower MIDI notes on average than the Roland module. Than you are more on the left side of the yellow line in the graph and there the loudness varies much more than on higher MIDI notes. Or...

Connecting a Roland V-Drums module to Drumgizmo, it feels like there is almost no dynamic at all. Playing "ghost notes" is almost not possible. This is a topic which I discussed with deva a while ago via private chats. Since the MIDI velocity handling of Drumgizmo is such a fundamental thi...

I am running Drumgizmo on a Raspberry Pi 3 with my Edrumulus prototype:
https://github.com/corrados/edrumulus/b ... ype-3-hd-1
Here, I am running Drumgizmo with the existing CLI interface (without any GUI). That works perfectly for me.

Thanks. I don't know why (maybe a merge issue) but if I look at the following commit: http://git.drumgizmo.org/drumgizmo.git/commit/?h=develop&id=3dd3c332414bfbebd69bfd71a4a3198198525eb6, the include is doubled which is incorrect: +#ifdef HAVE_INPUT_ALSAMIDI +#include "input/alsamidi.h"...

On my PC I had a default value of 1024 which gave me more than a second latency.

I consider my ALSA midi implementation as done now. If you like, you could merge my branch corrados_alsamidi it to your alsamidi branch.

Here are my new changes: http://git.drumgizmo.org/drumgizmo.git/ ... 4c51cea44d
With this change, low latency audio is now possible with my audio hardware.

Have you used a cherry-pick for putting my commit on the develop branch because I did not see any merge commit? Should I now remove my branch and the commit on my branch will then be deleted by the git garbage collector? BTW: I found out that there are more changes to the ALSA output interface neces...

I think it needs a lot of consideration for it to make sense in a generalized way... I thought this is just an additional step after the sample selection. If a decision for a specific sample was made, you simply adjust the power of the sample by a factor which is derived from the difference between...

Yes, you are right. The ALSA out interface does not yet implement the getBufferSize function. I've added it to the following branch: http://git.drumgizmo.org/drumgizmo.git/ ... aoutbuffer