niels@dettenbach.de

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Mapping controllers to Ableton parameters (Also labels) #69376
    niels@dettenbach.de
    Participant
      • Topics: 2
      • Replies: 6
      • Total: 8

      Ok, so could someone explain how to solve that in steps?

      Ive seen that vstIndex is going up to 650 – so i’ve set in “edit” – “preferences” – “max exported VST params” up to 800 (from 64 what seems default), saved ctrlr state and generated new VST exports, but without any luck in getting live mapping to work.

      Or should i rewrite an vstIndex numbers to lower ones (seems “randomly” distributed between 100 and 650)?

      Or did i miss something?

      Have the same effect in an older SHRUTI ctrlr panel which works otherwise as expected for me. I’m open to contribute my working changes as updates in case i find to there…ß)

      many, many thanks for any hint,

      Niels.

      • This reply was modified 7 years, 11 months ago by niels@dettenbach.de. Reason: just to get notifications

      ((d^b))
      dettenbach
      music fab

      in reply to: DSI Tempest librarian (editor) #69362
      niels@dettenbach.de
      Participant
        • Topics: 2
        • Replies: 6
        • Total: 8

        Seems nice so far. Personally i would switch from soundtower to this program if the sequencer is implemented properl. The soundtower still has ugly bugs here – i.e. make it impossible to define multiple tie regions. But i would use it as a patch loader VST if it is ready so far. ST still has no VST variant available for the Pro2 ß)

        ((d^b))
        dettenbach
        music fab

        in reply to: DSI Tempest librarian (editor) #69351
        niels@dettenbach.de
        Participant
          • Topics: 2
          • Replies: 6
          • Total: 8

          hiho arkation,

          this sounds nice – or at least – let us hope a bit.

          The major problem yet to even develop a basic librarian is even the lack of patch management / transfer sysex or the weird implementation of their handling. I think it makes sense to await the next beta / release publication of the firmware to plan, how to get into the project. As soon as the device gives us enough MIDI functionality i’m here to invest some days of productive work.

          The Tempest is such a nice machine, but hardly lacks software functionality for studio application as for live usage. I do believe that something is further developing there when i see it…ß)

          ((d^b))
          dettenbach
          music fab

          in reply to: DSI Tempest librarian (editor) #68539
          niels@dettenbach.de
          Participant
            • Topics: 2
            • Replies: 6
            • Total: 8

            Hi goodweather,

            this sounds nice. For the Pro2 and my Evolver i still have the editor from Soundtower (which has a helpful library, but still some bugs) – but havin it in ctrlr would be cool.

            yesterday i’ve started a thread in DSI Forum (Tempest):
            http://dsiforum.com/viewtopic.php?f=24&t=7545

            to see if there is further interest and to “collect” any known MIDI implementation details (which seems not officially documented yet). Within the forum exist some of the details and i have collected a bit to from different sources.

            Based on this sources someone developed the “sound randomizer” for Tempest (open source too):
            http://forum.davesmithinstruments.com/index.php/topic,165.0.html

            from my part – i’m open to open source or a paid product (and share to income) as a result, but assume that open source makes much more sense here because of the “incomplete” MIDI stack of the Tempest.

            many thanks so far – pls feel free to comntact me.

            Niels.

            ((d^b))
            dettenbach
            music fab

            in reply to: Moog Sub37 panel #68534
            niels@dettenbach.de
            Participant
              • Topics: 2
              • Replies: 6
              • Total: 8

              Just btw: Moog publishes their own plog out VST/AU/AAX next days (which works really nice). I’m in the beta program and the progress seems really far plus the publishing was announced these days officially.

              The editor/librarian is developed hardly together with the new sub37 firmware – so it may make sense to get/use the current beta firmware when fiddling with a remote MIDI implementation.

              just my two cents…

              ((d^b))
              dettenbach
              music fab

              in reply to: just MIDI plugin host to device #68531
              niels@dettenbach.de
              Participant
                • Topics: 2
                • Replies: 6
                • Total: 8

                I think i’ve found it. The “new panel” has to get “plugin host to device” setting (default) in the right settings tab.

                Next thing i look for is how to make a drop down list with MIDI devices inside the Panel to choose the output device.

                Is there any way to:
                – build a complete, single VST/AU (i.e. with the SDKs installed)?
                – route audio?

                Will read / learn a bit further – would be nice to get single VST/AU “packages” out – i would build a (“beta”) Dave Smith Tempest editor / librarian then.

                ((d^b))
                dettenbach
                music fab

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