SampleTank 4 Bizzare behavior

Plugins
1

Hello, I’d like to report a possible bug using SampleTank4.

I’m on M4Pro MacBook Pro, MacOS 15.3, GP 5.0.28. Latest ST4 update.

Here’s my issue:

Recalling a non-stock preset in ST4 causes the volume levels to drop SIGNIFICANTLY. We’re talking so low, barely audible if nothing else is going. I’ve created a video demonstrating it here:

It has 0 views, so I know IK’s team didn’t actually watch it. . .

Maybe someone here has any clue. I’ve tried replicating this issue in Reaper, and I can’t. I don’t know if host automation is handled differently in GP5 or not; outside my wheelhouse.

It appears that if I use a

  1. bog-standard preset in ST4
  2. edited preset that I save as an internal ST4 multi and don’t touch afterwards

Then I’m good.

If I save a setup as a GP5 preset, create a new multi but don’t save it internally to ST4 and recall via host automation, or edit a multi so that the little asterisk appears inside ST4 next to the name at the top, it’s 50/50 whether the volume issue will occur.

Recalling the sample set that isn’t playing back will bring back the volume, but I’ll lose any edits.

In particular, have a couple of string patches and a pipe organ that do this. In the heat of a set, I don’t have time to leave setlist mode, jump into the wire diagram, open ST4, search for the name of the preset that won’t sound loud enough, and recall it.

It’s REALLY annoying.

IK is… less than responsive on this topic. Though I do have a ticket open with them.

Anyone had this AND figured it out?

/Klop

2

If you search for SampleTank in this forum, you’ll find quite a few oddities reported. Some of them were remedied by assigning a widget to whichever control wasn’t getting recalled properly.

3

I was just in the process of making a new gig to test out variables which could cause recall to fail properly.

GP5 Crashed. I copied the crash report from Console if anyone wants to/can read it.

I created 5 racks, all different permutations of ST4.

ST crashed when trying to load a Miroslav sample.

4

ST4 is known to be buggy - I would never use it in a live situation —

I think that particular Miroslav patch crash has been reported before. Can you please post the crash report so that we can confirm it?

5

  1. Bummer. I swore off IK ST4 back on windows… guess I’ll do the same again for ST4.

  2. Good to know, and I guess I’ll go back to stock Kontakt strings for now. Session strings pro had too many hung notes when I was using it. I wish Korg Module with the KA strings would come out as a VST instead of only on iOS.

  3. No worries, here comes a lot of code. This is what the Console App spit out.

6

I deleted that stuff - normally please zip such things and upload them as compressed files.

That said, I did run that report through the Console system and as suspected, it’s crashing in SampleTank

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0   SampleTank 4                  	       0x148b42300 0x148800000 + 3416832
1   SampleTank 4                  	       0x148ba4cd8 0x148800000 + 3820760
2   SampleTank 4                  	       0x148ba34a4 0x148800000 + 3814564
3   SampleTank 4                  	       0x148f6b5ac 0x148800000 + 7779756
4   SampleTank 4                  	       0x148f74110 0x148800000 + 7815440
5   SampleTank 4                  	       0x1490c02b8 0x148800000 + 9175736
6   SampleTank 4                  	       0x1492e0154 0x148800000 + 11403604
7   SampleTank 4                  	       0x1492dd244 0x148800000 + 11391556
8   CoreFoundation                	       0x18ef1c8a4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
9   CoreFoundation                	       0x18ef1c838 __CFRunLoopDoSource0 + 176
10  CoreFoundation                	       0x18ef1c59c __CFRunLoopDoSources0 + 244
11  CoreFoundation                	       0x18ef1b138 __CFRunLoopRun + 840
12  CoreFoundation                	       0x18ef1a734 CFRunLoopRunSpecific + 588
13  HIToolbox                     	       0x19a489530 RunCurrentEventLoopInMode + 292
14  HIToolbox                     	       0x19a48f348 ReceiveNextEventCommon + 676
15  HIToolbox                     	       0x19a48f508 _BlockUntilNextEventMatchingListInModeWithFilter + 76
16  AppKit                        	       0x192a92848 _DPSNextEvent + 660
17  AppKit                        	       0x1933f8c24 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
18  AppKit                        	       0x192a85874 -[NSApplication run] + 480
19  GigPerformer5                 	       0x102deffdc 0x102738000 + 7045084
20  dyld                          	       0x18eab4274 start + 2840
7

Same thing, also at other Presets /( c70p grand, Syntronic…). Just for the first try of them. Syntronic is still not workin, but the will do their Jobs. Sample Tank max4 installed 2 day#s ago.

1 Like
8

Thank you for confirming, too!

Miroslav CE samples have been the only ones to crash it for me so far. The ST3 samples, in particular, seem to cause the volume recall issues. I don’t have many ST4 presets to try it with, since I’m working with ST4-CS, not the MAX. I refuse to upgrade when the CS version is this buggy already.

I’ve been able to get Syntronik Max v2 up and running, but am careful, based on the recommendations of the forum, to try and stick with the Syntronik2 presets and stay away from editing and then recalling any Syntronik1.

It is frustrating that I can’t get the behavior to replicate on Reaper, because IK’s response feels like “well it works in DAW-X, so it’s not our fault.”

9

Sorry about that! There’s nothing in there that says what part of SampleTank caused the crash though?

I feel that I need to make it blunt and obvious to the developer to get even the slightest chance they do something.