I've mostly used tidal on #! (CrunchBang) Linux with no problems except for my own lack of expertise in emacs. Yesterday morning I successfully installed tidal, dirt et al. on OS X Mavericks [10.9] and have been using it in the terminal. (I prefer the -nw mode of emacs; more straightforward.)
However, I've noticed that after 15-20 minutes of use, sample playback starts to drift out of sync - for instance, a simple rhythm like house [sn house] becomes something more like house [sn house ~] - something like 6/4 time rather than 4/4.
house [sn house]
house [sn house ~]
I'm not sure that this is necessarily a problem with tidal - I don't know what handles synchronisation. However, tidal and dirt are both at the same version on #! and OS X - respectively, cabal tidal 0.2.13 and tidalcycles/Dirt@4da850a - so I wonder if the issue may be with jackd or the coreaudio backend?
I will continue using OS X as my "scratch" for now, and record on #!...
Quick note: I have been using emacs with GUI on #! up to now, and have only just switched to -nw emacs on #! so I guess the coding environment is also a variable (even if it doesn't seem like it's relevant to the issue at hand.) I better get some sleep now after working late and then playing with tidal all evening, but I'll make sure this week to see if I can replicate this in Linux too or find that it really is specific to OS X.
I forgot to come back to this after some recording last week: the drift is definitely only happening in OS X, and not in Linux.
Interesting, I think it must be to do with the way that scheduling works in Dirt. Porting dirt to portaudio will help.
Oh man, compiling portaudio on Mavericks is problematic... but OK... I'll try to force myself through it one day and see if it works any better :)
Ah, I was thinking portaudio would make things easy..
Just confirm that this does seem to be a problem with the way dirt does scheduling..