JoeMatt

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Juno 106 incomplete? #19605
    JoeMatt
    Participant
      • Topics: 2
      • Replies: 4
      • Total: 6

      I don’t have the panel anymore. I really didn’t do much to it anyway. Just fixed the VCA inversion and grouped the range buttons. That’s easy to do by just selecting them all and setting the radio group > 0. The problem is you can turn them all off. You probably need to script it not to do that. The editor makes me want to pull my hair out so I stopped working on it since there are alternatives for the 106.

      in reply to: Juno 106 incomplete? #19593
      JoeMatt
      Participant
        • Topics: 2
        • Replies: 4
        • Total: 6

        I did some work, I don’t remember where I left off.

        The lack of presets was a bit of a deterrent of me continuing the work since I switched to using this max device.

        Tonight I’ll check it out and post it up if it’s in working order.

        in reply to: Mapping controllers to Ableton parameters (Also labels) #17431
        JoeMatt
        Participant
          • Topics: 2
          • Replies: 4
          • Total: 6

          I figured it out. If you click a control in edit mode it has a VST Index value. I’m assuming there’s a valid range that will be accepted here as setting to lower values. The maximum value seems to be 64. I tried the VST and AU wrappers and this applies to both.

          I’m not sure if this is a Live limitation, VST limitation or ctrlr bug. 64 seems like a low number so I’m suspicious it’s ctrlr in this case.

          • This reply was modified 10 years, 3 months ago by JoeMatt.
          in reply to: Bass station II parameter question #16490
          JoeMatt
          Participant
            • Topics: 2
            • Replies: 4
            • Total: 6

            I did some testing a few weeks ago on this. Going off of memory but I think I remember it as CC48 sending only the least sig. bit. cc16 can sweep the whole range but the steps will be every other. CC48 sends a low/high for the next bit to get all 256 values.

            ie; increase CC16:0 48:0 -> CC16:0 48:127 -> CC16:1 48:0 -> CC16:1 48:127 … etc

            This should be pretty easy to verify in any daw that can send CC automation to external midi outputs.

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