#45

I am getting tempo control just fine. Just not start/stop.

I see 2 Links in the Ableton top left corner. Is that the norns node thingy?

EDIT - where can I debug the start/stop from Link? I don’t see anything super obvious in clock.lua

testing with: Torii

#46

yes, it’s alright.

do you have link start/stop sync enabled in the ableton client?

the relevant code is in matron/clocks/clock_link.c

1 Like
#47

Oho… I don’t see this as a preference. Is this perhaps a Live 10 feature? (I am on Live 9.7.7 Suite)

looks like thats it:

Link currently provides tempo sync and a grid to which apps can align. In Live 9, there are no Song Position or Start/Stop messages sent via Link, nor can any other MIDI data be sent. In Live 10 the feature “Start Stop Sync” additionally shares Transport Start and Stop Commands.

Might call for a FAQ item (alerting señior @dan_derks)

1 Like
#48

sounds good - thanks for the thorough insight!

#49

2 posts were merged into an existing topic: Different MIDI in/out devices Norns

#50

I’m getting some weird behavior with clock.sync

when x = 2, I get a beat pattern of 2,2,1,3 in lengths. when x = 1, I get the expected pattern of 2,2,1,1. I’m assuming it’s an issue of the first sync after the loop missing the sync.

function test()
  while true do
    clock.sync(2)
    engine.trig(0)
    clock.sync(2)
    engine.trig(0)
    clock.sync(1)
    engine.trig(0)
    clock.sync(x)
    engine.trig(0)
  end
end
1 Like
#51

Right, this is a known issue that has now been fixed and the fix will be released with the next update.

4 Likes
#52

What’s the ETA of the next release?

#53

So I’m building a good old fashioned sequencer, and I came onto this “issue” which is probably just a design mishap on my part…

Say I have two sequences, both 16 steps long and running at 1/4 rate with each step playing its note after a clock.sync(1/4). I want to change one of them to 1/2, run it a while and then go back to 1/4. I noticed that if I change the rate to one of them it gets out of sync, as if the clock was clearing and restarting. It could be snapping to the nearest 1/4 pulse but it sounds like it’s smaller than the 1/4 step length.

Two possible solutions I can think of:

  1. sync the rate change to a master clock that always runs. Can I target a specific clock routine once it has been associated to a global var somewhere else in my script?
  2. Use only a master clock for all sequences and bang the note events at specific time “intersections“ using % - that would ensure a strict adhesion of all sequences to the global grid.

What do you think? I should be able to extract the portion of code from the rest of the script and post it here if needed.

#54

well, the point of clock.sync is to ensure that your code stays synchronized with the beat, so it mustn’t get out of sync :slight_smile: (not even if you restart the coroutines or change sync rates on the fly). but i’m not sure i understand your issue correctly, it would be good if you could provide a minimal code sample where it can be reproduced.

#55

Thanks! I hope this makes it clearer:

#56

so i press button 3 and get no sound, how exactly can i reproduce the issue?

#57

press button 2 to randomize the pattern first! otherwise no notes in the pattern :sweat_smile: oopsie

#58

for example:

  1. key2 to randomize tr.1
  2. change track with enc1, then key2 to randomize tr.2
  3. set both patterns’ step length to 0.5 with enc2
  4. press key3 to play
  5. change step length of tr.1 to 0.333, then back to 0.5
  6. patterns seem to have different start times than before

Example 2:
Two sequences are set with rates of 0.5 and 0.25, press key3 to toggle play a few times. They get synced slightly differently each time, but the notes should be overlapping every time (sequence 1 should play one note every two notes of sequence 2).

1 Like
#59

ok, so it seems that you’re misusing clock.sync here.

since note_on is not a coroutine, clock.sync will indirectly cause the external coroutine (in your case step) to suspend again, potentially causing the issue you described. double syncing seems to be unnecessary here.

i haven’t looked deeper in the code, but removing sync call from line 82 seems to resolve the issue for me. hope this helps!

2 Likes
Norns BeatClock & Swing
#60

Sorry if i have missed this…
Can link clock send star / stop commands or star play on next bar?
Im playing with some scripts that have link implemented but i doesnt seem to have that feature,
Thanks!

#61

from ableton? which version? Live 9 does not send start/stop over Link

see Norns: clock above

#62

Thanks @okyeron im using ableton 10, so i think that is not the problem.
I think im getting confused with the settings of link quantum and reset, on the settings page.
What do this do?
Thanks for your help!

1 Like
#63

Working on a test script with midi clock and seeing some weird behavior.

I get inconsistent looking timing while simply trying to make a graphic blink on the norns display in time with midi clock. I’m testing with midi clock being sent from a TR-09 drum machine over USB-midi.

In the following, the on screen box blinks OK, but sometimes stays on for more than a beat. The print output to maiden for my blink flag seems super inconsistent watching it go by in the REPL. I feel like it should be printing right on the beat, but it stutters.

issue is more apparent at slower tempos like 40-80

Am i doing something stupid/wrong here or is this some deeper issue?

test script:

local blinker = false

function init()
  midi.connect()
  params:set("clock_source", 2)
  clock.run(blink)
end

function blink()
  while true do
    clock.sync(1/2)
    blinker = true
    redraw()
    
    clock.sync(1/2)
    blinker = false
    redraw()
  end
end

function redraw()
  screen.clear()
 
  if blinker then
      screen.level(12)
      screen.rect(52, 20, 24, 24)
      screen.fill()  
      -- screen.pixel(112, 6)
  else 
      screen.level(1)
      screen.rect(52, 20, 24, 24)
      screen.fill()  
  end
  print(blinker)
  
  screen.stroke()
  screen.update()
end
#64

Will try to test MIDI sync tomorrow, but I wonder if this could be related to wonkiness I experienced using crow clock in. Norns scripting - Link + syncing bar starts (global clock)