ghc: bind: resource busy (Address already in use)

[jwaldmann]

when I start tidal-0.2.7 (via C-c C-s) I get

...
Loading package io-streams-1.1.2.0 ... linking ... done.
Loading package websockets-0.8.0.0 ... linking ... done.
Loading package tidal-0.2.7 ... linking ... done.
Couldn't CcoounClnodeuCnclo'tCdut onl tCu'dcooltnCou d 'onltncCtunde'oo lenmCtnucdc'poC nltidaoln>\
t touocedn'   luocnnttccdlnt'e oolndn tcc no'net totnct'coc neek tt otnmc,c  tnoept octen co snoom\
ett ttnn pce coaentotmtl rcee  pootttcmcto cei tplo tkmnt oo ce,pgot ctlm o  ockeops lt l,mcotcoet\
o pk alcmecso,croapmkt  ltclop,acsoik  o rltcn,cc stoakg llcticr, soolankt ltccorg,isoakkct  ntcr.\
,kilsgaat. ,not rli
s gcalt nts aroicgatlltcnl rao iagoltrccnl coitalg lkcnilo co.agn cllc.l gckooa
 l l.cclcghc: bind: resource busy (Address already in use)
olo.ak lcoc
l.coack ghc: bind: resource busy (Address already in use)

I can run tidal in ghci just fine, as in

ghci -XOverloadedStrings
:m Sound.Tidal.Dirt
d1 <- dirtstream "d1"
d1 $ sound "sid/6 (sid/5 (sid/3 sid/2))"

althoug it says

Couldn't connect to tempo clock, starting local clock..

[yaxu]

Thanks, replicated this.. Having a look now.

[yaxu]

I think this is harmless. Emacs starts ten threads running at once. If there isn't a tempo clock, they all try to start one up, then connect to it (all printing a message at once, hence all the garbage). All of them fail except one, but then they all try to connect again and silently succeed. I'll tidy this up at some point soon though, along with the prompt which has got too long..

[jwaldmann]

Ah! - I thought "resource busy" was a critical error, so I never followed it up with C-c C-c, which does actually work.