The Next Step in our VST Fun!

As some of you know we have a “sister site” where we talk about music, MIDI, keyboards and “things” that are not 100% Wersi related. We decided to dive into all of  the “mumbo-jumbo” part of our setup and testing of VST’s there. We made some great progress today getting a test VST config in place. A little more info on that is here. We will be following that up with a VST install on the OAX side in the coming days. For now, you can follow along with us on the “other side“.

VST_Test_Lab

 

 

9 thoughts on “The Next Step in our VST Fun!

  • 04/22/2018 at 06:21
    Permalink

    Hi Curt,

    Any news on the gentleman who was trying to midi his Ketron sd40 to his OAX, it would be
    nice to find out how he is going on.

    Cheers.
    Dave.

    Reply
    • 04/22/2018 at 11:15
      Permalink

      Dave,

      I haven’t talked with Ross is quite some time. Ross – Any news on using your Ketron with OAX?

      Reply
      • 04/22/2018 at 16:30
        Permalink

        Hi Curt,

        Thanks for the reply, I am still trying to get my head round the SD7 never mind trying
        to midi it to OAS, the Ketron in my opinion is proberbly the most underrated keyboard
        on the market and leaves others costing more in the shade, couple this to the new
        module which Reg and I have been working on and my time goes nowhere, I had more
        free time when I was working and I got paid for it!!……..oh well here we go again.

        Cheers

        Dave.

        Reply
        • 05/01/2018 at 15:48
          Permalink

          Hey Dave,

          Tell me what you might want to do assuming you were to “MIDI-up” your SD7 to OAS? I’ll take a run at a config that will get you up and running. I’ll be using OAX but the basic steps should be close.

          I totally understand your comment about time. I have no idea how I fit in working 40 hours a week with everything else. For those that haven’t retired yet – I highly recommend it! 😎

          Reply
      • 04/22/2018 at 18:17
        Permalink

        Hi David & Curt.
        No I have got no further with the Ketron SD40 set up, sort of lost interest as we never made much progress, but should really get back on to it if you get a chance Curt.
        I have had heaps of other stuff going on, we recently went to Australia for a holiday where I found a Hammond XH-200 in a music store, that I have purchased and it arrives here tomorrow so I may possibly also interface the Ketron to the Hammond at a later date.
        I am sure the Hammond will at last satisfy my desires for a decent organ sound. I have been looking for this model for well over a year and I nearly fainted when I saw one on the shop floor.
        I have also been spending a lot of time on that beautiful rendition of Intermezzi Sinfonico arrangement by Jaap van der Plas who has been very helpful with assisting me with registrations. I must say the string instrument registrations and some of the solo voices on the OAX are to die for.
        So give me a call Curt if you are interested helping with the Ketron again. Thanks a lot

        Reply
        • 04/29/2018 at 09:17
          Permalink

          Dave / Ross,

          I have a little bit of news on this topic. We contacted the US distributor for Ketron and they are going to send us an eval unit for a week. It should be here this coming Tuesday (05/01).

          I’ll start a new series of posts on the topic of connecting and using a Ketron SD40 with OAX later today or Monday. Probably be asking you folks what type of things you would like to see and how you would use the unit so we can try to get a setup in place that you can use.

          Stay tuned for more in the upcoming week!

          Reply
          • 04/30/2018 at 16:40
            Permalink

            You are a gem Curt look forward to it very much. I spent most of yesterday on the Ketron I have not used it since Xmas. it is quite a complex piece of kit with heaps of different control settings and different ways to access different settings.
            I guess the main thing would be sorting out how to load multiple individual Ketron sounds to the OAX, rather than loading multiple sounds within the Ketron.

            Thanks so much I look forward very much to your posts.

  • 08/02/2017 at 07:30
    Permalink

    You are correct Bill and as expected, there is a little latency. We are OK with that. Not really looking to use this setup to play on. It’s really about mapping controllers and setting up a patch changes from the keyboard to learn a little more about configuring whatever VST we are messing with at the time. Once we understand things on this setup then we try the same basic setup on OAX – Or at least that’s the plan! It’s just easier to sit at the desk vs. the bench of OAX to mess around for hours at a time.

    One minor detail. I don’t plan to install a DAW on the VM. Instead, I’m going to try the VSTHost program you mentioned and see how that goes. I did install KonKat on the VM yesterday since it has the ability to run stand-alone.

    That let me verify that I had MIDI and audio connections from the VM out to the Focusrite interface (with latency 🙂 ). We also reverted to a VM snapshot which removed KonKat and then switched back to the snapshot that included the KonKat config.

    Just got a fresh cup and will be taking a new snapshot of the current config before we make more noise or smoke – Whichever occurs first! 🙂

    Reply
  • 08/02/2017 at 04:54
    Permalink

    The main problem you will probably come across is latency, as by using a VM you are creating an extra software layer between the interface and VST software, which is never a good thing.

    The other problem is that not all VST or DAWs play nice with a VM, (Particularly if they require a security dongle) so it will be a case of suck it and see.

    Another option to consider, getting round the possible problems above, is to create a separate partition on your HDD/SSD and load a second copy of Windows (Dual Boot) to keep everything separate. (Just remember not to enter the Windows code (It will automatically recognise that it is running on the same computer) otherwise it will think you are trying to load on more than one computer. You can use system restore if something goes wrong (Manually create a restore point before doing anything that could cause problems) or just create an image of that partition on a separate HDD/SSD. (Windows has an Image program built in)

    You can also Dual Boot on a MAC; however it may be a little more involved as Windows will probably recognise it as a new computer, thus requiring the code.

    Have fun (Remember to wear a hat so that you don’t pull your hair out)

    Bill

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *