Dropped the VST3 and all is well! Hopefully the first update will be here soon.

I ordered the Boxed version. Hopefully they will come with the first update patch on them.

After an easy install, had issues with the standalone version - got a fix for that after I had found the solution on IK's Forum.
However, ST3/VST3 plug-in does not work (as many have stated here), but VST2 does.  It's like there's no "note off" messages being sent around when using an external kybd (akin to keeping the pedal down all the time).  But you cannot play the same note after the first time it "jams".  Weird.
As someone pointed out, it seems to work okay in Studio One (or whatever), so I'm wondering if it's not a Cake VST3 issue ...
Anyway, have opened a ticket with IKMM.

SONARtist
After an easy install, had issues with the standalone version - got a fix for that after I had found the solution on IK's Forum.

Could you post a link here to the fix page you mention on the IKMforum?  I want to make sure that I have it correct.  The only thing I saw over at the IKM forum was to use the asio4all drivers first.  A link to the fix would be helpful.  Thanks.

.

I wonder if Noel Borthwick would care to chime in on whether there could be something untoward about Sonar's VST3 implementation, given that other DAWs are happy with SampleTank3 in its VST3 form? I'm also curious about Glyn Barnes' post above re. issue with other VST3 plugins.

@cecilius2
 

cecelius2

SONARtist
After an easy install, had issues with the standalone version - got a fix for that after I had found the solution on IK's Forum.

Could you post a link here to the fix page you mention on the IKMforum?  I want to make sure that I have it correct.  The only thing I saw over at the IKM forum was to use the asio4all drivers first.  A link to the fix would be helpful.  Thanks.

Disclaimer: Before anyone acts on the following, please note that I do not take any responsibility for any actions you take in trying this fix, that may lead to the incorrect working of SONAR, SampleTank, etc.  PLEASE MAKE A BACKUP OF YOUR "SampleTank 3.settings" FILE BEFOREHAND - just in case.
 
Basically, I had issues with the ST3 standalone crashing when opening the app.  My ASIO system (SSL Soundscape MADIXtreme) was not recognised.  Although I saw the ASIO4ALL solution, I did not use this, but it seems to have worked for some ...
 
This is the answer I got directly from IK, and which was posted beforehand on the IK Forum (Thanks to Robert Stallard) :-
==============================
- 1 - Navigate to and open the "SampleTank 3.settings" file in a text editor:

    C:\Users\Username\AppData\Roaming\IK Multimedia\SampleTank 3\SampleTank 3.settings

    To open this file, right-click on it and select "Open with..." from the context menu and choose your text editor.


- 2 - Edit the audio device settings as follows:

    The file contains the following XML code (or something similar):

    Code: Select all
        <?xml version="1.0" encoding="UTF-8"?>

        <PROPERTIES>
          <VALUE name="audioDeviceState">
            <DEVICESETUP deviceType="ASIO" audioOutputDeviceName="" audioInputDeviceName="">
              <MIDIINPUT name="MIDI (Lynx L22)"/>
            </DEVICESETUP>
          </VALUE>
          <VALUE name="midiIsAny" val="0"/>
        </PROPERTIES>

    Note that the settings for "audioOutputDeviceName" and "audioInputDeviceName" are empty. Enter the name for your corresponding ASIO audio interface within the quotes following each setting, as follows (in my case, my audio device is "LYNX L22):

   
        <?xml version="1.0" encoding="UTF-8"?>

        <PROPERTIES>
          <VALUE name="audioDeviceState">
            <DEVICESETUP deviceType="ASIO" audioOutputDeviceName="Lynx L22" audioInputDeviceName="Lynx L22">
              <MIDIINPUT name="MIDI (Lynx L22)"/>
            </DEVICESETUP>
          </VALUE>
          <VALUE name="midiIsAny" val="0"/>
        </PROPERTIES>

To find your audio device name, open your ASIO driver/audio interface configuration settings in Windows Control Panel. Alternatively, look in your DAW software audio device ASIO settings.


- 3 - Save the file and run ST3 standalone.

    If it opens, go into the Audio/MIDI settings in ST3 and configure as you wish. ST3 started working for me after this. After exiting ST3, the "SampleTank 3.settings" file looks something like this:

    Code: Select all
        <?xml version="1.0" encoding="UTF-8"?>

        <PROPERTIES>
          <VALUE name="audioDeviceState">
            <DEVICESETUP deviceType="ASIO" audioOutputDeviceName="Lynx L22" audioInputDeviceName="Lynx L22"
                         audioDeviceRate="48000" audioDeviceOutChans="11">
              <MIDIINPUT name="MIDI (Lynx L22)"/>
            </DEVICESETUP>
          </VALUE>
          <VALUE name="midiIsAny" val="0"/>
        </PROPERTIES>

Senior Technical Support - IK Multimedia
==============================
 
Edits: Backslashes added to folder address at beginning ...

Skyline_UK
I wonder if Noel Borthwick would care to chime in on whether there could be something untoward about Sonar's VST3 implementation, given that other DAWs are happy with SampleTank3 in its VST3 form? I'm also curious about Glyn Barnes' post above re. issue with other VST3 plugins.

My issues were with several synths in the Arturia V collection. The VST2 works fine but the VST3 versions caused crashes. The issue was reported to Cakewalk at the time but I can't find the ticket number. I was not too worried about it once I found a solution because I don't think there are any VST3 specific features in those instruments. I reported mainly for the "greater good".
 
I do not have any other VST3 VSTis but I do have a couple of effects that seem to work OK, but I must admit to using the VST2 versions most of the time.
 
I seem to recall other VST3 issues being reported in these forums.

Here is more on the Arturia VST3 issue http://forum.cakewalk.com/Potential-work-around-for-those-having-trouble-with-Arturia-Synths-m3050021.aspx
 
http://forum.cakewalk.com/Bass-station-and-Arturia-VST-not-working-in-Sonar-X3e-m3035009.aspx
 
Some problems with UHE VST3 synths also cam up in the search.

my speculation is that the synths with issues are trying to utilise some as-yet-unimplemented-in-sonar part of the vst3 spec, whereas the other hosts have implemented that, and that sonar's vst3 implementation will continue, and that with some future sonar update these synths will work, but that's just speculation