I saw that. It was pretty good.

Today I installed 2.2

I needed less than a minute to understand that

IT IS OCCASIONALLY SKIPPING NOTES.

You understand the point?

Use a patch with 2x unison, play a 4 note chord, again and again and again
unitl you SEE and also HEAR that not all voices are used. WTF. What does this company think?

That's weird.. I was pretty sure they fixed this problem with one of the latest updates?

Will do a new test soon.

Whats much more weird is the fact that I needed 1 minute and what all those other users actually doing all the time? Its sop easy to prvoke the error. I was too lazy in the past to upgrade. I had high hopes, but just no.

Now I installed 1.1 but it accepts only the FPGA file and the other file does't work, so that didn't help. because the firmware doesn't belong to that FPGA. (Polydesk262)

Confirmed.
One voice dropped on x2 unison playing 4 note chords.

Does this only happen with unison? Or also with 8 note chords?

Also with 8 note chords.
With 2x unison it also can happen that 7 voices are on which should never occur.

Doesn't seem to happen with 8 notes on mine.
x2 also becomes intermittent when I use an Init patch. Other patches it happens almost 100% of the time.

If I press them arpeggio it does not happen, only all hit at once. What do you mean by intermittent ?

Sometimes a voice drops, sometimes it doesn't. On some voices other than Init it happens 100% of the time.

I totally have a ghost memory of this happening and then realizing what was causing it and making it go away. I forget now the solution, sorry.

What happens if you tighten the release?

Basically, I realized that a sound was still in a "buffer" and therefore still taking a note. That might be why the init isn't causing it.

Which is still a weird implementation. Shouldnt new notes getting priority over held notes?

Downgraded to 1.1 through midi ox

after realizing that the firmware must be send to "bootloader", not "peak". Thank God. Two lfos and three envelopes are enough anyway.

I did a quick test and can confirm that it happens (about 50% of the time, or maybe even more) with a repeated 4 note chord with 2 voice unison.

However, when sending repeated 8 note chords in regular poly mode, I wasn’t able to reproduce. Seems like a bug that only happens with unison?

Unfortunately, I can't check it anymore. Back to 1.1

Uh, now Bon Jovi’s Runaway will be unobtanium in unison until they fix this!

SE-80 (beta) Demo - Polyphonic Aftertouch Expander for Novation Peak.

That's a novel idea, don't think I've ever seen something like that before. But it makes sense. Cheers for sharing (:

I thought Peak doesn’t support poly AT, do you know how it works?

Peak supports polyphonic aftertouch quite well!

Always has done.

So can we get on a mailing list for this so we know when this controller might be available?

Sounds great. And I know that it is putting controls on features already in the synth, but I have found that is a much easier way to explore and use certain features. Otherwise they can be forgotten or ignored.

I'm considering buying Momo's editor, since I just found out he added support for LFO 3 and 4 and other features of the latest update.

Anyone here using it and how happy are you with it? I think it doesn't read the current parameter values when you load a patch, right? But if you tweak a knob, the editor will reflect its movement, right? So you will be able to record that movement inside an automation lane in Ableton (instead of inside a clip's envelope)?

Any other editors to consider? I tried the one by Sigabort, which looks great, but for some reason didn't communicate correctly with my Peak inside Ableton..

Any Peak users happen to use Cubase, and possible to confirm if this is an issue for you? - I've set up Peak as a midi device (in Cubase 14), and on the Peak I have it set to transmit and receive CC/NRPN messages.

All sounds good until I hit any button on the front panel, (osc, env, mod, voice, fx etc). Suddenly Osc2 goes haywire and drops the pitch - affecting Mod Env2 Depth. I slapped a midi monitor on the channel and have figured out there is a conflict with CC 38. All the buttons at the top are sending CC 38, which according to the Peak Manual happens to also be the CC value for Osc2 Mod>Env2. I've asked the Cubase forum but they are making me sound like I'm crazy but the thing is - I own a few other DAWs and tested in Logic, Ableton, and Pro Tools – none of them are creating this conflict. Midi monitor shows nothing for CC 38.

Kinda renders a $1600 synth useless at least in that program.

Secondly, I just learned the Peak uses "CC pairs" for a few knobs, including the filter cutoff. The manual doesn't explain this but apparently something to do with the fact the filter goes from 0-255 means they had to split the controllers in half (since they all go up to 127) - here CC 29 handles half of it, and CC 61 the other half. The result, in any of my DAWs, is two automation lanes battling for control, creating lots of wonky and useless jittery automation data. WTF? Who thought this implementation would be useful in the real world? I just want to move the filter cutoff and record it...

Has anyone experienced either of these issues and if so, what can be done about it?

I don't have Peak so I can't say for sure but try recording only one of them. I believe CC 29 gives you the normal 127, the other is extra resolution on top.

I am wondering whether there is a MIDI loop involved there. If the Peak is sending CC38, it should not be coming back to itself.

I would if this were the case in normal operation, it would have been picked up by a lot of people at this stage (the peak has been around for a long time).

Yeah, that's exactly what I have thought at first too - a midi loop. I've posted around on the Cubase forum to no avail - no one seems to have any suggestions as to how I could address, filter, or block a potential loop. Still waiting to hear back from Novation support. Agree that if this were normal we would've heard about it by now, though I am hoping to find anyone who might have the same setup (Peak+Cubase) and can confirm whether or not it does this for them. At least to rule it out as potentially an issue with my exact unit or setup.

To eliminate Cubase - it may be setting up the MIDI loop, you could try a different DAW like Reaper and see if you get the same thing.

I do use Cubase but I don't have a Peak. However I found this thread in the Electra One forum that mentions a "CC38 bug" in the Summit/Peak:
https://forum.electra.one/t/preset-n...t-peak/1424/28

Same thing mentioned in the Summit thread: https://gearspace.com/board/electronic-music-instruments-and-electronic-music-production/1264645-novation-summit-post16233415.html

When you use a hardware synth as an External Instrument in Cubase, anything sent from the synth is reflected back to it via the Instrument track in Cubase (this is as intended and won't create a MIDI loop as long as Local Control is turned Off on the synth), so this is probably where the issue with CC38 pops up.

It might work if you only allow Midi In to the synth from Cubase (but no MIDI Out from the synth into Cubase) and leave Local Control turned On. That way, pressing the buttons on the synth won't send MIDI CC's to Cubase, but you will still be able to play back MIDI notes and automation data from Cubase to the synth and also program the synth via the panel. However you won't be able to write automation data into Cubase by turning the knobs on the synth that way (you'd have to draw it in or use another MIDI controller).

Wow, thanks! I currently have a ticket open with Novation and I will share that thread information with them.

I have actually investigated all setup variations, and discovered the only possible workaround is to not allow Peak as an input on the instrument track. But the reason I don't prefer this is obvious - when I perform live, I like to move knobs in real time, and none of those moves will get recorded. So what I am doing in the meantime is disabling Peak as an input when I need to dive into the panel buttons - just annoying to have to switch back and forth constantly.

What I find interesting, is that when I've tested the same setup in Logic, and monitor with an external midi monitor (snoize), CC 38 does not get included to Peak. Even though it's set for Midi To and From Peak in the same way. So in Logic I get 3 rows of data From and To Peak with every panel button - 99, 98, 6. But with Cubase, I get 4 rows - 99, 98, 6, 38. I don't understand why this is.

Figuring it's not a hardware fault on my end, it just seems odd to me there's not one other Cubase user who owns a Peak or Summit who has also run into this (I mean, according to all my internet searching). I just wanna play the synth and record CC moves while I play - not a wild setup, but according to the Cubase forum it's apparently bonkers of me to even consider lol. You'd think someone, somewhere would've mentioned this since the Peak or Summit were released years ago. But according to one of those threads you shared:
That was in 2022...