#41

Yeah, I’m running at 48 PPQN. Thanks so much for the script example! I’ll try implementing this logic tonight and see what happens.

2 Likes
#42

for sure! ymmv, you might need to add some additional logic to reign things in (i’m actually finding better results with 1.5/t.resolution, otherwise it gets caught in a lil loop and ends up pulling off a full beat – i updated the file above), but it’s a start – running 480bpm on link over public wifi and we’re in sync for 1400 bars and counting! :slight_smile:

edit: here’s maybe an even more adaptable version synced-test-maybe-best-who-knows.lua (2.4 KB)

3 Likes
#43

Hi,

The version is 1.3.1
I’ll try the latest update and report back. Norns clock was set to midi. Looking at your subsequent posts I think the sync problems were worse with my set up. I was sending midi clock from Bitwig and the sync would go noticeably out over say 16 bars. Of course I can use Norns as clock source so it’s not such a big deal.

Thanks for looking into this!

#44

I just updated to 1.3.5 and I’m still seeing the unresponsive behaviour when loading saved instances. If noone else is reporting this I guess it may be a quirk of my setup.

To reproduce - presuming you have saved a performance in GridStep:

  1. In GridStep screen 1 select Load
  2. UI displays list of saved files but no longer responds to input from buttons or encoders

To workaround:

Press K1 twice. Screen is now black, but turning E2 prompts redraw of list of saved files and selection is now possible.

For context, I’m using Norns Shield and Neotrellis Grid, so full DIY. Norns version appears to be 201029. Perhaps I should try updating that.

1 Like
#45

There might be an error with the save file, try saving from a new project, then load the newly saved project and see if it’s still freezing. Also if you could do this with maiden open and send me any errors you see it would be helpful.

#46

I updated to the latest version of Norns and now the unresponsive behaviour has disappeared. Sorry to waste your time on that one, I think it was a quirk of my system*. One less thing to worry about though!

The sync to external midi clock behaviour remains the same as before.

*(In particular, FAO NeoTrellis users, when patching after updating Norns to add support for the NeoTrellis grid, running ./waf to build the code seems to fail numerous times here. It has to be rerun 2 or 3 times to complete all steps. So I’m guessing my codebase was not properly built last time.)

1 Like