Trying to use the Kilohearts pitch shifter plugin to tune my guitar down 1/2 step for a song in the setlist. However I’m experiencing troubling latency. I’ve got buffer at 128 and same rate at 44.1. Jitter and Grain turned off (they contribute heavily to latency and crap tone). Latency is better than previous buffer setting of 192 but still I can hear
and feel the delay after a struck chord (it’s fine when plugin is bypassed). So how can I fix this? How low can I shrink the buffer before cpu load on my other rackspaces that use lots of synth and effect plugins cause pops and crackles? Are there other better pitch shifter plugins to accomplish this without all the latency? Only really need it for one or two songs so I don’t want to spend a lot.
In Overloud TH-U 2 (which is included in the GP 5.1 update) there is a built-in transpose feature you could try.
I’m on GP 4.8. Didn’t know about the detune feature in 5. But I have a couple big gigs next week so I don’t want to do an upgrade right now. When I added a new interface a couple wastage I had to relearn midi on all my widgets. Took awhile. Guessing that may be the case with the upgrade as well presuming there are no other hitches.
The detune feature is not explicitly part of GP5 - it is part of the included lite version of TH-U
Audio pitch shifting does tend to have noticeable latency though there are some low latency plugins out there that may be good enough, e.g. Slate Digital MetaPitch
Some suggestions are here: Realtime Pitch Shifting Transposer plugin?
I contacted Overloud about upgrading THU to fully licensed version. They said I could upgrade through GP. Is it possible to run THU 2 on GP4.8 and if so how would I go about the upgrade?
Yes, the reason they recommend you upgrade through GP is because you can get a 10% discount on TH-U if you are a GP customer
Visit
https://gigperformer.com/partner
No reason why it wouldn’t work on GP4 but I would point out that the reason you don’t want to upgrade to GP5 (because you have upcoming shows) is the same reason you shouldn’t upgrade anything else unless you have plenty of time to deal with any issues that might arise.
I guess you didn’t use the Rig Manager?
I don’t even know how
A) It’s documented in the user guide where we explicitly say, The Rig Manager is designed to speed your workflow by eliminating the need to teach controllers to Gig Performer every time you use a different keyboard or controller
B) There are several videos that explain exactly how to use the Rig Manager, for example, https://www.youtube.com/watch?v=wPtsxeVEfy0
C) There’s also a blog article I wrote a long time ago. (Rig Manager has been available in Gig Performer since 2018 in GP 2)
A google search will find you other resources
What’s really quite fascinating is how good a job ChatGPT does in explaining both the purpose and the how-do of Gig Manager (I just tried that out of curiosity)
I do remember reading about this feature when I first started but since I’m only using one controller didn’t think I needed it at that time. I also wasn’t aware that a new interface (Motu M4 replaced the M2), would be seen as a different controller
The MIDI port name was probably different.
I use a plugin to tune many semitones lower
as many as 3 semi down for playing
Living La Vida Loca which is performed in standard C# tuning I think.
I use the Eventide H3000 plugin
No noticeable latency on my 2023 MacBook Pro M2… yes the tone changes subtly of course and it’s really not very polyphonic, however it works for the most part.
Also unrelated but noteworthy the filters on the H3000 plugin are voiced or particularly suitable for guitar processing.
Just a guess but perhaps it’s app related?
Have you tried other version vst3 versus AU versions etc ?
I haven’t tried other versions but I’m currently using VST3. I’ll try the AU and see. I’ve got the latency to barely usable but low end notes still have lots of jitter.
I haven’t used a pitch shifter myself but it doesn’t surprise me that low notes cause issues. Unless one does some really clever processing, It takes longer to recognize a low frequency than a high one (basic physics here) and that could cause issues. This is why pitch to MIDI tools are tricky
It’s actually audio pitch shifting. Midi isn’t an issue.
Yes, I know that – we are only talking about audio pitch shifting. What made you think I was suggesting MIDI?
The pitch recognition to produce MIDI is just another example where recognition of the low notes are tricky.
Simple physics: 80 hz means 80 full cycles per second. This implies one full cycle takes 1000 ms / 80 → 12.5 ms.