Ycros

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: How to Guide for V5: How to make your own controllers? #2490
    Ycros
    Participant
      • Topics: 1
      • Replies: 4
      • Total: 5

      Hi, I’ve been working on a panel for my Waldorf Blofeld. First you need to go to Devices and make sure your device is ticked in both input and output columns. Then select MIDI Mon from the toolbar, and when you move controls on your device, you should see a bunch of numbers coming up in the MIDI Mon window, to the right of your device name. The numbers are in base 16 (hexadecimal). For example:
      [code:2vm5dgig][MidiIn][14:39:52:422.000]: [MIDI IN][Waldorf Blofeld][b0 1f 15][/code:2vm5dgig]
      If the numbers start with a b0, then you’re dealing with CC MIDI messages. To set these to a Slider, add a Slider, then in the properties box to the right scroll down to the MIDI section. Make sure that "MIDI message type" is set to CC. Next you will need to set the "MIDI Controller number" to the [u:2vm5dgig]decimal[/u:2vm5dgig] value of the second number. In my case this is 1f, which is 31 in decimal.

      The other type of message you are likely to see are SYSEX messages, they start with f0:
      [code:2vm5dgig][MidiIn][14:45:51:6.000]: [MIDI IN][Waldorf Blofeld][f0 3e 13 00 20 00 00 08 26 f7][/code:2vm5dgig]
      These are trickier, and you’ll probably have to reference the documentation for your particular device to work out how to decode them. However, for simple cases, where the values fit within a byte (255), you can usually work out which number corresponds to the value of your control, just by moving your control around a bit (it will be the only number that’s changing in the sequence). In my case, the second last number, the 26 is the value for this particular control. To enter this into a Slider, first you need to set the "MIDI message type" to SysEx. Then at the very bottom, click Edit on "SysEx Formula". Set the length so that your entire SysEx string fits (in my case, that’s 10), then enter in all the numbers. For the number that’s your value, put in xx into the editor, this tells it that that’s where your value is located.

      These will work for simple cases, but a device manufacturer can cram whatever they want into SysEx messages, so you’ll be much better off if you take a look at the documentation for your device. There are other codes you can use in the SysEx formula editor to handle values that have been split across fields, but I don’t know them off the top of my head, but let me know and I’ll look them up in the code.

      in reply to: Handling Multiple Parts #2566
      Ycros
      Participant
        • Topics: 1
        • Replies: 4
        • Total: 5
        "atom":3kkek8t4 wrote:
        but with one instance you can still automate all parameters[/quote:3kkek8t4]

        I can, but then I have to automate all the parameters for all the parts on one track, I can’t sequence them alongside my notes as I’d like. This makes it tricky when I have multiple sequences coming in and out throughout a song. I guess I could fall-back to just using CCs, but then I lose the niceness of having a VST there.

        in reply to: Handling Multiple Parts #2563
        Ycros
        Participant
          • Topics: 1
          • Replies: 4
          • Total: 5

          Um, but ideally I’d like an instance per track in my DAW, to be able to sequence automation alongside my notes for each part.

          in reply to: Handling Multiple Parts #2561
          Ycros
          Participant
            • Topics: 1
            • Replies: 4
            • Total: 5

            I’ll probably go for a slider or something. My goal is to have multiple instances of Ctrlr, one for each part that I’m using on a track.

          Viewing 4 posts - 1 through 4 (of 4 total)
          Ctrlr