Happens for me as well, both on startup and I believe when issuing a ;restart command in the SC portion of Maiden

what do you mean? we are talking about strong aliasing or modulation distortion on the norns audio inputs.

if you mean the chorusing sinewave that is played for 6 seconds on startup (or ;restart,) this is intentional; it can be removed or customized by changing or removing this line

as the comment suggests, this was added as a debugging step at some point, but we liked it and kept it around.

Ah, indeed I was! Sorry! Well, for what it’s worth, I have encountered what you guys are talking about (an altogether unpleasant distortion applied to incoming audio) twice, and a reboot (via sleep) solved it both times. If it happens again, I’ll get a sound sample and post.

1 Like

Just chiming in to say I’ve experienced this “ring-modulated” distortion issue with Norns once or twice, but a proper reboot always seems to solve it.

One more question about logging - is it generally safe to nuke the entire /var/log directory? I’ve also noticed that my daemon, messages, and kern logs are somewhat large.

1 Like

thanks for the heads up. I need to reopen the log size issue, as we thought it was fixed

Yeah I can say I had the issues too several times since 2.0 (ring mode stuff + distortion on incoming audio) the ring mode thing is easy to spot because the weird sine wave sound on startup sound makes it obvious right away. Haven’t had it the last few times I used norns though an haven’t updated to 2.1 yet so couldn’t say if it’s fixed or not!

ok, that’s a new one, i have not observed the weird aliasing thing on output, only on input.

afaik, sure, unless you need the logs.

Really? It was sort of ring modulation sort of flanger, for a while I just assumed the “launch sound” had changed, but it sounded weird on the apps too so I was a bit confused and looked around to see if there was a new FX I missed and should bypass, couldn’t find anything. And if I remember correctly it took a few resets and it came back to normal.

Also had the distortion on input (kinda similar to what I’d get on a computer with too low buffer settings, completely crashing, super low volume) I actually assumed for a while it was my electro acoustic guitar that was out of battery life, but then plugged the OPZ and it was the same so I hard reset the norns and it worked fine.

I couldn’t reproduce the bug with the ring mode / flanger thing so it’s not an issue anymore, but I will record it if it ever appears again, always better than describing!

1 Like

I can actually corroborate these oddities too. I’ve had the same. Some times the audio engines generated clean sound, but the input was aliased. But I had the output/engine sounds be affected in similar ways once or twice.

@zebra another data point re aliasing / distortion sound; I’ve been seeing it intermittently when using softcut:

  • it appears briefly (~0.25 - 1.25 seconds) then self resolves
  • only affects the real-time incoming sound
  • does not appear in the softcut voice playback of the sound
  • no obvious repeatability or causal situation

you mean you hear this on the “monitor” route, but softcut playback is clean??

and when softcut is not doing anything, the monitor route is clean???

this is the weirdest one yet.

it is sounding like possibly a JACK issue (underruns? though on my single observation there was very low CPU load - no softcut, no engine.) some JACK connections get munged for some reason?

those affected might try changing buffer size in /etc/systemd/system/norns-jack.service.

also, this is gonna sound dumb, but: is there a cell phone or something next to the norns? sometimes i use the phone as hotspot during development and it blasts sporadic digital gunk into the audio.

@zebra, edit below following a quick check on norns. I think I need to make some more careful observations here before before I describe this as clear.

Yes. EDIT --> . . and also no. Sometimes the input is not clean but is clean when played back by softcut, sometimes softcut is not clean when the input was clean. I haven’t yet had a clear example of unclean input played back as unclean by softcut. I thought maybe it was an overloading or something when sounds were piling up, but I saw a clear example while watching the output levels screen where an unclean soft cut playback occurred when the output was only ~50%; this one was with no additional input being played.

Not sure. Softcut was continuously playing back in my observations, so monitor route was clean and intermittently not clean with softcut actively playing.

1 Like

To be honest I can’t remember. I am sure that a power cycle via sleep addressed the problem.

no worries, I didn’t take it like that at all. just figured y’all were busy enough. but I wanted to chime in again while the topic was current!

I need to check which processes get reset via system menu. not sure it restarts jack, but that would make sense to do.

It does restart norns-jack.service, but not norns-crone.service.

New discovery re distorted inputs: scripts play the recorded material fine. Tape plays same files distorted…

Can you record the 2 and post it here?

…same file played via tape and then via timber

Hello, got a question here:

I’ve been getting an issue of

error: Supercollider fail

It just occurs at startup some times. Reset, or just putting to sleep and waking it up doesn’t just “fix it.” Instead, if I cycle a few times, it will eventually go back to normal for a while, then the issue returns a few uses later.

It usually occurs after using Takt, but that just might be the case because I’ve been using that script the most the last few days.

When I attempt to load up a new script, I hang at “loading…”

Maiden doesn’t show any specific issues there, instead just says that it cleaned up and is beginning to run whatever script I just chose.