TidalCycles version 1.10.1 Link troubles

Hi,

I'm running Tidalcycles 1.10.1 and I'm no nonger syncing to my ableton link devices.
I opened up two other programs (reaper and PD) on the same computer and another computer on the same network running sonicPi, and they all sync.

Tidal does not. It's supposed to work out of the box right? I checked the BootTidal.hs for the "disableLink = true" but it is not there.
I did add something to supercollider lately to have my midi devices sync to the linkclock

~lc = LinkClock.new.latency_(Server.default.latency);
~ltmc = LinkToMidiClock(~scOut, ~lc)
~ltmc.start

Ii can also report the connected peers with it. This is always 1, regardless of the number of link devices in the network, while on the other link devices this is a higher number, but not including tidalcycles

~lc.numPeers;

I don't think this interferes with the tidal link, because I do not load it by default (startup.scd) but It is the only thing that is different from the default install...

How can I debug this? I don't know where to see what is going on. I can chage the tempo using setcps but other devices are not following it. if I do it in other link enabled softwares, everything but tidal follows...

i think since 1.10, the default is to have link turned off, but there should be a function in the new Sound.Tidal.Boot enableLink :: Tidally => IO (), which you should be able to call in your editor, just by executing enableLink after booting tidal. could you check if that works for you?

Hmm, just calling it from the editor gives:

Variable not in scope: enableLink
Warning: GHCi |     Suggested fix:
Warning: GHCi |       Perhaps use ‘cEnableLink’ (imported from Sound.Tidal.Context)

The 1.10.0 release notes and more specific this were helpful though...

-- It has to go after you define 'tidalInst'.
instance Tidally where tidal = tidalInst

-- Uncomment to enable Ableton Link on startup:
-- streamEnableLink tidal

But confused because my bootTidal.hs content is completely different from the new format found here on github
I'm using some extras like connections to other PCs on the network for visuals, So not ready to ditch my old bootTidal.hs completely

I had things like:

tidal <- startStream (defaultConfig {cVerbose = True, cFrameTimespan = 1/20, cCtrlAddr = "0.0.0.0"}) [ 
                                   (pivizTarget, [pivizShape]),
                                   (superdirtTarget {oLatency = 0.0, oAddress = "127.0.0.1", oPort = 57120}, [superdirtShape])
                                   ]

vs

tidalInst <- mkTidalWith [(superdirtTarget { oLatency = 0.01 }, [superdirtShape])] (defaultConfig {cFrameTimespan = 1/50, cProcessAhead = 1/20})

in the new version

but yeah stuff changed, I wasn't aware..
This github issue keeps track of the fact that the documentation needs updating... but the code moved to codeberg...

hmm yes this is a bit of a problem i think, i wouldn’t have thought it’s possible to be on 1.10.x and still be able to use the old boot file somehow. i guess there are two options for you:

  • downgrade to 1.9.5, or
  • use the new bootfile and add your custom stuff to it

it’s probably worth making an issue about this on codeberg