Reaktor 6: How do I debug Metaphysical Function
Answers
-
This is an old ensemble that does use event loops. You turned off event loops, so it is complaining about the event loops that it is not allowed to run.
Just tried on M1 Macbook Pro Mac OS 14.5 (latest) Reaktor 6.5.0
HTH
drb
1 -
Yes, that’s it! Earlier in the thread someone told me to disable event loops, but as they were already disabled, I thought the problem lay elsewhere.
Thanks a lot!0 -
No, it doesn't hurt of course! It's your time and you can waste it in anyway you like… 😀
0 -
So, the problem was the opposite from what i suspected, because he had the Event Loops already disabled (which is not the default setting)!
Thus it was impossible to guess it, but you did! Good catch, well done.
0 -
That's very weird because the error message says 'an event loop occured' so you would think naturally disabling them would have fixed it, not the opposite - maybe this is another example of Reaktor's often not useful error reporting?
0 -
Hi @Kymeia,
It notifies you that the Ensemble is working with Event Loops, and because the Event Loops are disabled, this is important information. Otherwise, the user would not know why Metaphysical is not working properly.
2 -
No, it doesn't hurt of course! It's your time and you can waste it in anyway you like… 😀
On my machine reinstalling Reaktor took 25 seconds, not much wasted, but i totally understand your point.
0 -
Have you identified the loop in edit mode?
0 -
Hey @Studiowaves if with loop you mean the modal Dialog Boxes Event-Loop occured in Module, those have nothing to do with the Edit mode. These messages appear no matter if Edit mode is enabled or disabled.
0 -
I'm not talking about the errors, I'm talking about going into edit mode to see the structure of the ensemble. In general, if there are loops in the ensemble that aren't properly coded, the debugger highlights the loop. Most feedback loops in reactor use the Z-1 module to allow feedback. You might have to go in there and look around for a highlighted event loop. If you find that then break the loop by disconnecting something just to see if the errors go away. Then hook it back up and post a screenshot of the highlighted loop for us to look at.
0 -
Why should we do that ? The issue Daniel describes can be fixed by enabling Event loops in Reaktor6, which is the default.
0 -
"Why should we do that ?"
Well… out of curiosity perhaps? …to see the structure? …to cannibalize some delicious module part for your own works? …there are many reasons (but of course no one has to do with Daniel's issue)…
…aren't those the real reason that we love Reaktor? 😉0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 735 Tech Talks
- 3.9K Native Access
- 15.9K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 817 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 7K Traktor
- 7K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators