#2246

can’t believe I missed that! thank you v much for the link!

1 Like
#2247

eh, little elves always chipping away, hard to keep up

1 Like
#2248

Yes, removing a network interface while the system is running is a great way to cause huge problems, with all the system components that use networking…

I guess reinstalling image can’t hurt anything.

I’ll keep saying this one thing: don’t use the hard reset button if there is any way to avoid it. If you use that a lot your disk will die .

1 Like
#2249

Thanks, this got me hacking in my lunch break. 2011 MacBook unibody running El Capitan

Update: spoke to soon, keeps dropping after a few minutes and ipv4 does not seem to be assigned. This is a fates Norns clone for reference

#2250

hypothesis:

i think we might be seeing some general audio dropouts after recent updates from adding network filesharing services.

it makes sense that with maiden and samba running, many threads are created and could easily crowd onto the crone and scynth processors.

so… maybe something to keep in mind / check for when you notice dropouts?

my strategy is:

  • use a strong network adapter (ethernet or panda) at home in “development mode”

  • in “performance mode”, all network devices are disconnected. login with serial and use vim if i need to make a quick change. remember to go back online regularly to synchronize time.

…maybe there should be a mechanism to toggle networking and related services from within the norns menu?

3 Likes
#2251

@zebra i’ve likewise been thinking about this— initially in the context of wanting the bootup time to be faster.

explicitly enabling networking seems like not an unreasonable step.

2 Likes
#2252

I was helping another user get started with maiden and it looked like he might have had some poor network connectivity issues. The first time he created a file he could not save or execute and on page reload the file disappeared. I was worried he had bad fs permissions but everything worked as expected on the second try.
Matron REPL did not show the reconnect message.
He also confirmed he has poor WiFi in his studio. I did suggest a physical connection might be less problematic.

Does (or could) the code editor in maiden have some “offline” capability to hang on to changes if network drops?

#2253

Hey guys.

I recently start to experience an issue when I’m using Grid in conjunction with Norns.

My grid does the sudden flash of some lights when connected, but it otherwise becomes unresponsive, no lights, the pads becomes unresponsible, nothing. I get repeated disconnects and reconnects of the Grid, and this causes Norns to lock up entirely. I connected the same Grid and cable on my Ansible and everything looks to be running without any issues, even when physically disconnecting and reconnecting.

Any thought on why this is happening?

#2254

@RamnFassn Just here to say that I have experienced this couple of days ago. Most recent firmware. I was not able to figure out why this happened. Thought it was related to my using Cheat Codes at the time, but am not sure.

1 Like
#2255

Yeah, I’ve experienced this odd behavior using mlr as well as cheat codes. I’m also not sure if it was something related to my using of these scripts or a filesystem corruption.

#2256

sorry to hear about the troubles. good to know it’s with mlr and cheat codes – does it happen with any non-softcut scripts? any additional info about reproducing? does it happen during use or upon script load? while performing a specific action?

also, are you seeing any maiden output about libmonome errors?

#2257

In my case it was definitely during Cheat Codes use.

#2258

hopefully a one-off for you, but please keep us updated if any additional troubles arise! it’d be great to be able to track it down – seems pretty rare so far, but super undesirable. any steps to reproduce or even frame what’s going on before it happens would help.

fwiw, both cheat codes and mlr redraw on grid every 20ms. shot in the dark, maybe metro failures are causing wonkiness?

I have found that keeping the on-board reverb and compressor off can reduce the CPU utilization with cheat codes by ~50%. I’ll also be adding a toggle for the delay so that you can shave another few points if you don’t want to use it :slight_smile:

#2259

were you both powering the norns externally at the time?

i’d generally suggest keeping the norns externally powered when using grid applications. there might be cases where the battery might not be able to keep up and the CPU may trip a bit.

1 Like
#2260

Yes: my norns was externally powered at the time.
Stayed powered in the studio pretty much all the time.

#2261

What version grid?

Do you have an offworld to try by any chance? (Usb power splitter)

USB cable quality can also sometimes be an issue with power delivery. Trying a different cable might be a good Thing to try if this happens again.

#2262

It happened during mlr and cheat codes use so far. I tried loading Awake and let it run for half an hour and everything seems to work as expected.

I don’t see any maiden output about errors, where should I look to find those?

Same here, my Norns also was externally powered at the time.

It’s the latest iteration - bright warm white lights.

Also tried using the usb splitter connected to an external power brick, same thing happens.

#2263

just in maiden’s main REPL when you connect to norns.local — any status messages will print there

thanks for the detail! are reverb and compressor on as well? for cheat codes (and generally) it might be worth disabling if you’re having performance trouble with a softcut-heavy script.

1 Like
#2264

Ok, so I just tried that and Norns locks up in the booting particles screen

#2265

@RamnFassn just to confirm, is this a norns, norns-shield, or fates? have you updated to 200106? what is plugged in on boot?