Muve

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: Sequential Circuits Six-Trak #10012
    Muve
    Participant
      • Topics: 4
      • Replies: 9
      • Total: 13

      Hi Sixtrakker, good to see someone can potentially get a bit of use from this. It certainly works as a MIDI controller for the Six-Trak and should be pretty simple to set up. From looking at how you have it, it looks OK, but some setting or other will not be playing ball. The simplest way to test is to use with CTRLR in standalone mode, with no other MIDI instruments connected and no other MIDI software or DAWs open. Perhaps monitor via headphones directly from the synth to make sure its not a problem with your audio routing either.

      On Six-Trak
      – Connect via both MIDI IN and OUT to your MIDI interface
      – Hold Control Record and press 1 to allow program changes
      – Hold Control Record and press 4 to allow parameter changes
      – Hold Track Record and press 1 to put in Omni Mode

      In CTRLR:
      – Open Six-Trak Editor 1.1 Panel
      – Set MIDI Input to interface and leave on ‘all channels’
      – Set MIDI Output to interface and leave on channel 1
      – Check the MIDI IN and Out devices have a smiley face on them to make sure they are connected properly.
      – Test INPUT by moving the mod wheel or changing programs on Six-Trak, this should update on the Editor.
      – Test OUTPUT by changing the CTRLR parameters while playing the synth. Make sure Panel Mode is Off (Panel Menu or Ctrl + E)

      CTRLR should now be able to control all parameters in Six-Trak. As stated in an ealier post, the Six-Trak’s lack of being able to send parameter data via MIDI, means that CTRLR can not update parameter info if changed on the Six-Trak. It’s essentially a one way street, but better than nothing!

      Atom: Yes it’s an unfortunately lack of foresight from Sequential on not sending parameter data, I didn’t realise this when I started the project. For me, it’s the one thing that stops it being able to function like a modern MIDI synth. The rest of the MIDI implementation is very good for its age. Perhaps the latest ROM chip from Wine Country addresses this drawback, mine is v9. And yes if anyone can do the LUA programming, a CTRLR patch librarian would really take this to the next level.

      For me though, I’ve decided to sell this and get another synth as it doesn’t quite fit with my workflow. Good luck to other Six-Trak users!

      in reply to: Sequential Circuits Six-Trak #9809
      Muve
      Participant
        • Topics: 4
        • Replies: 9
        • Total: 13

        For those that need to know… I think the Six-Trak is unable to send parameter data via MIDI, so the Editor will not be able to update changes. It can send/receive program changes and mod wheel data however, so they can update on the Editor if the settings are right. See page 65 of the manual.

        Also I’ve fixed the Mod wheel on the editor as it wasn’t correctly calibrated. See the panel download section for the latest version.

        in reply to: Sequential Circuits Six-Trak #9627
        Muve
        Participant
          • Topics: 4
          • Replies: 9
          • Total: 13

          Interesting thanks. Yes they are CC controllers so I’ll give it another look tonight.

          Do you have any idea of how to take on the patch library side of things?

          in reply to: Saving/Exporting #9577
          Muve
          Participant
            • Topics: 4
            • Replies: 9
            • Total: 13

            Thanks, it doesn’t seem to work though. If I enlarge either panel or canvas size then export, the background doesn’t fit as it should. It doesn’t matter though, it was only a small thing.

            in reply to: New to Ctrlr – Questions re: Ableton #9372
            Muve
            Participant
              • Topics: 4
              • Replies: 9
              • Total: 13

              You wrote it in your first post.

              – To get MIDI information in Ableton to reach the synth, I’ve selected ‘MIDI > MIDI Thru > Plugin Host > Output Device’ which works.

              No, that works to transmit MIDI from Ableton to the synth. I want to also be able to transmit MIDI from the synth to Ableton.

              I assume it isn’t possible then. I think a separate MIDI keyboard is needed.

              in reply to: New to Ctrlr – Questions re: Ableton #9366
              Muve
              Participant
                • Topics: 4
                • Replies: 9
                • Total: 13

                When in standalone mode, all ctrlr does is send and receive sysex, which controls the parameters of your synth. It has nothing whatsoever to do with any audio.

                Thanks, I recognise this, that is why I asked for it as a feature which I would find very useful.

                i won’t add code for Audio processing cause it will cause bugs.

                Then that is fair enough.

                Go into your MIDI prefs in Ableton and enable your MIDI interface as an input. If it is a multi, enable all of them
                Enable the same as outputs.Make sure you can play your synth and record MIDI notes. If you can, then open ctrlr, choose the correct MIDI port and channel from within ctrlr’s MIDI prefs and away you go.

                Unfortunately not. If you have a look at previous posts on CTRLR in Ableton, you will see that to get CTRLR to work properly as a plugin within Ableton (ie take control of the MIDI), it is recommended to turn OFF the relevant MIDI interface ports in Ableton preferences. If I leave them ON, then yes I can use the keyboard to record MIDI into Ableton, but CTRLR won’t be able to control it.

                Anyone with experience of this know if its possible to both use CTRLR as a plugin in Ableton, AND use the same keyboard to record MIDI (without changing prefs every time)?

                in reply to: Roland MKS-50 Advanced #9324
                Muve
                Participant
                  • Topics: 4
                  • Replies: 9
                  • Total: 13

                  Works great! The graphics are much improved, and I really like the envelope window, very useful! Also it’s great that the panel updates when you change patches on the machine.

                  I had trouble getting it do anything until I realised it works on midi channel 1 rather than 7 of the other programmer, but once I changed it on the synth it works perfectly. I’m still a bit confused about the MIDI channel thing in CTRLR though, so maybe you can help. If I change the MIDI channel via the MIDI menu, it doesn’t seem to affect it and it is still on MIDI channel 1, is it overruled by a setting in the panel? I figured in the original PG-300 panel that the MIDI display box on the bottom right controlled it, but now I’m a bit confused.

                  in reply to: New to Ctrlr – Questions re: Ableton #9323
                  Muve
                  Participant
                    • Topics: 4
                    • Replies: 9
                    • Total: 13

                    Thanks for the reply and info. I think it could be useful to be able to handle audio in standalone mode, in a similar way to NI’s standalone instruments. On my system I have to monitor directly from the synth headphone output if using CTRLR standalone, so would prefer to be able to monitor via my interface.

                    Any idea if there is a setting that will allow the MIDI notes from the synth to reach Ableton when using as a plugin?

                    in reply to: Roland MKS-50 Advanced #9273
                    Muve
                    Participant
                      • Topics: 4
                      • Replies: 9
                      • Total: 13

                      Hi Bomma

                      I’ve just bought an Alpha Juno 1 and have just started to get up to speed with how Ctrlr works, using the PG-300 panel. Your panel looks like a fantastic upgrade to that. Unfortunately on loading it up (Windows 7 64), it gives me a white screen with a few messages in red saying invalid resource, see pic. I’m using the latest build 1400. Any ideas on what I need to do to see the panel properly?

                      Thanks
                      Muve

                      Attachments:
                      You must be logged in to view attached files.
                    Viewing 9 posts - 1 through 9 (of 9 total)
                    Ctrlr