< Back to IRCAM Forum

How to recover a patch after an unstoppable error loop?

OpenMusic
#1

From time to time, it happens, that I connect the wrong things together (I’m a beginner). Usually, after evaluation, an error message pops up, and i can undo my connection. that’s fine.
But in some rare cases, I can’t stop the evaluation, and an error message shows up again and again, and the patch will be unusable. The abort-shortcut apple+shift+a doesn’t work here.

Is there a way to abort the evaluation/error loop to recover and undo the connection?
Or is it possible to implement an abort process in the future?

I attached 3 pictures with a simple example, I connected in the wrong way.
First shows the original patch, the second the messed up patch after evaluation an the third the error messages.

#2

Hi

Your note object (left) cannot take a list for midic. You should use either a chord object or input a simple midic integer,
Independently of your hang process.

best
K

#3

Thanks Karim,
this patch is just an example. I made this by purpose to produce a non stoppable loop. I did other mistakes, which I didn’t understand instantly…
I just wanted to show the possiblity to mess up a patch accidently.
Ben

#4

Dear Ben,

Sorry didn’t catch it. My bad. But anyhow you should not have a non stoppable loop with such mistakes. Maybe (i say maybe…) it is because you are using the reactivity mode. It is just a guess since i don’t use it. Only the stack overflow will let your computing go for a while but you still will have an error message signaling the stack overflow and then auto terminates the calculation. These happen when you have a non terminal iteration or a recursion or such. But with a simple mistake like that this is not normal.
Maybe Master Jean will tell us more about this issue.

BEst
K

#5

The error is caused by the note display.
I agree it should not be such a big deal and OM should prevent this to happen in the first place

a solution to get out of the error is to select the window and press ‘M’ (uppercase) to hide all miniviews

Jean

#6

@Jean
Hiding the miniview works to stop the error-loop. This is good for undoing mistakes. Now I found out, that in this case, where a list of midinotes is badly connected to a NOTE-object, the hide of the miniview disables an error message at all. There should be an one-time error message to alert about the bad connection. Is this right?

@Karim
I don’t have reactivity mode enabled.

Thank you both for answering strange beginners questions
Ben