SampleTank 4 on the way

[Peter - IK Multimedia]

Peter, I won't mention the name of the support technician I worked with, but can you inform his manager/supervisor that I am very happy with the service received? Ticket number was #228056

Thanks! I've let our Support Manager know.

[Peter - IK Multimedia]

Peter,

Can you just clarify the order of installation? I have ST4 Standard but haven't installed anything yet awaiting bug fixes (but already have ST3 MAX installed from pre ST4 days).

Is the following correct (I am using filenames minus .zip below to avoid ambiguity)? :

• Run SampleTank_4_0_0 (or can I just go to step 2?)

• Run SampleTank_4_0_2

• Run SampleTank_4_Instruments_Installer

• Run all of the separate instrument installers (I make it 29 files here for the ST4 std)

• Run SampleTank_4_Sound_Library_Update_1_1

I am running the Windows version on Windows 10.

Thanks

If you haven't installed anything yet, just install 4.0.2 first, then the sound libraries, then the updaters. Advice about installing the updaters first was for those who have already installed a previous version (and it wouldn't cause the apocalypse if they didn't anyway ).

[Peter - IK Multimedia]

With regard to Studio One only seeing the VST3, that's by design. The developers have explained:

This is normal. There’s a setting in the VST library code, which is enabled by default in our code, that basically says “if a VST3 version is available, use that”. Studio One (and possibly Cubase as well) use that setting, so if you have both VST2 and VST3, the host will hide the VST2 version.

On another note, please consider that VST2 is now completely deprecated. Steinberg stopped supporting it a few months ago and they strongly suggest using VST3 from now on.

[Saukar30]

I'm seeing multis here. ST4.0.2.

ST4, ST3, Syntronik, & Miro CE 2.

Cool. Thanks, Zzz00m

[rrichard63]

With regard to Studio One only seeing the VST3, that's by design. The developers have explained:

This is normal. There’s a setting in the VST library code, which is enabled by default in our code, that basically says “if a VST3 version is available, use that”. Studio One (and possibly Cubase as well) use that setting, so if you have both VST2 and VST3, the host will hide the VST2 version.

On another note, please consider that VST2 is now completely deprecated. Steinberg stopped supporting it a few months ago and they strongly suggest using VST3 from now on.

Thats fine -- except for plugins where the VST2 version works and is stable in a specific DAW but the VST3 version is not. Case in point: ST4 in Studio One. There are several reports in this thread of this issue. How many of the affected users have tested the VST2 version to see whether it has the same problem? They would have to uninstall the VST3 to try this.

[zimmerabc]

No shipping for me, germany

[zzz00m]

With regard to Studio One only seeing the VST3, that's by design. The developers have explained:

This is normal. There’s a setting in the VST library code, which is enabled by default in our code, that basically says “if a VST3 version is available, use that”. Studio One (and possibly Cubase as well) use that setting, so if you have both VST2 and VST3, the host will hide the VST2 version.

On another note, please consider that VST2 is now completely deprecated. Steinberg stopped supporting it a few months ago and they strongly suggest using VST3 from now on.

Thats fine -- except for plugins where the VST2 version works and is stable in a specific DAW but the VST3 version is not. Case in point: ST4 in Studio One. There are several reports in this thread of this issue. How many of the affected users have tested the VST2 version to see whether it has the same problem? They would have to uninstall the VST3 to try this.

I just tested this, and Peter is correct.

No need to uninstall the VST3 to try it.

Just simply renaming or moving the VST3 plugin file temporarily will do the trick. On the next startup Studio One will present only the VST2 in the instrument browser, if that is all the scan can find. Make sure that you have "Scan at startup" checked in your S1 options.

[DrumAddict]

loading multis from imported ST2 Librarys does not work at all , nothing changed with the update to 4.0.2 .

[ZincT]

Peter,

Can you just clarify the order of installation? I have ST4 Standard but haven't installed anything yet awaiting bug fixes (but already have ST3 MAX installed from pre ST4 days).

Is the following correct (I am using filenames minus .zip below to avoid ambiguity)? :

• Run SampleTank_4_0_0 (or can I just go to step 2?)

• Run SampleTank_4_0_2

• Run SampleTank_4_Instruments_Installer

• Run all of the separate instrument installers (I make it 29 files here for the ST4 std)

• Run SampleTank_4_Sound_Library_Update_1_1

I am running the Windows version on Windows 10.

Thanks

If you haven't installed anything yet, just install 4.0.2 first, then the sound libraries, then the updaters. Advice about installing the updaters first was for those who have already installed a previous version (and it wouldn't cause the apocalypse if they didn't anyway ).

Thanks Peter.

[zzz00m]

Found something odd about a Syntronik "Groove Split" multi loaded into ST4, as it sounded different than when played in Syntronik.

I was testing with the factory multi "Syntronik > Groove Splits > Venus".

It loaded the four instrument layers OK, but defaulted to four successive MIDI channels 1-4. So fixed that by changing them all to use MIDI channel 1 for a split as it was in Syntronik, but it still sounded different.

The arpeggio sound was missing on the fourth part!

Turns out the arpeggio was loaded in ST4 for the fourth part, but was inactive. Had to switch on the arpeggiator "play" button manually.Then it seemed to work fine.

Not a big deal, but it would be nice to not have to make these small adjustments to get it to play correctly. Probably just an oversight. Hopefully they will auto enable any arpeggiators for imported multis, and address the MIDI channel assignment thing.

This seemed to be pretty consistent behavior based on several Syntronik multis that I tried.

[PointOfDeparture]

Can anyone comment on the sounds themselves? Are they approaching Kontakt-level detail or are they closer to what was presented in ST3 (a couple velocity layers for most patches)?

For instance drums: Would you say they are on the level of previous Sampletank libraries, Infinite Drums/Ocean Way, or AddictiveDrums?

I'm assuming the sound engine is improved. Is there a noticeable difference using raw ST4 content vs. ST3/ST2?

Please elaborate upon whatever you feel is necessary

....Wait this is KVR...I didn't need to say that last part.

[Spin Boyz]

Got my FedEx tracking number today. I'm guessing everyone that ordered the USB drive should be receiving theirs soon.

[MikeCallon]

Peter,
Any chance we could have an answer on when us USB purchasers can expect to receive our software? I would at least have expected an "it's on it's way" email from IKM, if only as a common courtesy! Having paid 15 Euro for delivery of essentially a USB stick, I was hoping this would have been delivered by now, but as far as I know it's not even been shipped yet.

Very poor comms on this one IKM - I expected better

[Peter - IK Multimedia]

Peter,
Any chance we could have an answer on when us USB purchasers can expect to receive our software? I would at least have expected an "it's on it's way" email from IKM, if only as a common courtesy! Having paid 15 Euro for delivery of essentially a USB stick, I was hoping this would have been delivered by now, but as far as I know it's not even been shipped yet.

Very poor comms on this one IKM - I expected better

I know there have been USB orders shipped, received, and installed so they are shipping. You can get your order status in your IK User Area under My Orders and you should see the tracking information once it has.

[Peter - IK Multimedia]

With regard to Studio One only seeing the VST3, that's by design. The developers have explained:

This is normal. There’s a setting in the VST library code, which is enabled by default in our code, that basically says “if a VST3 version is available, use that”. Studio One (and possibly Cubase as well) use that setting, so if you have both VST2 and VST3, the host will hide the VST2 version.

On another note, please consider that VST2 is now completely deprecated. Steinberg stopped supporting it a few months ago and they strongly suggest using VST3 from now on.

Thats fine -- except for plugins where the VST2 version works and is stable in a specific DAW but the VST3 version is not. Case in point: ST4 in Studio One. There are several reports in this thread of this issue. How many of the affected users have tested the VST2 version to see whether it has the same problem? They would have to uninstall the VST3 to try this.

The VST3 version should be stable in DAWs though, so I'd also recommend reporting any issues with the VST3 version to IK Support. Crashing issues have been fixed in 4.0.2 and if there were reported issues with specific DAWs reported and verified those would be fixed too either in 4.0.2 or an upcoming update depending on when they were reported, verified, and fixed by dev.