We’ve seen some initial connection issues within the dev crew a couple of times whilst the reception wasn’t very good. I believe just moving norns closer to the accesspoint/router to connect the first time made it work all the time for those cases.

It’s working fine for me with a signal value of ±65 using nmcli device wifi list.

1 Like

Took a second to understand the new script organizing / Library / SFTP vibe but now that I get it, its so great. Much faster and now I am more frequently engaged w/ Maiden. 2.0 is great - thank U all!

5 Likes

Much appreciation for the work that went into 2.0; Arc functionality is great!

13 Likes

@nosollution
cool looking use of the Arc!
looking forward to your app!

1 Like

have to once again say thanks to all who worked hard on this release and updated their apps

honestly still haven’t gotten around to using some code in the library
we are truly spoiled for choice!

10 Likes

What script is that? Hard to see, but real pretty!

Thanks @atomboyd!

It’s a midi-note recorder work-in-progress. The Arc controls an adjustable window that optionally constrains playback and overdubbing to a range within the original full loop. At the moment it just records triggers and note values (i.e. not gates . . . that’s a longer range goal).

1 Like

Very cool, can’t wait to try it out… do you ever have issues of norns restarted when arc and grid are both plugged in?

It’s happened a few times, but not consistently, still pretty new to Arc land though.

I’ve crashed the norns / grid / arc combo due to coding errors and during some high-frequency grid/arc updating situations (< 0.001 s step sizes), but I haven’t 1) purposefully stress tested the set up to try and identify specific update limits for this code or 2) attempted code optimization yet.

I haven’t had norns spontaneously restart, either w/grid/arc or other operation.

:scream:

way too fast. this isn’t a norns bottleneck (unless you were also trying to draw screen or send OSC or something) but a serial port and grid/arc firmware bottleneck.

serial port bandwidth is ~100kb/s
each LED is 4 bits

Thanks @zebra! The numbers help (I think) explain some of the intermittent gremlins I’ve seen. Should I interpret a grid:refresh as 128x4=512 bits in all cases, or does it matter how many LEDs are changing state? Would the ~100kb/s translate directly to some kind of per step burst limit?

Atm, I’m running at 0.01 s base step size with a range of 0.0025-0.03 s to change playback speed and it is running stable with grid/arc during playback, but I am getting the occasional (but unrepeatable) gremlin at 0.0025 s when there is also input on arc or grid.

Grid refresh is actually getting data sent for 256 leds every frame

See https://monome.org/docs/serial.txt and look for prefix/led/level/map

1 Like

Help! I just ran update from the menu item, now after it said complete ,the screen seems to be unresponsive, if i reset then power up, grid sparkles, but nothing on the norns screen… any ideas?

I can connect to maiden, but matron and sc both say they cant connect

edit: serial/manual update fixed it

Just loaded up @zebra’s crown script again and it is the first time I realised that there seems to be some kind of grid function programmed to it but I am unsure what the grid actually does… It seems to capture the softcut buffer somehow?
But maybe it is supposed to remain a mystery since the script is also not in the community catalog. Still curious…

it sets rates, levels, positions and feedback parameters for 4 softcut voices

i should tidy up / document ‘crowns’ and add it to community repo. main thing that bugs me (trivial) is the lack of a proper audio taper for sine levels.

6 Likes

Thanks a lot for your reply, it would be cool to have this script in the community catalog for sure. I really like it a lot like it is, would be cool to be able to map the parameters to external controls (yeah, I should really spend some time trying to learn these things, I know…) but I will check out the grid stuff again. Thanks!

i would really love this! crowns is one of favorite scripts

one thing i’ve always wondered is the input pitch tracking fully implemented? or is that just the beginning of that idea in the code?

Pitch tracking should work, is central

1 Like

wow i finally figured it out last night :upside_down_face:
great stuff

Ok, I opened the grid cut lua and now it starts to make sense as in “wow, there is another weird world of niceness hiding in that script”…

From the script notes (“note to self”):
top 4 rows: draw current rate index for each voice

bottom 4 rows:
1st column: level
3rd column: freeze
columns 5-8: feed

I am unsure about the feed implementation of 5-8, should there be different divisions or is it % of feedback?