User goal: set multiparam to control Vibrato Rate among other params, useful for MIDI-controlled synthetic vibrato when you want it but the instrument you're using doesn't have it
1. Install MVibrato 16.10 AU and launch as a Logic 10.8.1 (M1, non-Rosetta, Mac 13) plugin insert
2. Click the up/down arrows to the right of Utilities
3. Click "1:" (first multiparam)
4. Click + under Parameters
5. Select Rate
6. OK dialog
=> Crashes every time on my machine
Note that at least some other params don't crash
Note also this crashes on loading such presets from an earlier era when this worked
Thanks in advance for a prompt fix, I didn't try 16.11 beta
MVibrato 16.10 crashes with easy repro
-
martin-meldaproduction martin-meldaproduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=583716
- KVRist
- 266 posts since 6 Oct, 2022
Hello,
the issue is reproducible, but I have to inform you the bug is not on our side. It happens only on macOS Ventura and Logic Pro engine (in native mode). No other DAW can cause this. We have been aware of this problem since January 2023 and reported the bug to Apple shortly after. Apple acknowledged that the bug is on their side, but unfortunately, they have not fixed it yet, despite it being 12 long months already. They promised a workaround, but so far, there have been no results. We have been regularly urging them for updates, but they haven't provided any substantial answers yet.
Nevertheless, you can get rid of the issue by running Logic Pro in Rosetta mode or by using another DAW or if you upgrade to macOS Sonoma, the bug is gone also in Logic Pro.
the issue is reproducible, but I have to inform you the bug is not on our side. It happens only on macOS Ventura and Logic Pro engine (in native mode). No other DAW can cause this. We have been aware of this problem since January 2023 and reported the bug to Apple shortly after. Apple acknowledged that the bug is on their side, but unfortunately, they have not fixed it yet, despite it being 12 long months already. They promised a workaround, but so far, there have been no results. We have been regularly urging them for updates, but they haven't provided any substantial answers yet.
Nevertheless, you can get rid of the issue by running Logic Pro in Rosetta mode or by using another DAW or if you upgrade to macOS Sonoma, the bug is gone also in Logic Pro.
Martin
MeldaProduction
MeldaProduction
-
- KVRer
- Topic Starter
- 2 posts since 6 Nov, 2009 from San Francisco
Ok thanks very much Martin for the update. I have resisted the Sonoma upgrade worried it would cause more problems but here it apparently fixes one.
