SampleTank 4 on the way

[rrichard63]

Only the VST3 version is resizeable. The VST2 version isn't.

I'm not having this issue here with Win 10. The ST4 standalone host app, plus the VST2 and the VST3 are all resizable.

Please, somebody explain why different users are reporting different things about resizability.

I think you will be happy with ST4. I upgraded for the same reason - the UI was too small in ST3. I'm very happy with the size of the ST4 interface.

Are you referring to VST2? To VST3? To standalone? It is critically important that everyone be accurate and precise here.

It is even more critically important that IKM be accurate and precise about this.

[zzz00m]

I have a ton of problems with this.

Windows 10, 32 GB of RAM, 2 TB HD, ST4 4.01.

1. I cant resize the screen

Don't understand why not. It works fine for me on Win 10.

2. I found out that only ST4 instruments can access the mod matrix. ST3 instruments can't. That's some bullshit right there

Agreed! I find that quite a a surprise! I believe that IKM owes us a converter to import our ST3, Miro, and Syntronik libraries to the new preset format so we can fully use the new features in SampleTank 4!

4. Only Element LFOs & User Envelopes are only available for ST4 sounds

Another biggie!!! I think that should be addressed the same way as with the mod matrix!

[msorrels]

Now I'm even more confused. I removed the VST3 version and Cubase is supporting resizing in the VST2 version.

Is it possible they patched the 4.0.1 version a second time without saying anything? Certainly seems like it's supporting resizing now, but it really didn't the first time. I tend to not trust IK's VST3 synths so I went with VST2 by default.

At this point I'm thinking I'm wrong or it's changed and resizing is working in VST2.

[zzz00m]

Only the VST3 version is resizeable. The VST2 version isn't.

I'm not having this issue here with Win 10. The ST4 standalone host app, plus the VST2 and the VST3 are all resizable.

Please, somebody explain why different users are reporting different things about resizability.

I think you will be happy with ST4. I upgraded for the same reason - the UI was too small in ST3. I'm very happy with the size of the ST4 interface.

Are you referring to VST2? To VST3? To standalone? It is critically important that everyone be accurate and precise here.

It is even more critically important that IKM be accurate and precise about this.

Are you using a Mac by any chance? I cannot imagine why different users would be reporting resizing issues, unless it has something to do with specific hi-dpi displays or GPU drivers, or cross platform issues. Maybe a lack of full QA testing, perhaps?

I am using a stock Intel HD Graphics integrated GPU and a normal HD 1920 display, without any issues with resizing of any form of ST4.

[zzz00m]

Just a thought. There may be some DAW related compatibility issues regarding the window resizing. I have heard that hi-dpi compatibility can be particularly troublesome. DAWs often handle plugin window management in their own way.

If the standalone version resizes OK, then your GPU and display are probably compatible. If you have trouble in your DAW with either the VST2 or VST3, then you probably should open a support ticket with IK.

[fahl5]

does anyone else have all SampleTank 4 content in triplicates?

The same here.

I saw, that ST4 installs its Samples and instruments in the same folder alredy used by my previous ST3. Could that be the reason?

Is there any way to get each sound only displayed?

[rrichard63]

Are you using a Mac by any chance?

I haven't bought ST4 yet. Whether I ever do buy it depends on how this issue gets resolved. There's no trial or free "custom shop" version, so I can't find out for myself.

I'm on Windows 7, and am using an onboard Intel HD 4600 display adapter to drive a 2560 x 1080 (ultrawide) monitor. Windows is set to a custom text size of 110% rather than the default 100%. But all of that is subject to change at any time, so any software I buy must be compatible with a range of display options.

[Elektronisch]

Just a thought. There may be some DAW related compatibility issues regarding the window resizing. I have heard that hi-dpi compatibility can be particularly troublesome. DAWs often handle plugin window management in their own way.

If the standalone version resizes OK, then your GPU and display are probably compatible. If you have trouble in your DAW with either the VST2 or VST3, then you probably should open a support ticket with IK.

Well if thats the case, then its actually IK fault not to testing on every possible commercial DAW (Reason, Cubase, FL Studio, Pro Tools, Nuendo, Bitwig, Ableton, Studio One, Traktion, Reaper)

Anyways, im still quite shocked about this rocky ST4 release. You did do so well with Uno, new interface, T-racks 5 (minus reported and registered and aknowledged bugs half year ago ). Lucky people who didnt jumped on pre-orders, but even so if people who did that i think if requested IK should give a refund, that would be a right thing to do from their side.

[msorrels]

I'm running Cubase 10 on Windows 10 at 4096x2166 (yes, true 4k on a RTX 2080ti) so anything is possible. But at least when I had only installed the VST2 version Cubase wasn't drawing the little resizer/grip in the corner of the plugin at all. Wasn't that it wouldn't work, it wasn't even possible. I then installed the VST3 version and that fixed it.

I thought I skipped the 4.0.0 version and went right to the 4.0.1 but perhaps I'm wrong about that?

Since other people have reported resizing issues I'm pretty sure it's wasn't just me. But at least right now I seem to be able to resize with either version. No clue exactly why I couldn't before I installed the VST3 version.

[abernathy]

Once again, I hope I'm missing something here... But if you're like me and you love your old Imported Instruments (Sonic Synth, SampleMoog, original Philharmonik, etc.) then ST4 may not be for you. I can't find any way to see these instrument libraries grouped in any way, much less their helpful (critical?) folder hierarchies. There's one big "Imported In..." category with all of the instruments jumbled together - like "If you really want to see that old crap, here it is..." You can't even see the copyright info that was in ST3, and now we REALLY need that to have any idea what library the instrument is from.

[Gamma-UT]

Another biggie!!! I think that should be addressed the same way as with the mod matrix!

As the ST3 and Syntronik sounds have subtly different controls (and no matrix etc) from the ST4 patches, I suspect buried inside ST4 is the ST3 engine, which might help explain the ludicrously large memory footprint for an empty instance. Which means a converter is probably unlikely - at least one that will match the previous sound.

However, I'd be OK with a converter that just moved the samples across and the basic controls with no promise of a sonic match. At least that would make the old Future Synths package vaguely usable.

[msorrels]

The manual has a whole section on there being two engines for the earlier ST3 sounds.

[fahl5]

My original MP II is loaded without problem. And the ST 3 Sounds which were already installed here are loaded as far as I can see without problem (Win 10)

But again: Is there anyone else except me and the other User Burillo (who has posted his screenshot with the issue) with this "triplicate display of the available sounds-issue"?

[rrichard63]

The manual has a whole section on there being two engines for the earlier ST3 sounds.

Can I download the manual, or read it on line? If so, where?

[msorrels]

There doesn't seem to be any public links to the manual(yet). I looked since I thought posting it would be useful. It's only available in your account.