Hi, I’ve been running into some tuning issues with the Super-8, and they’ve emerged after using the synth off and on for a few months. I did some tracking with it in late March, mainly with preset sounds, and everything was great/in tune.
Now I’m more involved with programming on it, and things have changed. Presets that I have recorded in perfect tune are now 20-30 cents sharp. In general I have taken the master tune about “two LED lights” down to get back to 440Hz.
What gets weird: doing Init Patch is perfectly in tune (if the synth master tune is back to “440” that is).
I’m not sure what I should be doing exactly at this point. I haven’t tried a factory reset since that means reloading all my patches … I do wonder if maybe I restore the some factory patches from USB they’ll magically be in tune. What’s annoying is that some of the presets I made a few weeks ago are now out relatively to each other. I’m resolving this with the layer tuning so far.
I’m desperately hoping I don’t show up to a gig and the synth is way out and I have to layer tune every preset. Is anyone else experiencing this? BTW I did try the manual lower + hold lower procedure, no idea what that does … it did not resolve the issue.
Have you checked layer tuning, like is the tune offset same for upper and lower layer in dual mode? if so, its probably related to performance tuning.
Any MIDI NRPN related to detuning in effect?
I’m using both global and layer tuning to resolve the issue at the moment. Global, because factory patches are now sharp; layer for my performances for live which are inconsistent even with each other/across layers in the same patch.
I don’t think so? Not intentionally. I am using a norns connected over USB for MIDI interaction, but I’m only sending note_on/off, midi CC and program change. I don’t understand NRPN in any case, old 80s-era midi geezer here.
If you want, you can send me a couple of performance / patch files + your init patch/perf files from the synth drive, and I can check what detune values they´re stored with.
Thanks for the offer and I’ll happily do that, but I’m wanting to understand why the factory patches are off.
I went ahead and diff’d “performances_a/h1/x5_UnpreparedPiano_DN.xsg” from my keyboard with the factory patches zip and they are identical. I power-cycled the unit and started it with no MIDI connection, and the factory patches are still 30-40 cents sharp (even though the init patch is still true). It would seem something in the unit is causing this no?
I can check what detune values they´re stored with
If possible it would be great to know how to find this in a hex editor 
May be something related to global config in the firmware (which I assume is latest 1.33). You can do a global reset which shouldn´t affect stored patches, though I recommend doing backup anyway beforehand. If that doesn´t help you probably need help from support.
Try checking these byte offsets (assuming patch format hasn´t since last year):
layer 1: 0x10C (2 bytes)
layer 2: 0x66CC (2 bytes)
performance: 0xCBE4 (2 bytes)
EDIT 2: resolved with global reset. PHEWWWWWW
I seem to be in big trouble here.
I checked my firmware and it was 1.24 (P1 + D + E), so I updated the firmware.
The synth is really messed up now. It shows the firmware version P1 + A + F … but it seems like a voice is out, on the init patch every 5th note is silent. It won’t load most performances, and when it does, the P button stays blinking, and sometimes it blanks out of perf or patch mode altogether and shows just P1 (neither perf nor patch highlighted).
This is a disaster, I have a gig in a week 
EDIT would restoring to 1.24 help anything? Is that downloadable?
EDIT 2: global reset seemed to resolve the issue. Synth is still sharp … but playing!!
Thanks. I’ve now updated to 1.33 and have done global reset, and factory patches are still needing the global tuning. I’m assuming this is a tech support issue at this point …
FYI I checked these out, and they reflect the adjustments I’ve been making. (I even diffed a perf file where all I did was change layer pitch and indeed those addresses [10c,66cc] were the ones that changed).
What is 0xcbe4? Is there a performance-scope fine tune?
Yes but I haven’t examined the parameter specifically.
I think this parameter (PERF DETUNE) was the root of my troubles, I have 4 performances that I must have created from some global preset whose value at 0xcbe4 was 0x2900 (41 sharp, assuming little-endian) and then kept saving it off as a new performance.
So, good news/problem resolved: synth is back to flat global tuning, I reset all my layer- and perf-tunings to 0 and all is well.
NB: The latter, perf tuning, I could only do by overwriting 00 at oxcbe4 on my laptop and uploading to the synth. The manual notes that a dedicated PERF DETUNE is only available on the Super Gemini, but also that “You can achieve both functions on the Super 8 by using the TUNE control of DDS 2 in shift mode” – this seems incorrect. AFAICT shift+TUNE only affects layer detune.
1 Like