Petition for Firmware Update for E2 and E2S

[Steinberger]

Here's one feature request you can take off of the list:

the option toggle pads in jump step mode from latch to momentary

Apparently it's been there all along: https://youtu.be/15mgxYCciyI

Yep. They really need to go and fill up that owners manual. Really now.

[h.vel]

There may be some duplicates, and I may have missed a few. This list is still in progress, and I will likely eliminate over 50%, or the ones that seem too tough to implement.

Please feel free to list (below) any important changes that I may have missed.

Thanks for your work, I really apprechiate it. But honestly the polls could be much more representative. Some features are still very similar (or exactly the same), sometimes there are 2 features in just one single request, some features aren't possible to fix, some features are already possible and you forgot many requests (at least from my favourite features). Again, thanks for your work and I hope Korg will take the petition seriously. Maybe this cpuld help:

2 features in one request:
- Add song mode or pattern chaining
- Step record and direct access to step edit
- regulate send level of each trigger to Master FX or let Korg add reverb or delay into Insert FX
- Improve sample editing and add a timestretch function


Similar/same features:
- filter improvements (tracking, better high resonance, etc)
- Filter keyboard tracking
- replace the main filter and resonance with the IFX versions
- keytracking for filter

- step record and direct access to step edit
- step record and direct access to step edit

- Reduce voice stealing for muted track
- better voice management (even when no fx and no polyphony is activated, just 10-11 tracks can play simultaneously without voice stealing)

- TRANSPOSE - part/pattern
- make transposing of whole parts easier

- Allow event recorder to sync to a midi clock and allow it to loop
- the playback of Event Recordings to be able to synchronize with external sequencers

- Record with quantize off or alternate quantization
- the ability to select different quantize options

Not possible:
- Increase sample memory
- reverb for IFX

Already possible:
- glide mode and note ties
- Add the ability to copy/paste parts/bars/notes/patterns around the whole machine

Features which you forgot to metion (which has been asked by the users important, I only will list my favourites from this thread):
- pre listening before loading samples
- minimum waveform representation on the screen - for quick editing (e2s)
- ability to enter MIDI notes via an external MIDI keyboard in the Sequencer mode
- When changing a parameter the display should show if the current value isn't the original value anymore (like on the EMX/ESX)
- Record Mute on/off
- Legato pattern change mode. Be able to change a pattern before the pattern end, the new pattern is not starting from the beginning, the play position continues where the old pattern was switched. If this would be recordable, it becomes very mighty for intuitive creation of variations.
- Decay and release could be separated (for release press shift).
- Long (tied) notes dont look the same (in sequencer mode) like separate single 1/16 notes.
- Nudge notes
- MIDI receive/transmit ON/OFF per part
- parameter locks (or easier editing of controller values per step)
- per part MFX send level
- Fix Attack bug (http://www.korgforums.com/forum/phpBB2/ ... highlight=)
- Improved MIDI implementation
- Midi out 'osc' (no audio in, just uses the sequencer and cc messages)
- Copy chords and notes in step edit
- per part play speed - i think elektron gear has this, basically allow a single part to be played at half speed / quarter speed or whatever.

[hztirf]

First of all: Cade, thank you for time & patience to compile such a list. I appreciate it.

Regarding the content I support h.vel's opinion, that the list needs at least one additional iteration loop to get rid of some duplicates, false-positives, ...
Beside that, my favourite is also missing: "Midi out 'osc' (no audio in, just uses the sequencer and cc messages)"

Regarding the poll, I'd suggest to discuss the poll's setup upfront in the forums as well. Right now it is quite hard to get a comprehensive view on the first feedback. Perhaps the setup can be bettered, maybe the tool...

Anyway, keep up the good work. If you need some help, just contact me.

[SMK]

Cade, awesome job you are doing here!

Here is another feature request, I have seen in your lists, that you can remove.

Part Mute - Mute Groups
Select and hold down as many parts as you need (or can) while giving the Kaoss Pad a quick tap. Once the lights on your selected mutes change state you can tap the Kaoss Pad again to turn on or off the group. Hit any trigger pad to ungroup the mutes. Mute Groups are not saved.

[Poumtschak]

Cade, awesome job you are doing here!

+1000

Beside that, my favourite is also missing: "Midi out 'osc' (no audio in, just uses the sequencer and cc messages)"

That'd be covered by :

- MIDI receive/transmit ON/OFF per part

[gazaxian]

Make the whole OS opensource and let us make it awesome(r)

That's do it

[Cade]

Make the whole OS opensource and let us make it awesome(r)

That's do it

I think this is the best option. But Korg may not go for it.

Regarding the content I support h.vel's opinion, that the list needs at least one additional iteration loop to get rid of some duplicates, false-positives

I agree. I'm just going by what is here at the forums, and not checking to see if the suggestions are duplicates, already possible, or not possible to implement with the architecture.

It makes a great deal of sense to be clear and concise with these requests to Korg, for sure. I would love some help refining the polls. I will have 4 polls with 20 choices each.

Please post revisions and suggestions in this thread.

[thebiglebowski]

Here's my proposal:

1. We should set a deadline for posting submissions.

2. After the deadline, the feature list should be revised, edited, no double features, trimming impossible features or ridiculous features (people already explained why 8 bars or more memory is a no go - deal with it).

3. The revised and final list is posted in a new thread.

4. Each feature/bug fix on the list has its number: 1, 2, 3 and so on.

5. In this thread each user can vote for only FIVE features he needs the most, in a simple answer, for example: 5, 14, 30, 42, 50.

7. We set a deadline for the vote, after the deadline we count which features made the top 10 or so.

8. To avoid spammers and cheaters only votes from users with a X minimum amount of posts on Korg forums are counted.

PS. The Electron Octatrack has a maximum of 64 steps per pattern. And people live with that. So please, stop asking for 8 bars, lets vote for a pattern chaining option which solves way more problems than just the 4-bar limit.

[h.vel]

I think if the current polls just get edited (delete duplicates, split requests with more than 1 feature, delete requests which are impossible/already possible) it is great to start with, and there will be space for a few more feature we already mentioned in this thread. After the poll (2 weeks?) we need to compress that list and then rewrite it for Korg that it sound reasonable.

8. To avoid spammers and cheaters only votes from users with a X minimum amount of posts on Korg forums are counted.

In general this is a great idea. But what is with the users from other forums/internet which just registered here to support this petition? And until now just 30 users voted the polls. The less votes the less representative are the polls. Theoretically we need more users not less.

PS. The Electron Octatrack has a maximum of 64 steps per pattern. And people live with that. So please, stop asking for 8 bars, lets vote for a pattern chaining option which solves way more problems than just the 4-bar limit.

I agree. And please do not mix song mode and pattern chain in one single request (as it is ATM). Pattern chain could solve 8 bars AND some kind of song mode.

[thebiglebowski]

Hey h.vel,

The current poll method that is implemented on this forum unfortunately does not allow to do this properly.

For example - my top 3 requests are in one poll „set” in which I have only one vote.

So my votes are determined by the order in which the features are listed and split between 4 polls.

Confusing and morst importantly, totally unrepresentative of what I really want to vote for.

[MaartenNl]

Hi guys,

Im coming in late but i think this feature is missed in the sugestions, and i suggested it multiple times in the past on social media I guess.

My suggestion is a MFX lock which act the same as the bpm lock. This means you can fix and and change the MFX globally, so when you switch to another pattern you always have the same MFX. This means you can get a litte more freedom when you want to change the MFX in the fly, without worrying about the MFX high pass delay getting cut of when you switch to a pattern that has reverb. I think this is very easy to implement, but I'm not a coder. Why I think this is easy: the bpm is saved with each pattern, but bpm lock saves a global bpm.. So, I hope you guys like this.

[hztirf]

Cade, awesome job you are doing here!

+1000

Beside that, my favourite is also missing: "Midi out 'osc' (no audio in, just uses the sequencer and cc messages)"

That'd be covered by :

- MIDI receive/transmit ON/OFF per part

I have a different understanding: I'd like to define some parts for external sequencing, where I don't need an OSC nor manipulate the audio-in stream. Therefore, it would be great to have an "OSC" called "midi-only". This part won't use much/any audio DSP power.

The feature you mentioned (MIDI receive/transmit ON/OFF per part) would be a different option.

[jpeg]

So how are you going to get Korg to even read these requests; cos I assume this is an unofficial forum so they probably care less about what is being discussed.

[captain johnson]

the petition page needs to be created for anything to go forward.

[PurpleSpaceMan]

I have a different understanding: I'd like to define some parts for external sequencing, where I don't need an OSC nor manipulate the audio-in stream. Therefore, it would be great to have an "OSC" called "midi-only". This part won't use much/any audio DSP power.

Agreed, that's what I meant by midi 'osc'


Also- if someone was to connect a volca or other small portable gadget to audio in and allow audio thru on the electribe, the signals won't get doubled up and you can have long fx trails without being limited to 'audio in' osc note being on to let audio through.