renderSlice 1151 -10876 Error

[ary48682]

Hello everyone,

I'm trying to load up FM8 1.4.1 on the most recent version of DP 11, but when I do, I receive this error: "renderSlice 1151 -10876" I did some research and it /seems/ it has something to do with macOS Monterey + DP compatibility or that it is being worked on. The post I found goes back four years ago though, so not sure where it's at at the moment.

I tested opening FM8 on a different DAW and it loaded up just fine. Any ideas/solutions for how to get this working? I already reinstalled FM8, reexamined the plugin in the DP preferences, but each time I make a new instrument track, I get the same error. In the forum post mentioned above, someone said removing the Library/Preferences fixed it temporarily, but I can't even find the MOTU preferences on my end.



Thanks so much for your help!

[HCMarkus]

You can probably run FM8 within Komplete Kontrol.

PS: You might want to add a signature with CPU and other specifics.

[cuttime]

I don't know what system you're running, but I get this error on some plugs that are Intel only when I'm running DP in AS mode without Rosetta. Reaktor come to mind, and generates the exact same error. I ran this by MOTU when I first got my M1 machine, and MOTU confirmed this.

[HCMarkus]

I don't know what system you're running, but I get this error on some plugs that are Intel only when I'm running DP in AS mode without Rosetta. Reaktor come to mind, and generates the exact same error. I ran this by MOTU when I first got my M1 machine, and MOTU confirmed this.

+1

[ary48682]

I don't know what system you're running, but I get this error on some plugs that are Intel only when I'm running DP in AS mode without Rosetta. Reaktor come to mind, and generates the exact same error. I ran this by MOTU when I first got my M1 machine, and MOTU confirmed this.

+1

I'm currently on macOS Monterey. I swear that every single time I upgrade the operating system, it either kills support for software I use, or forces me to find a workaround. I just need an offline machine that I never update under any circumstances. That should work for at least 10 years.

What is AS mode? Has MOTU indicated a fix for this issue? Or is this just something that I won't be able to get around?

[mikehalloran]

What is AS mode? Has MOTU indicated a fix for this issue? Or is this just something that I won't be able to get around?

Apple Silicon. Since you haven't told us what Mac you are running, we can only guess that you have an M1 or M2 Mac.

renderSlice 1151 -10876 Error is an OS error, not DP.

I'm currently on macOS Monterey. I swear that every single time I upgrade the operating system, it either kills support for software I use, or forces me to find a workaround. I just need an offline machine that I never update under any circumstances. That should work for at least 10 years.

The M1 is not 10 years old. In the mean time, FM8 is not AS compatible at all per this support doc from NI.
https://support.native-instruments.com/ ... ility-News

If you are not on an AS Mac, that this started with an upgrade to Monterey might be the issue. According to this, the last compatible MacOS for FM8 was Catalina:
https://support.native-instruments.com/ ... s-on-macOS
while this bulletin says it works over Big Sur
https://www.native-instruments.com/en/p ... fications/

You should contact NI Support to see if they have any advice for you.

[mikehalloran]

In this NI Community thread, someone from NI Customer Care says that FM8 is scheduled for updates.
https://community.native-instruments.co ... mment_4628

I forgot that I can look this up in Native Access (updated to 2.70 this morning):

[ary48682]

Ah – makes sense. Yes, I'm on the Apple Silicon M1 chip.

Thank you for posting the Native Instruments links. I had not seen those.

I guess I'm confused as to why this is a M1 chip issue. The standalone version of FM8 opens up just fine, and I can even load up the plugin in a different DAW. It's specifically Digital Performer which doesn't load it up, so shouldn't the issue be a DP issue?

[mikehalloran]

Ah – makes sense. Yes, I'm on the Apple Silicon M1 chip.

Thank you for posting the Native Instruments links. I had not seen those.

I guess I'm confused as to why this is a M1 chip issue. The standalone version of FM8 opens up just fine, and I can even load up the plugin in a different DAW. It's specifically Digital Performer which doesn't load it up, so shouldn't the issue be a DP issue?

What happens when you run DP over Rosetta 2?

[ary48682]

Ah – makes sense. Yes, I'm on the Apple Silicon M1 chip.

Thank you for posting the Native Instruments links. I had not seen those.

I guess I'm confused as to why this is a M1 chip issue. The standalone version of FM8 opens up just fine, and I can even load up the plugin in a different DAW. It's specifically Digital Performer which doesn't load it up, so shouldn't the issue be a DP issue?

What happens when you run DP over Rosetta 2?

Hilarious – guess what? It seems to work just fine! Huh.

Digital Performer seems to be noticeably slower though, but it isn't awful. Thanks so much for the tip! Maybe this workaround is good after all.

[mikehalloran]

…
What happens when you run DP over Rosetta 2?

Hilarious – guess what? It seems to work just fine! Huh.

Digital Performer seems to be noticeably slower though, but it isn't awful. Thanks so much for the tip! Maybe this workaround is good after all.

Per the NI links to the Customer Care post, FM8 is scheduled to become AS Native at some point (all of Komplete 14 will be). When that happens, running DP over Rosetta 2 will not be necessary unless you are using other non-Native plug-ins.

[cuttime]

Time to "plug" PlugInfo again. Sorts all of your plugins by processor type. It will save you a world of hurt during the Intel to AS transitions. All for the exorbitant price of $3.

https://apps.apple.com/us/app/pluginfo/ ... 2949?mt=12

[James Steele]

As mentioned, when running DP in AS native mode, you CAN run FM8 (VST) inside NI Komplete Kontrol. I also was able to run the AU version inside Blue Cat Audio’s PatchWork, although seemed there was a bit of a higher than usual CPU hit.

[dtobocman]

I'm having the same problem using Reaktor. Komplete Control gets around the problem, but I don't have the full functionality of Reaktor. It only loads presets, which then loads each of the different synthesizers (ensembles) within Reaktor, but it's not how I'm used to working with Reaktor. Ugh. I go to Reaktor to get weird and this feels like I'm auditioning keyboards at Guitar Center. This looks like it could helpful to get me back to my normal Reaktor enviroment:

https://support.native-instruments.com/ ... TE-KONTROL

[James Steele]

Have you tried selecting Edit View from Komplete Kontrol after loading Reactor? I know when you load Kontakt inside of Komplete Kontrol, choosing that will let you see the entire Kontakt UI just as if you’d opened it directly.