How do you think an octaver is the same as a polyphonic pitch shifter? Ever wondered why there's an octavia but there aren't a "fifthia" or a "thrdia"?Indeed.
How do you think an Octavia/Octafuzz works? Does it analyze the input pitch as well?
How do you think an octaver is the same as a polyphonic pitch shifter? Ever wondered why there's an octavia but there aren't a "fifthia" or a "thrdia"?Indeed.
How do you think an Octavia/Octafuzz works? Does it analyze the input pitch as well?
Indeed.
How do you think an Octavia/Octafuzz works? Does it analyze the input pitch as well?
No, you only add latency when you run your entire guitar signal through a send and a return.My kitchen sink preset has a stereo send before the IR block for a cab I one day intend to buy, and a stereo return before the final output that pipes in songs and backing tracks that then play through my FRFRs along with my guitar. Are these one way blocks adding any latency?
Whatever this may work like, the latency stays the same, regardless of the input signal.
I tried with: White noise, a 6-voice synth brass chord (extremely critical stuff), a single bass note, a power chord, a 4-voice epiano chord /w vibrato, a minor third with a clean guitar patch. Latency was consistent all throughout.
So?
Just a guess, but what do repeated notes of different frequencies look like?
I tested the virtual capo (default settings) on the fm9 by recording simultaneously a DI track and the output of the pitch block (which was shifting down 2 semitones)Whatever this may work like, the latency stays the same, regardless of the input signal.
I tried with: White noise, a 6-voice synth brass chord (extremely critical stuff), a single bass note, a power chord, a 4-voice epiano chord /w vibrato, a minor third with a clean guitar patch. Latency was consistent all throughout.
So different algorithms can exist
Fwiw, even if I'm no programmer at all, I still don't completely buy the "each pitch in a chord has to be analyzed" statement.
When you think about traditional pitch shifting, as happening with, say, vinyl records that you speed/slow up/down or samplers, hence as in length and pitch being altered simultaneously, the quality of the pitch shifting itself is quite excellent, just that the tweaked audio is also stretched/squeezed. In my layman book, all it'd take would be a stretching algorithm to be involved simultaneously.
But as said, I have absolutely no idea about programming, I just don't know why pitch analysis would be required on something that is basically just multiplying/dividing frequencies by a fixed amount while as well multiplicating/dividing lengths.
It's explained in the link I shared above why you need some form of pitch/frequency detection even for the most basic mono pitch shifter.Haven't tried that exactly. Might do so later on - but so far, all the tests I've done seem to indicate that latency isn't changing with (even vastly) different input signals. There's been a few pitched sounds when their initial attacks were hard to decipher because of the way less than shiny quality of the HX Poly Pitch block, but we're perhaps talking 1-5 samples of a possible "grey area" here, accounting for 0.1ms or something.
Fwiw, even if I'm no programmer at all, I still don't completely buy the "each pitch in a chord has to be analyzed" statement.
When you think about traditional pitch shifting, as happening with, say, vinyl records that you speed/slow up/down or samplers, hence as in length and pitch being altered simultaneously, the quality of the pitch shifting itself is quite excellent, just that the tweaked audio is also stretched/squeezed. In my layman book, all it'd take would be a stretching algorithm to be involved simultaneously.
But as said, I have absolutely no idea about programming, I just don't know why pitch analysis would be required on something that is basically just multiplying/dividing frequencies by a fixed amount while as well multiplicating/dividing lengths.
Also, if that would be happening with chords as well, why can't we then as well pitch individual voices within that chord? Should as well be possible then.
If we zoom in a little we already see that some notes are more aligned than others, for the first note the latency is almost invisible at this zoom level while the third note is visibly late on the second track
Simply changing the sample rate like you're describing changes the duration
so that's not how pitch shifter effects work.
Actually on the fm9 you can turn off the pitch tracking in the pitch block, hear how that sounds (first with it active and then turned off)
Awesome, thanks!No, you only add latency when you run your entire guitar signal through a send and a return.
Placement is crucial.Depending on the input material, Poly Pitch on the Helix often sounds more like the version without tracking.