Note-on/off artefacts with Hornet Hatefish

Using Hornet Hatefish with GigPerformer (V4.1.5) in Windows 10 gives strange additional ‘ghost’-notes when creating any rhythm.
Having no external input sources and Hatefish creating simply 4 quarters per bar, Hatefish sends sometimes additional note-on note-off events to Battery in this case.

Hatefish/GigPerformer seems to add (ghost) kicks after 250 ms (a 16th note). Not always but quite frequently.
Changing the length parameter (LENGTH 100 seem to be about 250ms) does not change anything with the unwanted ghost-kicks, it just sends the note-off command as expected (LENGTH 50 around 125ms)

The screenshot shows the general set up and a midi monitor window displaying these odd ghost-notes. You can see 2 different ones: first very short ghosts (e.g. 5998 to 6000), and second false-regular notes like the one from 6250 to 6498. As we have a tempo of 60 BPM and only quarter notes triggered, there must be no note triggered 250ms after a quarter beat (every 1000 ms)

This might be a problem with Hatefish or GigPerformer, but this does not happen with Cubase (instead of GigPerformer) and less frequently under MacOS with GigPerformer.

Have you reached out to Hornet? We don’t generate extra events

Yes, of course, but they don’t either. I suspect that no one is intentionally creating those note events :slight_smile:
Most likely it’s the combination of GigPerformer and Hatefish as Cubase does not show this issue at all with Hatefish.

No, sorry, but the fact that it works fine with Cubase does not imply a bug in GP, it just means they did enough testing with Cubase but not necessarily enough with GP.

I’m not saying with 100% certainty that it is not a GP problem and we work closely with plugin developers to track down such issues wherever they are. Please see what Hornet has to say about it…if necessary we will reach out to them as well.

1 Like

When I look at the MIDI monitor I see that a Note On message is sent and then after that a Note Off.
For me that are not Ghost Notes, or do I miss sonething?

Maybe my wording is misleading here, pianopaul. There are additional notes which do not belong there. They are (strangely) aligned with the rhythm - either immediately following an note event (giving a kind of flam) or on an 8th. I just named it ‘ghost’ as it does not really belong there, but is also really a kind of a real but unwanted ghost-note.

Is it VST or VST3 you are using?
And what happens when you are using for example the length of 4th?

And what is LFO for?

Apologies if you got the impression that I think it’s GP fault - I didn’t mean at all that it’s necessarily GP’s fault, that’s why I wrote it’s the ‘combination of GP and Hatefish’.
I just wanted to ask if someone with insight could take a look at this combination and figure out where to tweak.

It’s both, VST2 and VST3 having these problems.
The LENGTH is set to 100, the maximum, what makes 250ms. Not sure if this is related with the tempo, but here you can see that the note length is always about 250ms (besides these ‘ghost’ notes, they can be very short though). Changing the length does not change anything in the erroneous behaviour.

The LFO in Hatefish is the frequency for modulating the note velocity (volume), the corresponding AMOUNT gives the amount of this modulation.

Did you sync the plugin with the global play?
Does it start when you press global play?

No apologies necessary – we’re not being defensive etc., if it’s our bug, we will most certainly deal with it - it’s simply that we would have expected to see this reported with lots of plugins that generate MIDI data so there isn’t really enough info here to hone in on the problem.

No matter if I sync externally or use GP standalone. Same issue.

I’ll try to find some other MIDI note event generators and keep you updated.
Maybe you want to check if you can reproduce this issue with Hatefish?

What happens when you remove the 1st, 2nd and 4th note?

OK, I set up a similar scenario with Steinberg’s Groove Agent. As I’m testing at the moment on a Mac it took a little longe, but also with Groove Agent there are these junk notes (maybe a better expression for the ‘ghost’ notes).

Not sure if this has anything to do with this issue and I’m not sure if these internal MIDI monitors are reliable, but the jitter in GP is extremely high in comparison to Cubase which is pretty rock solid (maximum 10ms vs. maximum 1ms). The Groove Agent double note on event happened 10 ms apart, but that just may be a coincidence.

Just leaving the 3rd beat in gives this error

I had a free midi sequencer (Harvest Mini) that I tried to replicate the issue with, but couldn’t (I’m on MacOS Mojave). I was outputting the midi events to the Protokol monitor app, and then dumping it into a spreadsheet to be able to pick out any outliers.

One comment about the Hornet plugins - I tried the free version of Hatefish - and the VST version didn’t work at all (it only output Note Off messages). VST3 was ok. But it didn’t fill me with confidence.

EDIT: I recorded 750 messages from the Harvest Mini plugin (1/4 notes @ 120bpm), I couldn’t find any extra notes when I analysed the data.

EDIT#2: I tried the same test with the Hornet RhyGeneratorOne and didn’t find any issues with the 750 notes I recorded.

Thanks for the hint rank13, I‘ll give that try.
How did you set that up in GP? Can you provide a screenshot?

I routed the plugin to a virtual midi output block in GP. MacOS has these virtual ports built in.

The Protokol monitoring app was then able to record the messages.