Novation Summit

Discussion in 'Samplers, Synthesizers' started by roustany, Feb 10, 2025.

  1. MWAX

    MWAX Newbie

    Joined:
    Sep 16, 2025
    Messages:
    5
    Likes Received:
    0
    I'm more concerned about whether I should return the device to the store or if this is typical for this device. It looks like a firmware issue, but what if not?
    That's why I'm looking for someone who has it and can confirm or deny this behavior. I don't want to give it away because it's a great synthesizer, but I don't want to be left with a broken device.
    I ran some more tests, and it seems the problem occurs with patches that have a delay level set (if the patch I'm changing to has that value set). The higher the delay level, the more distortion there is for the first note.

    It's also strange that if I hold down a key while changing patches, the problem doesn't occur.

    Novation support, of course, silence and no response.
    The problem is audible for many presets, and I have provided examples above.
     
  2. MarkSlater

    MarkSlater Producer

    Joined:
    May 16, 2012
    Messages:
    208
    Likes Received:
    93
    It is weird that Novation support didn't reply to you. I have a lot of gear from them and Focusrite and over the years, I needed support from them, many times. I found them to be the fastest and most helpful support out there, along with Audient. They even offered an engineer to call me so to fix the issue fast. Maybe they changed that in the last 3-4 years, since last needed help from them? :unsure:
     
  3. MWAX

    MWAX Newbie

    Joined:
    Sep 16, 2025
    Messages:
    5
    Likes Received:
    0
    How did You contact them? Now is only one help site with request ticket and even I cannot see this thicket anywhere. There is only mail with confirmation of submit and nothing else from 5 days.
     
  4. MarkSlater

    MarkSlater Producer

    Joined:
    May 16, 2012
    Messages:
    208
    Likes Received:
    93
    Through the ticket support. So maybe, indeed, they ruined their support, post-covid, like many other companies. Because, to me, they always replied within 1-3 hours, which was amazing. Five days is a lot, but not the worst. Native Instruments replied to me 22 days later. Phil Speiser, I sent multiple tickets for the same issue, for about one week, something like 2-3 months ago. I still got no answer. Propellerheads (Reason Studios) replied after 6 months, asking me if I still have the issue, appologising for the late reply, etc

    For me, your issue sounds like a RAM overloud problem. I think I had something similar with a different synth in the past. Probably with Blofeld.
     
  5. E.C.R

    E.C.R Platinum Record

    Joined:
    Aug 28, 2014
    Messages:
    379
    Likes Received:
    187
    the summit is a great bread and butter synth, in that you can get great sounds , it is a very good synth, althought i rate my OB-8 to be the best and also the super 6? amazing sound, but for great basses, pads, synth sounds etc get the summit
     
  6. PulseWave

    PulseWave Audiosexual

    Joined:
    May 4, 2025
    Messages:
    3,042
    Likes Received:
    1,663
    Should You Return It?
    • If It's a Dealbreaker: Yes, return it while you can. The Summit shines in seamless layering/splitting, so if patch changes are core to your flow (e.g., live sets), this could sour the experience. Stores like Sweetwater or Guitar Center often have lenient policies, and you could test a demo unit in-store to see if others exhibit it (though stock might vary).
    • If You Can Work Around It: Keep it—it's probably not worsening, and the synth's strengths (bi-timbral power, wavetable depth, analog warmth) outweigh this for most. Firmware hasn't addressed it yet, but Novation's history shows they iterate (e.g., slew improvements in v2.1 for delay modulation). You're not "stuck with broken"—just a finicky digital effect.
    I understand your frustration—it's a killer synth when it's firing on all cylinders, but that kind of glitch can make it feel unreliable, especially during live switching or performance. Based on your detailed description (distortion on the first note after patch changes, tied specifically to delay level in the target patch, worse with higher settings, and avoided by holding a key), this does point strongly to a firmware or processing artifact rather than outright hardware failure. The fact that it doesn't happen mid-note (with a key held) suggests the issue kicks in during the idle-to-attack transition, possibly from how the delay buffer initializes or clears on patch load.

    From digging into user reports and forums, this isn't an isolated incident—it's been flagged by a handful of Summit owners as a recurring quirk, often linked to the onboard delay effect's handling during rapid patch switches. It's not universal (many users don't notice it in their workflows), but it's typical enough that it's not a "broken" unit warranting a return unless it's severe enough to disrupt your use case. Here's a breakdown:

    Why This Happens (and Why It's Likely Not Hardware)
    • Delay Buffer Glitch: The Summit's digital effects chain (including delay) uses a buffer that can produce brief artifacts when loading a new patch, especially if the delay is active/high-feedback. This is exacerbated on the first note because the voice allocation and effect routing reset abruptly. Higher delay levels amplify it since more "echo" material is in the buffer, leading to that distorted smear.
    • Key-Hold Workaround Insight: Holding a key keeps the voice active, so the patch change overlaps with ongoing audio processing—essentially bypassing the cold start of the delay init. This is a common symptom in hybrid synths like the Summit (digital osc/FX + analog filter/VCA stages).
    • Not Typical for All Patches: As you noted, it's patch-specific (delay-enabled ones), which rules out broad hardware distortion like a failing op-amp or VCA. Analog distortion stages (pre/post-filter) would affect everything consistently.
    User reports confirm this behavior:

    • On KVR Audio forums, multiple threads describe identical first-note distortion on patch changes with delay-heavy patches, with no resolution beyond workarounds. One user called it "annoying but livable" and stuck with their unit.
    • Gearspace discussions mention similar "glitchy artifacts" in delay time/routing during switches, with Novation acknowledging it as a firmware quirk (no fix in updates up to v2.1).
    • Reddit's r/synthesizers and r/Novation have scattered posts on Peak/Summit FX glitches (e.g., effects not applying cleanly on load), but Summit-specific ones align with your delay observation.
    No widespread hardware defect reports (e.g., no recalls or batch issues like the 2019 encoder problem), and searches on X/Twitter turned up zero recent complaints matching this—suggesting it's not a hot-button failure mode.

    Should You Return It?
    • If It's a Dealbreaker: Yes, return it while you can. The Summit shines in seamless layering/splitting, so if patch changes are core to your flow (e.g., live sets), this could sour the experience. Stores like Sweetwater or Guitar Center often have lenient policies, and you could test a demo unit in-store to see if others exhibit it (though stock might vary).
    • If You Can Work Around It: Keep it—it's probably not worsening, and the synth's strengths (bi-timbral power, wavetable depth, analog warmth) outweigh this for most. Firmware hasn't addressed it yet, but Novation's history shows they iterate (e.g., slew improvements in v2.1 for delay modulation). You're not "stuck with broken"—just a finicky digital effect.
    Quick Fixes and Workarounds
    While waiting on support (yeah, their response times suck—try the ticket escalation or Focusrite forum proxies), here's what users recommend:

    1. Patchcue Mode: Enable this in Settings > Misc (hold Shift + Patch button). It pre-loads the next patch silently, reducing switch artifacts by ~80% for many. Test on delay-heavy presets.
    2. Lower Delay on Load: In Components (free app), edit affected patches to drop delay level to 0 on init, then automate a ramp-up via mod matrix (e.g., to aftertouch or a dummy LFO). This masks the glitch.
    3. Voice Management: Set Voice Limit lower (e.g., 8-12 voices) in the menu—frees processing headroom during changes. Also, enable "Legato" for sustained patches to mimic your key-hold trick.
    4. External Routing: If gigging, send Summit audio through a DAW/pedal with its own delay (bypass onboard). Or use MIDI program changes with a slight delay (5-10ms) from your controller to soften the transition.
    5. Firmware Check: Double-confirm you're on v2.1 (latest as of now). Download via Components if not—includes delay tweaks that help some.
    Next Steps for Confirmation/Support
    • Test Another Unit: Hit up a local shop (e.g., via Google Places for "synth stores near me") and replicate your test on a floor model. If it's there too, it's typical.
    • Escalate to Novation: Repost your KVR thread details to their Focusrite Audio Engineering forum (they handle Novation support there—faster than tickets). Include audio clips; users say that gets traction.
    • Community Check: Drop your examples on r/synthesizers or the Novation Discord—folks with Summits often share patch files to verify.
    Hang in there; the Summit's a beast once dialed in. If you share more (e.g., your firmware version or a clip link), I can refine this further. What's your main use—studio, stage?
     
  7. quadcore64

    quadcore64 Audiosexual

    Joined:
    Jun 13, 2011
    Messages:
    1,959
    Likes Received:
    1,089
    1. Have you tried a factory reset on the synth?
    2. Are you still within the buyer's return period and, have you talked to the store about a refund or a different unit?
     
  8. MWAX

    MWAX Newbie

    Joined:
    Sep 16, 2025
    Messages:
    5
    Likes Received:
    0
    1. There is no such option in Summit (only reinstall current FW without FMPGA). Tried calibrating option few times instead.
    2. Yes and that is the problem (one day left) and I don't know if I return and buy another the problem will be the same. If this is
    problem with this particular piece of equipment that would be good option but if it is FW or common feature of this synth replacing it's not worth the effort but only wasted time.
    They will give me options after requesting return so I don't know for now what options are.

    So my choices are:
    1. Leave as it and bother with this problem and regret if this will be hardware copy problem
    2. Leave as it and waiting for eventually fix if this is common behavior
    3. Return and buy another and have the same problem (if this just is like that)
    4. Return and buy another copy and have no problem if this behavior was revelat to this specific broken copy

    First is awful option, second I can live with it but I don't know that - maybe it is 1...
    4 is the best but I don't know that, maybe it is 3...

    It will be very good to know if this is specific for my copy... or common for this model...
     
  9. MarkSlater

    MarkSlater Producer

    Joined:
    May 16, 2012
    Messages:
    208
    Likes Received:
    93
    • Interesting Interesting x 1
    • Useful Useful x 1
    • List
  10. PulseWave

    PulseWave Audiosexual

    Joined:
    May 4, 2025
    Messages:
    3,042
    Likes Received:
    1,663
    I've had three hardware devices (Virus TI, Blofeld, and MiniNova) return with defects, and each one was repaired.
    Two had memory issues, and one had a broken button.

    Usually, they provide a shipping label so you don't incur any costs, and you wait about two weeks. If the problem persists, at least you tried. You might even get a new 2-3 year warranty, depending on your country. Our retailer has a workshop, so a technician from the manufacturer comes to the workshop, examines the device, assesses the problem, and either repairs it or provides a new one.

    So, to get back to your question: You've listed all the possibilities. I recommend sending the device in for repair/return. You might get the same device back, or a new one, possibly with the same problem, or with a chance, a brand new, flawless device. For software errors, they usually just install the latest software.
     
  11. MWAX

    MWAX Newbie

    Joined:
    Sep 16, 2025
    Messages:
    5
    Likes Received:
    0
    Yes, I know - I will send it back. Thank You for Your support. I have just wondered if this is more common problem with Summit.
     
  12. Lois Lane

    Lois Lane Audiosexual

    Joined:
    Jan 16, 2019
    Messages:
    5,913
    Likes Received:
    5,936
    Location:
    Somewhere Over The Rainbow
    Good idea about sending it back since the lack of Novation support hasn't helped. I appreciate you posted about your issue as I was thinking about turning over some gear and buying a Summit myself. Now I'm having second thoughts.
     
Loading...
Similar Threads - Novation Summit Forum Date
Novation 61 SL Mk3 or Novation 61 Launchkey Mk4? Instruments Today at 9:37 AM
Checking Out: Sonic Atlas by Pitch Innovations Software Reviews and Tutorials Saturday at 4:27 PM
Novation Play - Free for Launchkey MK4 Owners (but should you?) Software Reviews and Tutorials Oct 2, 2025
Novation Launchpad pro mk3 vs. Push 2 for Bitwig Soundgear Sep 30, 2025
KLEVGR. Degrader Free for Focusrite|Novation user Software News Aug 13, 2025
Loading...