Looking at the standalone editor I get a visual representation of my knobs when I move them. I can see and hear that some of them are not matching up on a 1:1 basis. For instance my VCO 1 LVL & VCO 2 LVL only use about 50% of the physical knob-turn to show 100% of the turn on the editor. What I'm seeing is also what I'm hearing, past half-way the knob doesn't increase the volume. I get the same anomaly on other knobs like AmpDECAY only uses about 30% of the physical knob to reach 100% of it's affect. Knobs like the CUTOFF and RES and VCO2 FREQ all perform as expected, audibly and visually within the editor.
Any ideas?
Odd knob behavior.
Re: Odd knob behavior.
Have you tried a pot calibration routine yet?
http://forum.moogmusic.com/viewtopic.ph ... ot#p116840
http://forum.moogmusic.com/viewtopic.ph ... ot#p116840
http://audiotecna.info
T-III, Voyager, VX-351, Slim Phatty, Model D, Sub Phatty, Subsequent 37, Minitaur, all moogerfoogers and minifoogers, EW+, Theremini, Model 15, Filtatron, Animoog, Model D App, iOS 11 Mother-32, DFAM, Werkstatt, Win7, High Sierra
T-III, Voyager, VX-351, Slim Phatty, Model D, Sub Phatty, Subsequent 37, Minitaur, all moogerfoogers and minifoogers, EW+, Theremini, Model 15, Filtatron, Animoog, Model D App, iOS 11 Mother-32, DFAM, Werkstatt, Win7, High Sierra
Re: Odd knob behavior.
Thanks for the suggestion. I just tried the knob calibration routine and it did not fix my problem.
Any other ideas?
Any other ideas?
Re: Odd knob behavior.
I believe the editor send 14-bit NRPNs, which is two messages MSB and LSB. Is one of them missing? You don't have 7-bit controllers turned on the Minitaur or the Editor?
Gear list: '04 Saturn Ion, John Deere X300 tractor, ganged set of seven reel mowers for 3 acres of lawn, herd of sheep for backup lawn mowers, two tiger cats for mouse population control Oh you meant MUSIC gear Oops I hit the 255 character limi
-
durgaprasadzone
- Posts: 1
- Joined: Sat Feb 28, 2015 3:15 pm
- Contact:
Re: Odd knob behavior.
Thanks for sharing info... 
Re: Odd knob behavior.
The MSB and LSB do not each cover one half of the parameter range, as then the bit deepth would be only 2x 128 available values = 256 values = 8 bit.MC wrote:I believe the editor send 14-bit NRPNs, which is two messages MSB and LSB. Is one of them missing? You don't have 7-bit controllers turned on the Minitaur or the Editor?
It is rather MSB doing the higher 7 bits and the LSB doing the lower 7 bits. So the bit deepth is 14 bit = 2^14 = 16384 different values.
Therefor:
The MSB is covering about 99.2% of the range.
The LSB is just filling up the values in between and from value 16256 (binary 1111111 0000000) to 16384 (binary: 1111111 1111111).
keep on turning these Moog knobs
Sequence:
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16
Sequence:
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16
Re: Odd knob behavior.
Wanted to bump this as I am having a rather weird pot problem.
My VCO 2 Freq is controlled by my FF pot. I get no response from the actual VCO 2 Feq pot but I can change it in the stand alone editor. In addition as I turn the filter frequency pot up, it changes the tuning of VCO 2.
It seems they, FF and VCO 2 Freq, got tied together somehow and I cannot figure out how. Just bumped up to 2.1 Firm and 3 Editor. No problems prior to this.
My VCO 2 Freq is controlled by my FF pot. I get no response from the actual VCO 2 Feq pot but I can change it in the stand alone editor. In addition as I turn the filter frequency pot up, it changes the tuning of VCO 2.
It seems they, FF and VCO 2 Freq, got tied together somehow and I cannot figure out how. Just bumped up to 2.1 Firm and 3 Editor. No problems prior to this.
Re: Odd knob behavior.
I have not figured out my issue yet. Haven't had the time to call support. If I do figure out my issue, I'll be sure to report back.
Re: Odd knob behavior.
Well I tried running the knob calibration again and everything is working! I may have been trying to send the knob-sysex-calibration in bootloader mode when I tried to resolve this unsuccessfully before.