Console.stop

rzrsharpeprod

I've done something really silly and don't know how to undo it

For some unknown reason I have used the line Console.stop(true); earlier in my code and even though I have tried commenting it out, deleting it & recompiling etc it is like it is still active as nothing is showing in the console except for compile errors.
I have even tried Console.stop(false); as a means to reverse it but no joy.

If I start a new preset within the same project and use some console print code to show a knobs current value for example it works as expected and the values print in the console as the knob is rotated.
If I then paste that code back into the actual preset then nothing prints on the console at all.

Can I reactivate the console somehow as I don't want to have to start from scratch if I can avoid it.

Thanks in advance

Christoph Hart

@rzrsharpeprod If everything goes wrong, you can always edit the script in a external script editor and then reload the project. A Console.stop() command will invoke a breakpoint, but it shouldn't be something critical...

d.healey

@rzrsharpeprod

nothing is showing in the console except for compile errors.

Fix those and try again ;)

rzrsharpeprod

@Christoph-Hart I have removed the console.stop line completely but it's like it is still active. I don't understand what's happening.

Nothing shows in the console but if I load an older XML backup from before the console.stop.line is in there the console acts as it should do. This makes me think that the console.stop line has caused the issue

rzrsharpeprod

@d-healey no I meant if I have a compile error then that shows but nothing else does.

I don't have any compile errors currently, I was just giving it as an example.

Hope that makes sense

d.healey

@rzrsharpeprod Can you share the project with me?

rzrsharpeprod

@d-healey Hi David, apologies for the delay, I was having a go at finding the issue and have found it so thought I would share it in case you have any thoughts on why this would happen.

I went back to the last XML backup that worked and started adding things back in until the console stopped working as it should. I figured out earlier that it probably wasn't the console.stop command that was causing the issue as it made no sense that it would still be doing something after it was deleted and especially after I replaced the code completely via an external editor as @Christoph-Hart suggested.

Anyway I digress. The issue was caused by me linking a slider to an LFO on the degrade module (it also happens
if I link it to the intensity parameter as well as it turns out)
Why would you want to modulate the degrade with an LFO you are probably asking? Fair point, but I have been playing with different ways to get a wobble effect for an FX plugin so was trying allsorts.
The reason being that using LFO to mod the delay or using some of the scriptfx examples on here gives me a weird crackling effect when the slider is moved which doesn't sound great as I just want a pure, clean wobble effect.

Regardless of the reasons for me doing it, when I hook the slider up to the LFO modulating the degrade then the console stops giving me realtime feedback such as console print etc. It basically only gives initial messaging such as EQ1 added and then any compile errors but nothing else. It doesn't even say Compiled OK in the actual console anymore, it says that above the console instead.
Further to the console oddness, it seems to stop other functionality too - I have a button that turns on or off when the slider reaches a particular value for example, but it doesn't work if the slider is hooked up to that.

It's all a bit odd but at least I have found the issue so can resolve it.
My search for a good, clean wobble continues though as clearly that is not the way forward.