But I can say with 100% assurance, that TRIGGER is the absolute tightest drum replacer on the market
you sure about that?
but that offset is not what's bothering me...aptrigga has an offset sometimes, but then it's always by the same amount, so I can just slide the entire track and every hit is spot on.
With Trigger IF there's an offset (as I said, it works great 99% of the time) it's always by a varying amount of time, so every single hit has to be checked by hand...I can only assume that this might be because of Trigger trying to be in phase and reads the phase wrong from some trigger tracks? don't know.
not saying trigger isn't tight (even on my system it's really tight 99% of the time), but sentences like the one quoted above sound weird (to me at least) when they can be proven wrong that easily.
in this case the triggertrack was as clean as it can get...just the sample was a rather difficult one...
aptrigga just spits it out as soon as it sees the trigger-spike coming up...now the samples might be too late or too early, but always by the same amount....trigger tries to get the sample in phase for every hit (which is a nice idea), but with some samples or some triggers (piezo) it might not be that easy to "read" the phase, hence the offset?
just a guess, but that might perhaps be the cause, dunno.
I appreciate you trying to help though, I understand that with all the different systems and combination of software etc troubleshooting can be difficult sometimes
EDIT: I have TRIGGER v1.6, didn't know about 1.62, gonna download it now.
but since apparently my problem doesn't exist I doubt that 1.62 includes a bugfix for it
EDIT2:
not a problem, just an observation/question..
I've noticed that the samples on the printed tracks are far lower in volume than the actual sample used to create the TCI (even if the input trigger is peaking at the very top), why is that?
as I said, not a problem at all, just wondering