Hi Paul,

I'm using a Roland RD-2000 as my sequencer, connected via USB to my M1 Max Mac Studio. I'm using the most up-to-date driver for my RD-2000 with my Mac. Changing the "sample buffer" within the driver software does not seem to affect any of the issues I address within this post.

I'm recording MIDI using Garageband, and I'm running Vienna Imperial Bosendorfer as a VST plugin within Garageband. 

Here is a MIDI file I saved from Garageband in which I used full polyphony and full samples for the Bosendorfer. You'll notice from the beginning that there is muting of notes. After a few minutes, the plugin itself stopped working entirely even though the MIDI notes continued to be recorded - https://drive.google.com/open?id=1GA11Q77f8Hei324_s9Sy1sEC_OlCBLEO&authuser=sshimel123%40gmail.com&usp=drive_fs

Then, I restarted Garageband, re-launched the Bosendorfer plugin, set polyphony to 160 and samples to omit soft pedaling, and recorded. This time, I experienced no muting or any other issues - https://drive.google.com/open?id=1GAVYrs_WsbdvtwA4jdwbqiPfl4BqTxth&authuser=sshimel123%40gmail.com&usp=drive_fs

I can confirm that when using either the Imperial Player or Vienna Ensemble 7 that the issues I experienced in the first take with full polyphony occur in the same manner. Vienna Imperial Player often crashes when using full polyphony. I'm not sure how to send you those error logs, but I can if you'd like to see them.

Thank you for your help. Let me know if I can send anything else along.

Hi, 

I have requested access to these files, so that I can download and check those.

Best, 
Paul

@Paul said:

Hi, 

I have requested access to these files, so that I can download and check those.

Best, 
Paul

Hi Paul, you should now have access. Thank you.

Hi again Paul,

Just double-checking that you now have access to both MIDI files? 

As an FYI, I'm hoping that we can troubleshoot this matter more this week in case I need to request a refund for this VST while I'm still in the return window. At present, it remains unusable.

I should note that I'm also hearing occasional popping sounds when the VST is functional (it doesn't matter what polyphony level is used). Other VSTs I use do not exhibit this behavior.

Thank you again for your support!

Hi Rik3Rr,

Sorry for the delay. 

We loaded your first  song and played with the settings on a M2 MB Pro, with the internal soundcard. Running GarageBand natively, no troubles here with any polyphony settings. 

Your "Take 2" song doesn't contain any MIDI data...  Really wonder what's wrong here. 

Just to be sure: Your NVME drive is NOT formatted in exFAT, right?

Best, 
Paul

Hi Paul,

Both my internal NVMe and my external NVMe are all using APFS (encrypted) Could it be that the encryption is causing this issue?

Could iLok be causing this issue somehow? I'm using the cloud license option?

I have another MBP and I will load this VST onto it later and see what happens with it so as to compare results. 

Please note that I turned off encryption today, as well as my virus protection (bitdefender). Nothing changed.

Again, in the Imperial Player, when polyphony is set to 160 or above, muting of notes happens after 1 minute of play, and then eventually the player crashes. 

I tried reinstalling Vienna Assistant, Imperial Player, and re-downloading, but the results remain the same.

I'm at a loss for where to go from here.

Here is the crash log from Imperial Player this morning after it crashed while playing at 256 polyphony:

The VST is hosted on the internal NVMe, which is formated in APFS (decrypted now).

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

[Crash Report Text removed from post - please attach a text file]

Last post today: I just tried booting the Mac into Safe Mode, but no change in result.

If you all cannot figure out a solution, then I feel like my only remaining option is to try reinstalling MacOS entirely, but I'm not excited to do that, for obvious reasons.

Here is the crash report I posted earlier but was taken down due to length.

And here's another crash report with a different error code.