Is the latest SG firmware stable?

UDO Audio Gear Super Gemini
1

Always terrified to update, but I’ve yet again had unexplainable shit happen with this expensive lemon. LMK thanks!

2 Likes
2

Yep, all good here, no issues that I’ve noticed.

3

I installed 1.32. while back and now I see there is a 1.33 but it has the same readme (and has eliminated 1.32 from its history)

what gives? Is 1.32 a safe release to be running?

4

So the only addition in 1.33 from 1.32 is the updated framework?

5

From the Readme.txt

-----------------v1.33------------------

• Framework for 20-voice upgrade for Super 8 Model

  • A 20-voice upgrade kit will be offerred for Super 8 owners.
  • 10 LED Flourish will display at power up indicating Super 8 Plus
    upgrade installed

• DYNAMICS control (velocity) now affects VCA fixed envelopes

• Voice Panning (ping-pong) in non-binaural mode now predictable
in DUAL mode

Try it :

  • Setup a Dual Performance
  • Turn BINAURAL off for both layers
  • Set LR PHASE to maximum for both layers
  • Voice panning ping pong should be matched for both layers

• Reduced MIDI Clock to Audio out delay from 2,5ms<t<5,0ms down to
0,1ms<t<2,5ms.

  • Note that independent of the Super 8/Gemini, Audio to MIDI
    synchronisation is not guaranteed from most DAW setups without
    configuration. Some setup adjustment in host may be required.

Fixed / Improved

• Envelope keyboard tracking in non-binaural mode bugfix

• Improved Delay buffer clearing when changing patch/performance
and changing layer modes (SINGLE, DUAL, SPLIT) or changing layer
when in SINGLE mode

• Max ENV time settings saturation bugfix

• VCF Bender and Aftertouch to VCF using left hand control section
bugfix

• ENV1 Invert LED always on bugfix

• Super 8 USB Enumeration to “SUPER 8” (was “SUPER GEMINI”)

  • Drive may need to be manually renamed from “Gemini” to
    “Super 8” (or your choosing!)

Known Issues

• Modulation of LFO1 rate in non-binaural mode fix (1.26) was
reverted due to some user finding audio artefacts using the delay

6

deleting 1.32 from the readme does not exactly inspire confidence.

7

Sometimes interim release numbers are internal versions only, often where more bugs have been found and eliminated prior to public release so it’s not unusual to see gaps in public release numbering.

8

I think what you are missing is that 1.32 was publicly released! Hence it is on my synth. And there was never any notification of it being ‘withdrawn’.

All this is small beer, but yeah its not confidence inspiring.

1 Like
9

Fair enough. Perhaps there was something in that release that was causing major issues so they want to remove the chance of more people installing it.

10

I think the way the firmwares are released makes all the former ones unavailable online. If you did not keep the former ones yourself, there are gone with the last release.

I can totally understand a urgent patch of something small (hence 1.32 → 1.33), but I don’t get why suppress the 1.32 from the readme.