New Syntronik 2 from IK Multimedia

New Syntronik 2 released by IK Multimedia.
Just installed the update, seems to be free for existing Syntronik users.

Best feature: Now with Syntronik 2 Host Automation is implemented !

4 Likes

Hey, good news! That’s one good reason to have a look at IK again… just about to install V2 right now!

And they implemented streaming from disk.

That means…? The sound is available faster?

Should load faster and memory usage should be lower.

1 Like

Humm - I am wondering if I should update my Studio Max 2 to Studiio Max 3.5 and therefore get B3X in the updated bundle?.. :thinking:

B3X is wonderful

2 Likes

Now I built a gig with 20 rackspaces, each 1 Syntronik plugin.
Memory usage with Syntronik 2 is about 1GB lower than with Syntronik.
But I am sure when you play all notes then the memory usage will be similar.

But playing all notes does not make sense at all :wink:

Anyone else having problems with Syntronik 2 crashing GP after closing the plugin window? I can audition and choose sounds. But, whenever I exit the plugin window, GP crashes.

Process: GigPerformer4 [584]
Path: /Volumes/VOLUME/*/GigPerformer4 2.app/Contents/MacOS/GigPerformer4
Identifier: com.deskew.gigperformer4
Version: 4.2.3 (4.2.3)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2021-11-29 12:27:20.2070 -0600
OS Version: macOS 12.0.1 (21A559)
Report Version: 12
Anonymous UUID: F504616A-1DED-E792-C763-1DD55D477AA7

Time Awake Since Boot: 94 seconds

System Integrity Protection: disabled

Crashed Thread: 0 HotFudge Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000001dc
Exception Codes: 0x0000000000000001, 0x00000000000001dc
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [584]

VM Region Info: 0x1dc is not in any region. Bytes before following region: 4440071716
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 108a62000-10bbc2000 [ 49.4M] r-x/r-x SM=COW …GigPerformer4

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 Syntronik 2 0x1162b3068 0x115654000 + 12972136
1 Syntronik 2 0x115dff950 0x115654000 + 8042832
2 Syntronik 2 0x115f770e1 0x115654000 + 9580769
3 Syntronik 2 0x1161b3c1d 0x115654000 + 11926557
4 Syntronik 2 0x1161b0f27 0x115654000 + 11915047
5 CoreFoundation 0x7ff801f9084d CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
6 CoreFoundation 0x7ff801f907b5 __CFRunLoopDoSource0 + 180
7 CoreFoundation 0x7ff801f90534 __CFRunLoopDoSources0 + 242
8 CoreFoundation 0x7ff801f8ef6b __CFRunLoopRun + 893
9 CoreFoundation 0x7ff801f8e52d CFRunLoopRunSpecific + 563
10 HIToolbox 0x7ff80abac3e1 RunCurrentEventLoopInMode + 292
11 HIToolbox 0x7ff80abac137 ReceiveNextEventCommon + 587
12 HIToolbox 0x7ff80ababed5 _BlockUntilNextEventMatchingListInModeWithFilter + 70
13 AppKit 0x7ff8049b98f0 _DPSNextEvent + 886
14 AppKit 0x7ff8049b7f5c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1411
15 AppKit 0x7ff8049aa359 -[NSApplication run] + 586
16 GigPerformer4 0x108f8cefb 0x108a62000 + 5418747
17 dyld 0x118fb24fe start + 462

Couldn’t repro on Windows with VST or VST3.

1 Like

Thanks. I’m installing on Windows to try now. On my Mac it does it with vst, vst3 & AU.

1 Like

Found this in a Forum
Syntronik 2 crashes Live and Cubase , on Monterey. It loads but when you close the plugin screen it crashes. Didnt happen with version 1. Anybody else seeing this? Ive tried AU, VST2 and VST3

2 Likes

That’s what I’m on…Monterey 12.0.1.

Are you sure Monterey is supported by Syntronik 2?

It seems to work OK in standalone. But it crashes in GP. I’ll try Reaper and Live.

I am on Big Sur and do not face the crash

Yep…It crashes Reaper the same way…when closing the plugin window. I guess for the time being I won’t use Syntronik 2 in GP. :angry:

You should contact IK Multimedia

1 Like

The stack trace is very clear – the Syntronik 2 is crashing.

I have let them know. We’ll see what happens. I’m sure they’ll say TS…