@aymenSo Hello here. Not directly relevant but give you are on our testing channel, you may as well be using the latest version re:
See:
Shouldn’t affect your issue but it’s best to be reporting / experimenting against the latest code: just in case.
Also be sure to press the Rock-ons update button after making any changes. Expecially with custom Rock-on json files etc. And be carefull to use different names for these custom Rock-ons. It looks like you have had a clash of names from the following part of the message:
@Hooverdan and @Flox are more knowledgable on the Rock-on system. But if anyone can chip in on this observed failure then great. We can always improve the robustness of such custom experiments.
Not of much help I realise but just wanted to chip in on this one re use of latest testing, if testing.