Korg ER1 MK2 Current Pattern Problem

Home Forums General Using Ctrlr Korg ER1 MK2 Current Pattern Problem

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #69887
    Refrochia
    Participant
      • Topics: 6
      • Replies: 9
      • Total: 15

      Hi Again

      I know this is slightly off topic so if any mods want to delete the post thats fine but I’m posting in the hope someone can help?

      Trying to create a panel for the Korg Electribe ER1 MK2 and having problems retrieving the current pattern. From the device its only possible to do an all pattern dump and not just the selected pattern. This obviously takes ages and results in 256 being transferred when I only want the current pattern (the manual doesnt state whether the current pattern is from the edit buffer or the saved version in memory but I’m not fussed about that).

      I’ve determined from the Midi implementation doc that the correct sysex to request the curent pattern is: F0 42 39 51 10 F7 When I send this in Midi Ox or CTRLR I get a response of CC data which is not what I’m expecting and there doesnt look to be enough data transferred to represent a pattern (maybe im wrong and this is correct and I’m misintrepreting the midi implementation doc?). I was expecting a sysex response. To request an all pattern dump the sysex is F0 42 39 51 1C F7 which results in a sysex response – just like when manually dumping all patterns from the device.

      I’ve also posted this on the Korg forum but thought I’d try here as well given how common these machines are.

      Again, if this post shouldnt have been made here then feel free to delete.

      Here’s the manual and midi implementation doc:

      http://www.korg.com/us/support/download/product/1/101/

      Thanks
      R

      #69890
      Possemo
      Participant
        • Topics: 14
        • Replies: 638
        • Total: 652
        • ★★★

        When I look into the documentation:

          MIDI EXCLUSIVE FORMAT (R:Receive, T:Transmit)

          (1) CURRENT PATTERN DATA DUMP REQUEST R
          +—————-+————————————————–+
          | Byte | Description |
          +—————-+————————————————–+
          | F0,42,3c,51 | EXCLUSIVE HEADER |
          | 0001 0000 (10) | CURRENT PATTERN DATA DUMP REQUEST 10H |
          | 1111 0111 (F7) | EOX |
          +—————-+————————————————–+

          When this message is received, the CURRENT PATTERN DATA DUMP(Function:40h)
          message will be transmitted.

        So the message should look like this: F0 42 3c 51 10 F7

        #69896
        Refrochia
        Participant
          • Topics: 6
          • Replies: 9
          • Total: 15

          Thats what I thought at first but wasnt getting any response when sending that. Then I realised that 3C should actually be 39 because c is the midi channel and the ER is set to channel 10.

          When sending F0 42 39 51 10 F7 from the sysex window in Ox, all that shows in the monitor input window is the following:

          0003DA80 16 — 89 11 11 10 F 0 Note Off
          0003DA8E 16 — 89 00 00 10 C -1 Note Off
          0003DA9E 16 — 89 7F 7F 10 G 9 Note Off
          0003DAAA 16 — 89 7F 7F 10 G 9 Note Off
          0003DABA 16 — 89 7F 7F 10 G 9 Note Off
          0003DAC8 16 — 89 7F 7F 10 G 9 Note Off
          0003DAD6 16 — 89 7F 7F 10 G 9 Note Off
          0003DAE4 16 — 89 7F 7F 10 G 9 Note Off
          0003DAF4 16 — 89 7F 00 10 G 9 Note Off
          0003DB02 16 — 89 20 7F 10 G# 1 Note Off
          0003DB10 16 — 89 7F 7F 10 G 9 Note Off
          0003DB1E 16 — 89 7F 7F 10 G 9 Note Off
          0003DB2C 16 — 89 7F 7F 10 G 9 Note Off
          0003DB3C 16 — 89 7F 7F 10 G 9 Note Off
          0003DB48 16 — 89 7F 7F 10 G 9 Note Off
          0003DB56 16 — 89 7F 7F 10 G 9 Note Off
          0003DB66 16 — 89 7F 7F 10 G 9 Note Off
          0003DB74 16 — 89 7F 7F 10 G 9 Note Off
          0003DB82 16 — 89 7F 7F 10 G 9 Note Off
          0003DB90 16 — 89 7F 7F 10 G 9 Note Off
          0003DB9E 16 — 89 00 00 10 C -1 Note Off
          0003DBAC 16 — 89 00 7F 10 C -1 Note Off
          0003DBB6 16 — 89 00 00 10 C -1 Note Off

          Dont get anything in the sysex display window. Yet when requesting the all pattern dump from within the sysex window, the dump is displayed in the display window (as well as the monitor input window).

          I’m beginning to think this is a bug in the ER and it cant actually send the current pattern info.

          • This reply was modified 7 years, 7 months ago by Refrochia.
          #69902
          Possemo
          Participant
            • Topics: 14
            • Replies: 638
            • Total: 652
            • ★★★

            Yes. Then the Midiimplementation is probably buggy. Is there no other editor available for the ER1? It can be helpful when you see what other editor-softwares are doing.

            #69905
            Refrochia
            Participant
              • Topics: 6
              • Replies: 9
              • Total: 15

              Cant seem to find any. Soundquest claim to have an editor as part of Midiquest but going by the majority of the internet (it seems!) they make a lot of claims that arent necessarily true!

              Despite this and the midi clock issue, the midi implementation seems fairly sound although it would be better if you could address the individual seqeuncer steps via sysex like you can with the Evolver.

              #69906
              Possemo
              Participant
                • Topics: 14
                • Replies: 638
                • Total: 652
                • ★★★

                I just quickly checked Midiquest. There is an editor for the ER-1. The pattern-request message is exactly the same:

                F0 42 30 51 10 F7

                Soundquest probably coded it blindly according to the sysex-reference chart. They did it on many of their lousy editors.

                • This reply was modified 7 years, 7 months ago by Possemo.
                #69908
                Refrochia
                Participant
                  • Topics: 6
                  • Replies: 9
                  • Total: 15

                  Figured it out!!! I noticed that I got a discrepency in the number of bytes received when doing another all pattern dump and looking further, the received message wasnt terminated with F7 and in the OX input monitor at the end of the sysex is a load of CC data – just like when doing a current pattern dump (minus the sysex).

                  Connected up via my Elektron TM-1 and hey presto. I can dump the current pattern no problem. An all pattern dump sysex message terminates properly as well and gives consistent number of tranferred bytes. So it looks like the Midex 8 is screwing with the sysex…..Or so I thought!

                  I’ve dealt with sysex before via the midex 8 and not had any problems but I wasnt working with the ER1 on those occassions. I have a SonicCore Scope system so routed the Midi out from the ER into that, filtered out the time clock and then back out of scope and into the midex 8. Works fine now. The Midex was obviously getting confused by all the timing traffic and then unable to deal with the sysex dump properly.

                  What a voyage of discovery lol. Now if only I could switch off the timing info!!!

                  Really appreciate your help Possemo!

                Viewing 7 posts - 1 through 7 (of 7 total)
                • The forum ‘Using Ctrlr’ is closed to new topics and replies.
                There is currently 0 users and 109 guests online
                No users are currently active
                Forum Statistics
                Threads: 2,495, Posts: 17,374, Members: 77,605
                Most users ever online was 12 on January 22, 2019 3:47 pm
                Ctrlr