That's good news, because currently there's no tempo sharing working in the 1.0.0 beta (even between processes on the same computer). On Tue, 4 Dec 2018, 19:52 Ogborn, David, <ogbornd(a)mcmaster.ca&gt; wrote: > Hi Gil, > > Actually I have quietly been working on that but am not quite there - I > made something a week ago I thought should work but it didn't quite work > (doesn't work in performance). Hoping to get back to figuring out what is > missing here within the next week... > https://github.com/d0kt0r0/Tidal/blob/master/src/Sound/Tidal/EspGrid.hs > > -D > > ------------------------------ > *From:* Gil Fuser [gilfuser(a)gmail.com] > *Sent:* Tuesday, December 04, 2018 12:31 PM > *To:* TidalCycles > *Subject:* [tidal] Re: Sync Td<>SC with EspGrid > > Hi David. > How about using EspGrid with Tidal 1.0.0? Would it work? > I see that there's a file EspGrid.hs inside Tidal/src/Sound/Tidal/old. > So, I think it would work. > > best regards, > Gil > > On Sat, Nov 24, 2018 at 7:12 PM Ogborn, David <ogbornd(a)mcmaster.ca&gt; > wrote: > >> Hi Konstantinos, >> >> If you’re using Atom and Tidal 0.9.10 (which is what you’d get if you >> installed Tidal via cabal install right now) then the following should work. >> >> (1) Save the following startup routine in a file called BootTidal.hs and >> put it in a folder somewhere: >> :set -XOverloadedStrings >> :set prompt "" >> :module Sound.Tidal.Context >> >> (cps, getNow, getTempo) <- cpsUtilsEsp >> >> (d1,t1) <- superDirtSettersEsp getNow >> (d2,t2) <- superDirtSettersEsp getNow >> (d3,t3) <- superDirtSettersEsp getNow >> (d4,t4) <- superDirtSettersEsp getNow >> (d5,t5) <- superDirtSettersEsp getNow >> (d6,t6) <- superDirtSettersEsp getNow >> (d7,t7) <- superDirtSettersEsp getNow >> (d8,t8) <- superDirtSettersEsp getNow >> (d9,t9) <- superDirtSettersEsp getNow >> >> let bps x = cps (x/2) >> let hush = mapM_ ($ silence) [d1,d2,d3,d4,d5,d6,d7,d8,d9] >> let solo = (>>) hush >> :set prompt "tidalEsp> " >> >> (2) Open that folder (not the file) with Atom. A new Atom window will >> open with that folder as the focus of >> >> (3) Start the EspGrid app (I just tested with the 0.58.2 binary release) >> and turn the tempo on (the checkbox). >> >> (4) Open or save a file in atom with the extension .tidal, then boot >> tidal cycles from the atom menu. You’ll know that you got the alternate >> setup if you see the prompt “tidalEsp>” instead of “tidal>” in the post >> window. >> >> You should be able to (a) change the tempo in the EspGrid app and hear >> the difference in playing patterns; and (b) change the EspGrid tempo with >> cps in atom. If, instead, you want to change the tempo from SC: >> >> t = TempoClock.default = EspClock.new; // do this just once >> t.tempo = 1.5; // or whatever - you should see the change in the app, >> hear it from your running Tidal patterns >> >> Things might be a bit fragile because this doesn’t get tested much and >> Tidal has continued to change since I first contributed stuff that, >> crudely, showed how Tidal could be synced with EspGrid. Good luck, and >> happy to help more, or help adapt to different scenarios! >> >> Yours truly, >> David >> >> On Nov 23, 2018, at 1:04 PM, Konstantinos Vasilakos < >> konstantinos.vasilakos(a)gmail.com&gt; wrote: >> >> Hi David, >> >> Thanks for offering to help. I am trying to make tidal and sc share same >> clock (locally); I am under the impression that this is done with EspGrid >> and its Quark, right? Or is it used only for outside local setups. >> >> By changing tempo from EspGrid app window then I should expect to >> control both I hope, or maybe I am missing something here. >> >> K. >> >> >> *Save our in-boxes! *http://emailcharter.org >> >> >> On Fri, 23 Nov 2018 at 20:15, Ogborn, David <ogbornd(a)mcmaster.ca&gt; wrote: >> >>> Hi Konstantinos, >>> >>> Not super sure what the question is but I’m happy to help you get >>> things working over this weekend (today is fully booked though). Maybe >>> start a chat on the live coding slack about it, either direct message or in >>> the #synchronization channel? >>> >>> -D >>> >>> On Nov 23, 2018, at 11:36 AM, Konstantinos Vasilakos < >>> konstantinos.vasilakos(a)gmail.com&gt; wrote: >>> >>> Hey all, >>> >>> Is this the latest regarding syncing these two or something else I am >>> missing. >>> >>> Thanks >>> K. >>> >>> >>> *Save our in-boxes! *http://emailcharter.org >>> _______________________________________________ >>> TidalCycles mailing list -- tidal(a)we.lurk.org >>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>> >>> >>> _______________________________________________ >>> TidalCycles mailing list -- tidal(a)we.lurk.org >>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>> >> _______________________________________________ >> TidalCycles mailing list -- tidal(a)we.lurk.org >> To unsubscribe send an email to tidal-leave(a)we.lurk.org >> >> >> _______________________________________________ >> TidalCycles mailing list -- tidal(a)we.lurk.org >> To unsubscribe send an email to tidal-leave(a)we.lurk.org >> > _______________________________________________ > TidalCycles mailing list -- tidal(a)we.lurk.org > To unsubscribe send an email to tidal-leave(a)we.lurk.org > _______________________________________________ TidalCycles mailing list -- tidal(a)we.lurk.org To unsubscribe send an email to tidal-leave(a)we.lurk.org

Hi David. It's already there! Cool! How can we use it? The code above on this post won't work. Thank you! best regards, Gil On Wed, Dec 5, 2018 at 1:40 PM Gil Fuser <gilfuser(a)gmail.com&gt; wrote: > "That's good news" + 1 > I'm willing to test it when you have something ready to. > Good work. > > best regards, > Gil > > On Wed, Dec 5, 2018 at 6:48 AM Alex McLean <alex(a)slab.org&gt; wrote: > >> That's good news, because currently there's no tempo sharing working in >> the 1.0.0 beta (even between processes on the same computer). >> >> On Tue, 4 Dec 2018, 19:52 Ogborn, David, <ogbornd(a)mcmaster.ca&gt; wrote: >> >>> Hi Gil, >>> >>> Actually I have quietly been working on that but am not quite there - I >>> made something a week ago I thought should work but it didn't quite work >>> (doesn't work in performance). Hoping to get back to figuring out what is >>> missing here within the next week... >>> https://github.com/d0kt0r0/Tidal/blob/master/src/Sound/Tidal/EspGrid.hs >>> >>> -D >>> >>> ------------------------------ >>> *From:* Gil Fuser [gilfuser(a)gmail.com] >>> *Sent:* Tuesday, December 04, 2018 12:31 PM >>> *To:* TidalCycles >>> *Subject:* [tidal] Re: Sync Td<>SC with EspGrid >>> >>> Hi David. >>> How about using EspGrid with Tidal 1.0.0? Would it work? >>> I see that there's a file EspGrid.hs inside Tidal/src/Sound/Tidal/old. >>> So, I think it would work. >>> >>> best regards, >>> Gil >>> >>> On Sat, Nov 24, 2018 at 7:12 PM Ogborn, David <ogbornd(a)mcmaster.ca&gt; >>> wrote: >>> >>>> Hi Konstantinos, >>>> >>>> If you’re using Atom and Tidal 0.9.10 (which is what you’d get if you >>>> installed Tidal via cabal install right now) then the following should work. >>>> >>>> (1) Save the following startup routine in a file called BootTidal.hs >>>> and put it in a folder somewhere: >>>> :set -XOverloadedStrings >>>> :set prompt "" >>>> :module Sound.Tidal.Context >>>> >>>> (cps, getNow, getTempo) <- cpsUtilsEsp >>>> >>>> (d1,t1) <- superDirtSettersEsp getNow >>>> (d2,t2) <- superDirtSettersEsp getNow >>>> (d3,t3) <- superDirtSettersEsp getNow >>>> (d4,t4) <- superDirtSettersEsp getNow >>>> (d5,t5) <- superDirtSettersEsp getNow >>>> (d6,t6) <- superDirtSettersEsp getNow >>>> (d7,t7) <- superDirtSettersEsp getNow >>>> (d8,t8) <- superDirtSettersEsp getNow >>>> (d9,t9) <- superDirtSettersEsp getNow >>>> >>>> let bps x = cps (x/2) >>>> let hush = mapM_ ($ silence) [d1,d2,d3,d4,d5,d6,d7,d8,d9] >>>> let solo = (>>) hush >>>> :set prompt "tidalEsp> " >>>> >>>> (2) Open that folder (not the file) with Atom. A new Atom window will >>>> open with that folder as the focus of >>>> >>>> (3) Start the EspGrid app (I just tested with the 0.58.2 binary >>>> release) and turn the tempo on (the checkbox). >>>> >>>> (4) Open or save a file in atom with the extension .tidal, then boot >>>> tidal cycles from the atom menu. You’ll know that you got the alternate >>>> setup if you see the prompt “tidalEsp>” instead of “tidal>” in the post >>>> window. >>>> >>>> You should be able to (a) change the tempo in the EspGrid app and hear >>>> the difference in playing patterns; and (b) change the EspGrid tempo with >>>> cps in atom. If, instead, you want to change the tempo from SC: >>>> >>>> t = TempoClock.default = EspClock.new; // do this just once >>>> t.tempo = 1.5; // or whatever - you should see the change in the app, >>>> hear it from your running Tidal patterns >>>> >>>> Things might be a bit fragile because this doesn’t get tested much and >>>> Tidal has continued to change since I first contributed stuff that, >>>> crudely, showed how Tidal could be synced with EspGrid. Good luck, and >>>> happy to help more, or help adapt to different scenarios! >>>> >>>> Yours truly, >>>> David >>>> >>>> On Nov 23, 2018, at 1:04 PM, Konstantinos Vasilakos < >>>> konstantinos.vasilakos(a)gmail.com&gt; wrote: >>>> >>>> Hi David, >>>> >>>> Thanks for offering to help. I am trying to make tidal and sc share >>>> same clock (locally); I am under the impression that this is done with >>>> EspGrid and its Quark, right? Or is it used only for outside local setups. >>>> >>>> By changing tempo from EspGrid app window then I should expect to >>>> control both I hope, or maybe I am missing something here. >>>> >>>> K. >>>> >>>> >>>> *Save our in-boxes! *http://emailcharter.org >>>> >>>> >>>> On Fri, 23 Nov 2018 at 20:15, Ogborn, David <ogbornd(a)mcmaster.ca&gt; >>>> wrote: >>>> >>>>> Hi Konstantinos, >>>>> >>>>> Not super sure what the question is but I’m happy to help you get >>>>> things working over this weekend (today is fully booked though). Maybe >>>>> start a chat on the live coding slack about it, either direct message or in >>>>> the #synchronization channel? >>>>> >>>>> -D >>>>> >>>>> On Nov 23, 2018, at 11:36 AM, Konstantinos Vasilakos < >>>>> konstantinos.vasilakos(a)gmail.com&gt; wrote: >>>>> >>>>> Hey all, >>>>> >>>>> Is this the latest regarding syncing these two or something else I am >>>>> missing. >>>>> >>>>> Thanks >>>>> K. >>>>> >>>>> >>>>> *Save our in-boxes! *http://emailcharter.org >>>>> _______________________________________________ >>>>> TidalCycles mailing list -- tidal(a)we.lurk.org >>>>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>>>> >>>>> >>>>> _______________________________________________ >>>>> TidalCycles mailing list -- tidal(a)we.lurk.org >>>>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>>>> >>>> _______________________________________________ >>>> TidalCycles mailing list -- tidal(a)we.lurk.org >>>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>>> >>>> >>>> _______________________________________________ >>>> TidalCycles mailing list -- tidal(a)we.lurk.org >>>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>>> >>> _______________________________________________ >>> TidalCycles mailing list -- tidal(a)we.lurk.org >>> To unsubscribe send an email to tidal-leave(a)we.lurk.org >>> >> _______________________________________________ >> TidalCycles mailing list -- tidal(a)we.lurk.org >> To unsubscribe send an email to tidal-leave(a)we.lurk.org >> >