khake

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Tetra Ctrlr #1982
    khake
    Participant
      • Topics: 0
      • Replies: 3
      • Total: 3

      Thanks a lot for the update, Wren. "Good" to know that the problem is with the tetra (recall). That is to say, it sucks – but it helps a lot when trying to figure out how the vst from soundtower or ctrlr will work with the tetra within a daw.

      Khake

      in reply to: Tetra Ctrlr #1980
      khake
      Participant
        • Topics: 0
        • Replies: 3
        • Total: 3

        Just thought I’d update a bit on the Soundtower vst.

        I updated my tetra to os 1.5 and voice 1.2 and got the vst working.
        I’m assuming the update will improve performance for the ctrlr-panel as well – will test and update asap.

        Some points about the soundtower-vst (I’ve only used the demo, so bear that in mind). I use FL studio as my DAW.

        * Automation and parameter tweaking in real-time works for the parameters available in the demo version. Just couple of parameters are tweakable in the demo version though, but it works.

        * As far as I can see, FL studio is NOT able to recall which patch I was using when I saved the projects in FL. If i save a projects using a patch and switch to a different patch and re-open my project the original/saved patch is not loaded. Bummer.

        * Also, if i change some parameter in a pre-defined tetra-patch, like OSC1-frequency and then save the project, switch to a different patch and back again (restore default parameter settings for the patch) and then open the project again, the changes I made to osc1-freq are NOT loaded. Looks like FL is not able to save the parameter-settings for the vst.

        Both points above may be a demo limitation. Either way, bummer.

        * Another point, or annoyance, is the "help"-file that soundtower provides. Check this out, from the "manual":

        [quote:34htrdsm]"Click the PREFS button at the top of the Editor window. This opens a window to allow you control how parameter changes to and from the Tetra PlugSE communicates with your host DAW and the Tetra. A Default Settings is provided in the lower left corner and a Cancel and OK button in the
        lower right corner. "Host" refers to the workstation that his running the plug in (Cubase, Nuendo, Digital Performer,Ableton etc.) You may have to experiment with the
        various options to get the results you require." [/quote:34htrdsm]

        Now, there are 9 different options to toggle (they are not mutually exclusive) – which, according to my math, is something like 362,880 possible configurations.
        Yeah. I guess I "may have to experiment" a "bit", yeah. That said, I left everything on, and was able to send parameter tweaks and automation to my tetra.

        * Apparently, based on what I’ve read on other forums, there are sync-isses for LFO (DAW to Tetra via vst). Also, if you close the vst-window, apparently no midi is sent to the tetra.

        Given these issues, I am not going to buy the vst any time soon.

        I’ll give wrens panel a go using ctrlr and see how that works out now that I’ve updated my tetra.

        Again, I hope you don’t mind me posting this here, Atom. I just thought other tetra-users might be interested in what the soundtower-plug can do and not do. As you can see, it seems to be buggy as hell, and the ctrlr-panel seems to be a much better option.

        Khake

        in reply to: Tetra Ctrlr #1979
        khake
        Participant
          • Topics: 0
          • Replies: 3
          • Total: 3

          "Sound tower are releasing a VST but god knows how much it will cost."

          It’s been released. If I remember correctly, it was $50. Demo is available, with some limitations.

          Tested it, and it kinda works, but I do have some issues;

          I can send midi-notes from the plugin and get audio out of the tetra. Also, for combos, changes made to tempo in my host (FL Studio) will alter the tempo of the combo being played. Thus, some midi is going back and forth. If I tweak a potmeter on the tetra itself, like the filter cutoff, I can see the equivalent pot in the plugin moving. However, I am not able to send that kind of parameter-info to my tetra. That is, when tweaking the pot in the plug nothing happens.

          As far as I can see, my tetra is set to receive all midi-messages, so I am not sure why this wont work. I’ve had similar problems when trying the standalone (outdated) tetra-controller that atom made (thanks for all your work, Atom!!). It might be an error on my part, i.e. some global paramter being set wrong or something like that. Hence, I am posting here, since I guess a lot of you have tested various set-ups and so on with the tetra. Hope you don’t mind, Atom (?)

          My setup:
          Tetra <– USB –> Computer
          Firebox soundcard midi out <– –> Tetra midi in (I did this so that I could use the midi out on the soundcard to send midi msgs to tetra, while at the same time being able to use my midi keyboard to play other vst’s in my host.)

          Any help or suggestions is very much appreciated, thanks!

          Khake

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