Just what it says in the title - I’m getting a hard crash when trying to select a preset (from Pro-R2), consistently. Opened Nuendo 12, no issue, just seems to be something with 13. Doesn’t happen in any other DAW, either (Live 11, Logic, Bitwig, Studio One).
Running on an M2 Ultra Mac Studio, in native mode (no Rosetta). Running latest (Nov 7) Ventura, haven’t updated to Sonoma.
Interesting because i have no issues with it in N12 (just like the poster). So something is different in the way the version handle the plugin… or is that a too forward conclusion?
Please get in touch with FabFilter and provide them the crashlog from above. They are normally very fast in resolving such issues.
By the way I was not able to reproduce the crash. Did you choose a preset in the UI of the plug-in or do you use the Nuendo preset mechanism to load the preset?
Was able to reproduce it here, but only if Pro R-2 is used as an insert effect. It did not crash when placed on an FX channel/bus on it’s own. I was able to switch presets without issue. The crash happened right after placing it on an existing track (with clips) and attempting to select a preset.
Indeed. But I’m sticking with PT and Nuendo (and my heart’s in the balance). Samplitude, finished, despite many good years. Studio One, after several attempts, also abandoned. Reaper, too complicated. Feels like I have to build a kit house. No time. Ableton, my favorite interface, because no flafla. But I’m mostly in classical, so it’s not my world.
I work in pop, rock, and singer-songwriter stuff, as both a producer (in the traditional sense) and a mixer. I use Live as a production DAW/sketchpad, generally, though Nuendo for that on occasion - which was how I discovered this crash, I was messing around with routing my new studio.
I only use Pro Tools if the contract calls for it, and the others are specific people I work with.
I do use FabFilter stuff almost religiously, largely because of it being consistent across DAWs.
Have you tried doing it with something instantiated before, on a track with content? Because that is how I can consistently get it to crash - and it seems to be Pro-R2 only, not other FF stuff.