There are errors in the Shortcuts section, this needs to be corrected before more noobs end up losing their work:
An example:
WRONG
Page of track (trigs only)
REC, PAGE+COPY: Copies the trigs of the current page of the current track into memory.
REC, PAGE+CLEAR: Clears all trigs of the current page of the current.
REC, PAGE+PASTE: Pastes trigs from memory onto the current page of the current track
RIGHT
Page of track (trigs only) FUNC, PAGE+COPY: Copies the trigs of the current page of the current track into memory. FUNC, PAGE+CLEAR: Clears all trigs of the current page of the current. FUNC, PAGE+PASTE: Pastes trigs from memory onto the current page of the current track
But thatās not alll, there are more.
Basically any line where REC and COPY are used together is wrong because because REC IS COPY if you pres FUNC.
I was frantically looking through the manual to see where I managed to do these mistakes, but after a while, I understood that you meant the shortcut list in this thread I guess that what the person who wrote the list here meant with āRECā is that you have to be in a RECORDING mode to be able to use the following shortcut.
You donāt need to hold func to copy a page. Just need to be in grid recording mode, then press and hold page plus copy/paste/clear.
And indeed REC means you need to be in grid rec mode for this shortcut. Hence the ā,ā in stead of a +
Also, in case you clear or paste something you didnāt want, press the combination for the same action again to undo. Just make sure you didnāt do anything else after the initial action.
Iāve got to try this one. This prompted me to re-read the corresponding section in the manual (pattern menu).
In fact Kit data can be saved and imported (I overlooked that) but only in the current project, within a single pattern as far as I understand (probably why I didnāt find it that useful yet).
So, as Kits exist as an entity to save, what we miss a kind of āload kitā that would list kits that were saved from anywhere.
to use current option, PLocks on Tr. 1-8, but yes, itās about send levels only.
to use MIDI loop, extra MIDI splitter/router could be more useful than simple cable, anw if MIDI connection for your case will be DT OUT -> DT IN and then DT THRU -> E2, it should work, bcs THRU is just 1:1 copy of IN without any influence of settings in DT (instead of port func). But be sure to set receiving of RT messages (clock+transport) in DT to OFF, otherwise DT got RT loop shock and ends up in frozen state, restart is neccessary then.
to demand FW upgrade massively:)) bcs if seq. has 8 MIDI trx, it could have 10, or (at least) last two G+H could be optionally assignable to FXs channels, simply - internal routing instead of extra cable.
If there any wise enginner working in the electron I hope itās on their mind. I think itās not big deal to desing a small switch "device"to with 2i / 4o matrix to the midi architecture that is already there.