#409

everybody’s grids are still working on update 180828?

my norns will detect the grid, serial number, size, etc. in the new systems menu device setting under grid, but then no matter what scene i load up there are no lights or button presses detected, etc. tried several grids and 2 different norns with the new update…

maybe i’m missing something in the new update where i have to toggle something new to get the grid to talk to the script?

#410

Grids are working fine for me, outside of using grid and midi at the same time… which I think is a known bug.

1 Like
#411

shit, still no luck here with grids being responsive. tried to revert to the previous firmware via usb, no luck there. will have to dig deeper later tonight with a manual revert unless more ideas turn up here as to what might be going on…

#412

I had a similar problem here

A pull of the latest norns, norns-image and dust, including reinstalling them fixed my problem.

YMMV

2 Likes
#413

@instantjuggler could you check the debug output?

get your norns in hotspot mode. connect to it with your computer. run maiden (go to 172.24.1.1 in web browser)

connect a grid
run awake

post any errors shown in the bottom panel of maiden

@dan_derks does this error get thrown in you run a non-softcut script before mlr? seems this is a leftover-globals issue, we’ll get the globals-protection implemented in the next update for better inter-script sanity

#414

no errors shown that i can see!

Summary

Selected interface ‘wlan0’

wpa_state=SCANNING

ip_address=172.24.1.1

p2p_device_address=40:a5:ef:dc:4b:ad

address=40:a5:ef:dc:4b:ad

uuid=edc79a8c-2bd5-58c5-84c1-9d7065db5634

Selected interface ‘wlan0’

wpa_state=SCANNING

ip_address=172.24.1.1

p2p_device_address=40:a5:ef:dc:4b:ad

address=40:a5:ef:dc:4b:ad

uuid=edc79a8c-2bd5-58c5-84c1-9d7065db5634

folder

path: /home/we/dust/scripts/tehn/

script load

cleanup

script clear

script run

loading engine; name: PolyPerc

Engine.register_commands; count: 6

— engine commands —

amp (f)

cutoff (f)

gain (f)

hz (f)

pw (f)

release (f)

— polls —

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

tape_play_pos

tape_rec_dur

script init

grid/seek

reconnecting grid…

reconnecting midi…

READING PMAP

grid added: 1 monome 128 m1000093 m1000093

look like grid is detected just fine?.. but then no lights on grid, and no button responses.

#415

negative. fwiw, it works fine moving from loops or half second. only from cranes, which has a ton of engine stuff in the init script — and only after i try to execute a command line engine.env_time in cranes (which also errors similarly, but in cranes). i’ll try a fresh install of everything tonight (is there an existing walkthrough for this? :grimacing:) and report back.

#416

@instantjuggler in SYSTEM > DEVICES > MIDI are the defaults still set? (try setting port 1 to “all”)

@dan_derks hold on, let me do some testing before you try to reinstall things!

1 Like
#417

@dan_derks

i believe there’s probably an error in your WIP script. something like

engine.env_time = 2 -- THIS IS WRONG

instead of

engine.env_time(1,2) -- CORRECT

but i’m confused, because i thought an engine reload would redefine all of the params. dm your script?

1 Like
#418

yes, midi is set to default “all.”

man i don’t get this at all, but i must have messed something up since both norns behave the same.

is there any simple way to revert back to the previous firmware via usb or maiden or try to reinstall the current firmware with a new download of it?

#419

@instantjuggler e-mailing you

1 Like
#420

What’s the correct way to get the grid size with the new methods after doing grid.connect() ?

#421

the virtual port system sortof lost this functionality unfortunately, but @jah and i have been discussing how to re-introduce it. main problem is “all” won’t have a definitive size… perhaps the most-recent registered grid can pass its size to the virtual port? and then we can expose width/height attributes for the port?

#422

Ah OK, yeah maybe a size function can return a table so that all can return an array of all the grid sizes.
Or just an easy way to get the devices themselves that are connected to a virtual port could work.

#423

i can confirm the issue with the KarplusRings.sc engine knocking out the sound output with bpf_res set to 0, and if you do the reverse (bring bpf_res to the max of 4 with the bpf_freq very high) there can be some really sustained noise that may or may not require a reboot to clear out (watch out for speakers/headphones).

there are probably other solutions, but for me one quick way to deal with this is to edit the min/max values for bpf_freq and bpf_res in scripts using the KarplusRings.sc engine to tame the white noise that excites the resonator. here are the values that seem safe so far:

cs.BPF_FREQ = cs.new(100,9000,'lin',0,0.5,")

cs.BPF_RES = cs.new(0.05,2.5,'lin',0,0.5,")
2 Likes
#424

@doublecoolbossman

i’ve just confirmed that we somehow broke TAPE functionality. we’re working on fixing it right away. so it’s not just you.

many apologies!

2 Likes
#425

for me its STEP that has stopped working…no lights on grid, no sound.

#426

Thanks for the update! No worries!

#427

hm. just checked this out. try reattaching the grid, does it help?

#428

Unplugging and replugging the grid has helped me get out of a number of bad spots lately. Weird.

2 Likes