Minor issue.
I started looking at drumgizmo, and i sure like the sounds.
If i create a short region, 1-4 bars, loop over it, and insert the wanted instruments during that, after the first runthrough the region the first repeat of the loop the first beat gets completely ignored (both, kick and hi-hat, in my case).
I am aware this, vanishing or not played midinotes have been an issue in the past, but i haven’t seen them in a long time.
I tried it in Ardour 8.12, 9.2 and nightly.
I copied the midi-regions to another track with another virtual instrument, there it doesn’t happen. As far i can tell nothing wrong with the region itself.
I didn’t find any web results for it regarding ardour+drumgizmo, so i assume i am simply doing something wrong with drumgizmo.
Also i got a low-spec computer, not sure if that might be the root of the problem, drumgizmo soundfonts usually being big. (8 gigs of RAM, Celeron(R) J4105 CPU @ 1.50GHz).
Sometimes, when I’m working with MIDI in Ardour for a while, I get sounds at the starting point that aren’t represented by any notes at that location. Like the frozen hunting horn from the storyteller Baron Munchausen. I find that funny
Thanks.
But: Oh, i don’t seem to have been clear. It doesn’t happen occasionally, but every time
(let me add: everytime since yesterday, before that i didn’t use drumgizmo Since yesterday i tried everything i could think of, different soundfonts, moving the region, different ardour versions and what not, it stays. )
If i drag the region from drumgizmo to another track with another plugin, it works just fine.
Also the first run of the loop works, it is the second run when it starts to happen.
The workaround i found is to disable “snap to grid” and move the midi notes on beat 1 a tiny bit forward in time, a 1/128th note doesn’t always suffice, a 1/64 does.
beat 1 i mean the first beat where the loop starts. It only happens there.
I looked at midimap, and after the loop ends (or after it starts) there is a second
midi-note “On”, but i checked that with other plugins, and it seems to be the normal case.
Ardour 9.2-129 appears to have a bug where if you stop the transport in the middle of a MIDI note and then back it up and start rolling again you get to hear the note you just stopped on. Even if there’s no note under the playhead at that point.
It seems to be fixed in 9.2-588 but I haven’t researched exactly when the issue occurred and when it was subsequently fixed.
Don’t get me wrong here, i am anything but complaining, all is good info:
To me it seems, as if the problem mentioned by @guth is a different one, though also related to midi-notes?
(let’s assume my assumption is correct : )
As there are probably a few drumgizmo users, i think i really am doing something wrong with drumgizmo.
Mainly cause i have it in all tested Ardour versions.
I use it the way i user other plugins to quickly loop over a region, and with other plugins i don’t have the described problem. But not fully knowing a tool yet, i might well oversee something most obvious for others.
As said: i kinda found a workardound which, for my workflow, does the job well enough. But i am curious (mainly as it seems a lot i’d stick with drumgizmo, cause i like it ).
You can stick with the DrumGizmo; for me, it’s also the first few notes when the part loops. But even with the organ SetBefree, the first notes are sometimes silent in the loop. All the notes are audible on a single run.
I use setBfree quite a bit. I didn’t have it here yet, and, as said, it happens for drumgizmo constantly. Every time. not sometimes.
I’m gonna test that later, even though i am quite sure, regarding setBfree.
@n4dir I don’t think you’re doing anything wrong with Drum Gizmo. I have the exact same problem. I often do the same thing as you. Make a 4 bar drum pattern. Set the loop range to the region. Loop. The first time through any note directly on the first beat note plays. For, all subsequent passes any note directly on beat one is silent (interestingly the Ardour MIDI tracer shows the midi out for the track playing a note on/off as expected for every iteration of the loop).
Drum Gizmo 0.9.20 (DSR Kit)
In both Ardour 8.12 and 9.2
While my PC is quite old it’s modestly faster (i5-3570 @ 3.4 GHz and 16 GB RAM). I don’t think it’s hardware.
This is from memory, but perhaps it will help searching the original problem:
I believe the end of a loop sent an all notes off so that there would not be a hung note sounding forever, and in some cases the note off and the next note on were so close together that the note on was missed.
Maybe that description is not completely accurate, but I think it is close. There may be a configuration option to change the behavior in 9.0 or 9.2, but I haven’t needed it yet so haven’t looked for the location.
But AFAIK it shouldn’t affect plugins. Anyway, it might be worth trying to disable the MIDI output ports should send panic message at the end of a timeline (transport) loop option in Preferences → MIDI.
i like that