Hello. Registered serial # SUB00431 checking in.
Problem: Tuning not correct.
‘C’ registers as a ‘B’ on tuners.
I just read about how the active panel can be set to do this, but i have never attempted any active (hidden) features.
Followed manual to reset ‘C’ to ‘C’, but it is still off.
Middle C is registering 265.8Hz (standard is 261.6Hz, enough to be noticable).
C5 is 531.8Hz (should be 523.3, not good)
Also, please note I followed the forum instructions to update firmware to 1.1.5.
Firmware has been successfully upgraded.
Problem persisted before and after firmware upgrade.
Active Panel procedure for Reset Global and Reset Factory Settings did not affect either.
Please advise on further diagnostics. Thank you.
I understand it can use some settling time for tuning, but it’s been on for an hour and should be settled.
Not a super user… in my setup, I sometimes send MIDI sequences, but no strange CC messages or anything.
So very odd.
Currently, can’t use it at all… it’s so bad for your ears to get used to incorrect notes.
Team Moog… do you have any methods for calibration or fine tuning by the user?
enter Shift Mode by holding Bank 4 + pressing Activate Panel;
press and illuminate the Bank 3, Bank 4, and Patch 4 buttons, then play the lowest C# key two times.
you should hear a low A, a high A, then a low grumbling sound as the lowest notes begin to calibrate. If all goes according to plan, a few minutes later the tuning process will complete tuning the highest note.
Sysex file:
Transferred via C6 app. Verified Config was set to the Sub Phatty.
Sent… no acknowledgement, so sent again just because. Transfer happens so quick because it’s such a small file.
Next, ran the calibration.
On note 3, it seemed to take a very long time. Ran through all the values.
Next, used my tuner app, and verified problem is persistant.
To cross check my reading, i used a very vanilla patch on my DSI Evolver keyboard.
Verified Evolver is 130.8 Hz right on the money, and Sub Phatty the C# key is 133.2Hz.
One other data point you will have to trust me on… I know where C is on the keyboard.
Finally, sent the sysex via midi (instead of USB), and repeated calibration procedure.
No effect.
I find it odd after doing the sysex and calibration, my re-mapped keys are still effective.
Is there a total factory reset method? Remember I already tried to restore all parameters
Please advise. Is there any under the hood data dump I can provide for diagnostics?
Thank you.
I am new here so I will give a brief “hello”! My name is Keith.
now that I have that covered, I think this response I quoted may be the answer… did you check to make sure your fine tuning knob isn’t out of position? it should be pointed to 12 o’clock. if it isn’t, then no amount of tweaking or software fixes will do any amount of good. I am sorry if this is something you already knew to check, but I didn’t see you mention it.
Let me first say I am proudly holding my idiot flag up high.
It was the fine tuning knob all along.
I had no idea there even was a fine tuning knob.
But this thread will certainly help others in the future that have an issue.
What we have also learned is after firmware update, calibration routine, and restoration of factory settings, the knob position is King. This may be valuable information for troubleshooting issues beyond just my tuning.
Thank you to everyone, especially Amos and stiiiiiive.
You must be kidding… I thought about it at first read, but finally advised again posting…way too obvious for a man who seems so thorough with his testing…
Anyway , to cheer you up, I will tell you about the time I posted about that darn pitch tuning knob on the Etherwave that had no effect on the pitch at all. My thing must be broken. Then I read the instructions.
That’s the thing about Moog stuff, it gets you so excited you forget about the basics.
I’m so glad you got it worked out. I almost didn’t post my suggestion. I didn’t want to come off like a jerk on my first post if you had already checked that! LOL
On a side note, it’s interesting how you’ve been searching in the hidden functionalities or weird places while the guilty knob was the first one on the panel, right here. No offence meant, this happens to anyone. My point being sometimes the mind gets stuck on one particular idea and even obvious evidence need support to get it out of there.
Hurray! Some folks are going to say that we’re missing the point of voltage-controlled oscillators, but precise tuning control of both oscillators was one of the Sub Phatty’s big selling points for this happy owner (me).
I had a faux tuning issue of my own yesterday, which I’ll record here in case someone else has the same problem later.
In the morning I recorded some bass loops into my iPad, and in the afternoon I tried to layer them with Sunrizer (one of the best iPad synths). Something did not sound right! I pulled out my Korg bass tuner and the Sub Phatty was sharp. Odd… I checked the init patch, and it was dead on – which made me think it was a patch problem, not a hardware problem. Inspecting the panel (which hadn’t changed much since I saved the bass patch), I noticed that (a) pitch modulation was considerable and (b) LFO rate was quite slow. I turned down pitch modulation and the faux tuning issue disappeared. Speeding up the LFO to vibrato speed would have worked too, no doubt.
In case anyone else is having tuning issues across multiple octaves since the official Sub Phatty Editor (and associated firmware) release and having no luck with note calibration and fine tuning adjustments… I found that the SubPhatty_Calib_Init_Values.syx file Amos provided in this thread followed by the standard note calibration procedure outlined in the manual solved my problems.
My tuning idiot moment: hooked up my MiniBrute through the Ext Audio In of the Sub, MIDI out of MB to Sub then started palying. Ugh the D and the A keys are way out of tune with each other. WTF?!?
um, oh yeah, I left the Sub in MeanTone tuning. Doh!