Pitch Modifier Options
- red
- F4 - Digitalis
- Posts: 3
- Joined: Sun May 14, 2017 2:04 am
Pitch Modifier Options
Would it be possible to have more options for pitch-modifying, such as adjusting samples by semitones? I feel like the current "percentage dial/knob" is a little hard to work with. When I wanted to adjust a sample by a semitone, I used Audacity to convert the value of a semitone to a percent/decimal value in order to adjust the sample in Giada. It would be cool if I could do all the adjusting in Giada.
- FFT
- F14 - Syrian Rue
- Posts: 549
- Joined: Thu Mar 08, 2012 6:51 pm
Re: Pitch Modifier Options
Honestly I agree with you, working with raw percentages is kind of a pain. I suppose a "semitone shifter" (e.g. +1, -1) would be useful. Let's see what the pitch-expert @Duchamp has to say about this.
- Duchamp
- Site Admin
- Posts: 41
- Joined: Thu Mar 08, 2012 6:42 pm
Re: Pitch Modifier Options
Pitch lord here. I see two viable options: semitone shifter and pitch presets.
Semitone shifter
Two buttons like + and - that lower and rise the pitch value. One octave contains 12 semitones, so each semitone is. Upsides: easy to use. Downsides: nasty rounding errors when shifting up and down especially in the long run (e.g. moving up and down several times between two or more octaves).
Pitch presets
A drop-down menu filled with presets like ...b3, b2, b1, 0, #1, #2, #3... where "b" stands for "flat" and "#" stands for "sharp". Upsides: zero rounding errors, everything is pre-computed (it's a look-up table after all). Downsides: limited range, less easy to use (user has to browse between a set of choices).
I lean toward the latter. I can't stand rounding errors that would force the user to manually tweaking the floating point value.
Semitone shifter
Two buttons like + and - that lower and rise the pitch value. One octave contains 12 semitones, so each semitone is
Code: Select all
1.0 / 12 = 0.0833333333333...
Pitch presets
A drop-down menu filled with presets like ...b3, b2, b1, 0, #1, #2, #3... where "b" stands for "flat" and "#" stands for "sharp". Upsides: zero rounding errors, everything is pre-computed (it's a look-up table after all). Downsides: limited range, less easy to use (user has to browse between a set of choices).
I lean toward the latter. I can't stand rounding errors that would force the user to manually tweaking the floating point value.