Also, I noticed on the deep amp, there are lots of pops/clicks (every note pretty much comes with a click). Not sure if I am clipping something or my buffer size is too small–anyone have the same issue?
Sounds like a CPU or DPC latency issue, dropping an audio buffer. Which kind of system do you have?
Core i19 14900k with asus ROG motherboard 96GB RAM, SSD—windows 11
That’s a nice one 
You checked DPC latency? Also try 128 buffer@48.44Khz, in cause you are using smaller.
I am using 128-- I can try to measure latency-- Windows 11 no longer allows latencymon without some workarounds-- can look into.
You can hear it hear–its on pretty much all notes
Ah ok, yes I hear. This is not a buffer drop, but something I need to polish.
On another note, are the tracking presets in the windows version? I can’t seem to figure itout
It’s a hidden feature right now and I still need to document it. It will have to wait a bit until after a revision of the parameters in all the trackers.
Gotcha… thanks for the info! I am hoping this will also come with the ability to be able to store tracker parameters per plugin instance (not just tracker presets but a setting stored per instance of plugin). Just my thoughts…
Have a good one and thanks for the help!
Thanks for all the feedback!
1 Like
One more piece of feedback is (I’m not sure if this is new but I figured I would mention…), that the up and down arrows change patches if you have focus anywhere in MG3— this keeps causing me to change patches on accident and lose my settings.
Ah, you mean when running in a DAW and accidentally give MG focus and change patch?
You can disable the arrow keys in Settings => UI
Ah excellent-- yeah even actually when I click on another window it still keeps focus on MG3 for the arrows. Disabling arrows fixed my problem-- thank you!
I found that with the normal tracker you can also split into 6 midi-channels.
Midi channel 7 is the low Eand F,Fis G,Gis.Then comes channel 6 for A,As,B,C,Cis and so on.I was using Halionsonic,which has 16 midi-channels,when i figured this out.Is this new?
Yes. The non-hex trackers also split the notes to 6’ish MIDI channels. Thats required for MIDI MPE and multichannel MIDI. It’s not really a pr. string mapping though.
7 posts were merged into an existing topic: Detect individual strings on a standard guitar without a HEX pickup
in case you weren’t aware, MPE midi data is different, often described as ‘round robin’, in which the first note you play goes on channel x, the second on channel x+1, …third/channel x+2…
with halion it could get confusing if you expect the notes to be handled as they are in midi 1.0.
but it seems that halion is mpe capable, you may want to try that out.
Tried the external midi tracker for use with Fishman Tripleplay. Midi output has extreme velocity values. This happens when the audio feed option is turned on for the pressure envelope follower curve. If audio feed is turned off, the velocity values are correct.
You mean extreme high values?