# Testing Tidal 1.7 **URL:** \ **Category:** Uncategorized\ **Created:** [24 January 2021 10:09 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792 "2021-01-24T10:09:41Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 10:09 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/1 "2021-01-24T10:09:41Z")
(We need a forum category for this sort of thing.. Not sure what to call it) The new Tidal and SuperDirt is ready for testing. They should be upgraded together. Here's a thread for people up for trying it out. We can use it to help each other get it installed, try out the features and get things documented. First things first - how to get the cutting edge running. I use Linux, but instructions should be similar for other platforms - please share any os-specific findings! First for superdirt, from a terminal window change into the SuperDirt folder. E.g. under linux that would be: ```haskell cd ~/local/share/SuperCollider/downloaded-quarks/SuperDirt ``` Then get the latest changes, and switch to the development branch: ```haskell git pull git checkout develop ``` If you have changed some files, this might fail. In this case you can run `git stash` to undo your changes (they get backed up somewhere) and try again. > _If you later want to change back to the stable release of superdirt, you can do this:_ > > ```haskell > git checkout master > > ``` The next job is to install the tidal 1.7 release candidate. For simplicity and lack of bugs, I recommend using the old 'v1-' install method with cabal. _For the most predictable experience, it might be best to wipe your haskell packages at this point and start from a clean slate, especially if you have previously installed tidal with the now default 'v2' `cabal install` method. Under linux/mac os can do this by removing the `~/.ghc` and `~/.cabal` folders._ Here's how you install tidal 1.7: ```haskell cabal v1-update cabal v1-install https://hackage.haskell.org/package/tidal-1.7/candidate/tidal-1.7.tar.gz ``` > _If you later want to change back to a previous version of tidal, you can do this:_ > > ```haskell > ghc-pkg unregister tidal-1.7 > > ``` > > _If you started from a blank slate, you can then `cabal install tidal`_ to get the current release. Ok share you experiences with that and I'll later share some fun things to try.. ---
**Author:** ![nilhartman](https://uzu.lurk.org/user_avatar/uzu.lurk.org/nilhartman/32/957_2.png) [@nilhartman](https://uzu.lurk.org/u/nilhartman)\ **Post date:** [24 January 2021 11:07 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/2 "2021-01-24T11:07:27Z")
Fantastic news, I'll install it this afternoon. I have no clue what's new / updated but I'm thrilled to give it a try ! ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 11:49 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/3 "2021-01-24T11:49:46Z")
Ok here's the main thing to try, control busses. This lets you route an effect via a bus. ```haskell -- A simple sax sound d1 $ sound "sax" # legato 1 -- This doesn't do anything different d1 $ sound "sax" # legato 1 # squiz "0 1.5 0 1.5" -- A workaround is to chop up the sounds into parts: d1 $ chop 4 $ sound "sax" # legato 1 # squiz "0 1.5 0 1.5" -- But now you can use a bus to change a single sound while it plays: d1 $ sound "sax" # legato 1 # squizbus 1 "0 1.5 0 1.5" -- You can add a bus to most things but have to take care to give each thing a different bus number: d1 $ sound "sax" # legato 1 # squizbus 1 "0 1.5 0 1.5" # lpfbus 2 "400 2000 3000" # lpq 0.2 -- You can pattern things within bus patterns: d1 $ sound "sax" # legato 1 # squizbus 1 (chunk 4 (fast 4) "0 1.5 0 1.5") -- A big limitation is that bus patterns are monophonic. So if you do some patterning that layers them up, you'll be disappointed with the results: d1 $ jux rev $ s "sax" # ampbus 1 ("[1 0 [1 0] 1]*6") # legato 1 -- A workaround is to add 1 to the bus number, and 0 to the value: d1 $ jux (rev . (|+ ampbus 1 0)) $ s "sax" # ampbus 1 ("[1 0 [1 0] 1]*6") # legato 1 -- Or replace the control using a different bus number with `#` d1 $ jux (rev . (# ampbus 2 "1 0 1 0")) $ s "sax" # ampbus 1 ("[1 0 [1 0] 1]*6") # legato 1 ``` Most things work, but some key things like speed, gain, vowel and note don't. `panbus` will work, but in the range -1 to 1 instead of 0 to 1. Working on this.. (That range would be better in general, as you could multiply patterns to change amplitude) ---
**Author:** ![tedthetrumpet](https://uzu.lurk.org/user_avatar/uzu.lurk.org/tedthetrumpet/32/39_2.png) [@tedthetrumpet](https://uzu.lurk.org/u/tedthetrumpet)\ **Post date:** [24 January 2021 14:32 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/4 "2021-01-24T14:32:20Z")
On mac, deleted `~/.ghc` and `~/.cabal` folders. Now I have, in terminal, `cabal: unrecognised command: v1-update` ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 14:33 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/5 "2021-01-24T14:33:51Z")
Perhaps you have quite an old version of ghc? In that case, miss off the `v1-`, i.e. `cabal update; cabal install https://hackage.haskell.org/package/tidal-1.7/candidate/tidal-1.7.tar.gz` ---
**Author:** ![tedthetrumpet](https://uzu.lurk.org/user_avatar/uzu.lurk.org/tedthetrumpet/32/39_2.png) [@tedthetrumpet](https://uzu.lurk.org/u/tedthetrumpet)\ **Post date:** [24 January 2021 14:35 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/6 "2021-01-24T14:35:30Z")
> [@yaxu](#): > > cabal install [https://hackage.haskell.org/package/tidal-1.7/candidate/tidal-1.7.tar.gz](https://hackage.haskell.org/package/tidal-1.7/candidate/tidal-1.7.tar.gz) Thanks, looks like that's working. I guess the old version of ghc doesn't really matter? ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 14:35 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/7 "2021-01-24T14:35:53Z")
That's right, old versions are fine. ---
**Author:** ![tedthetrumpet](https://uzu.lurk.org/user_avatar/uzu.lurk.org/tedthetrumpet/32/39_2.png) [@tedthetrumpet](https://uzu.lurk.org/u/tedthetrumpet)\ **Post date:** [24 January 2021 14:47 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/8 "2021-01-24T14:47:18Z")
Well I haven't tried any of the new stuff yet, but so far nothing seems to be broken for me at least! All my old files still working, no errors in SC or Atom šŸ™‚ Will test more tonight. ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 14:49 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/9 "2021-01-24T14:49:05Z")
Good to hear! Trying existing stuff to see if it works the same is definitely a good thing for people to do.. ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 15:56 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/10 "2021-01-24T15:56:05Z")
A simpler function that I'm excited about is `press`. In mininotation terms it basically turns every instance of 'a' into '[~ a]'.. Every beat then becomes an offbeat and so the overall effect is to syncopate a pattern. A couple of quick examples: ```haskell d1 $ stack [every 4 (fast 2) $ sound "drum*4" # squiz 1.3 # speed 2, every 2 press $ sound "sd:1*2 sd:4*3 sd*2 sd:2*2" ] d1 $ jux press $ sound "sd:1*2 sd:4*3 sd*2 sd:2*2" ``` Funky times ahead ---
**Author:** ![iii](https://uzu.lurk.org/letter_avatar_proxy/v4/letter/i/ecb155/32.png) [@iii](https://uzu.lurk.org/u/iii)\ **Post date:** [24 January 2021 19:42 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/11 "2021-01-24T19:42:31Z")
I was going to ask about / try and implement a `pressBy` but `press` is just `pressBy 0.5`! Iā€™m looking forward to updating šŸ™‚ great stuff xxx ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [24 January 2021 21:50 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/12 "2021-01-24T21:50:41Z")
Yes that's right! I didn't find good results for values other than 0.5 yet but need to listen deeper.. You can pattern it if you like e.g. `pressBy "<0.5 1%3 0.75>"` (where 1%3 is a third) ---
**Author:** ![polymorphic.engine](https://uzu.lurk.org/user_avatar/uzu.lurk.org/polymorphic.engine/32/30_2.png) [@polymorphic.engine](https://uzu.lurk.org/u/polymorphic.engine)\ **Post date:** [25 January 2021 18:18 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/13 "2021-01-25T18:18:22Z")
I'm super excited ! For me on linux the installation worked perfectly. I did go ahead and delete the ghc and cabal folders before installing. I've tried some of my old code and it seems to work just fine. I espaccially wanted to have this update for smooth panning, so the first thing I tried was something like (water is a long water field recording) ``` once $ s "water" # panbus 1 sine ``` which did'nt work. So I realised that you always have to sample out of the continuos patterns so I tried ``` once $ s "water" # panbus 1 (struct "t*128" $ sine) ``` this works for the first couple of seconds and then it stops. Ofcourse ! Tidal only really sends messages over the first cycle! Then the solution came to me: ``` once $ s "water" # panbus 1 "0" d1 $ struct "t*128" $ panbus 1 $ slow 4 sine ``` This works like I intened. Note that the first block sends the actual message for the sound that plays whereas the second block only sends control messages. I think for the first block it would be cool to have a function panbus' or so that only takes one argument (the busnumber) and no pattern since in that case it doesn't really do anything. I also think that it would be good to introduce an alias for d1 etc. named c1 which can be used to distinguish between busses that produce sound and control only busses. These are just my first thoughts and I'm really happy that this is part of Tidal now! ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [25 January 2021 19:00 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/14 "2021-01-25T19:00:00Z")
Try using `panrecv 1` in the first one - hopefully this is the `panbus'` you're looking for. I might add a sendbus too. Not also that internally pan goes from `-1` to `1`, so you'll probably want to change this to `panbus 1 $ range (-1) 1 $ slow 4 sine` ---
**Author:** ![C-o](https://uzu.lurk.org/user_avatar/uzu.lurk.org/c-o/32/1692_2.png) [@C-o](https://uzu.lurk.org/u/C-o)\ **Post date:** [26 January 2021 14:13 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/15 "2021-01-26T14:13:46Z")
I'm getting some weird results from this: ```haskell d1 $ stutWith 3 (1/16) (|* gain 0.8) $ s "bd*4" ``` The expected result would be for the volume of the stutters to drop by 20% for every stutter but it doesn't seem to have any effect. This works fine though: ```haskell d1 $ stutWith 3 (1/16) (|* speed 0.9) $ s "bd*4" ``` After further investigation this: ```haskell d1 $ s "bd*4" # gain 0 ``` Produces sound so seems like something is up with the gain function as a whole... Could I have messed up the installation somehow? ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [26 January 2021 14:50 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/16 "2021-01-26T14:50:43Z")
Ah, good catch! I have the same. You could try with `amp` in the meantime, although that is scaled a bit differently to `gain`. ---
**Author:** ![msp](https://uzu.lurk.org/user_avatar/uzu.lurk.org/msp/32/1689_2.png) [@msp](https://uzu.lurk.org/u/msp)\ **Post date:** [27 January 2021 15:31 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/17 "2021-01-27T15:31:42Z")
This very cool! Great work šŸ™‚ > [@yaxu](#): > > (We need a forum category for this sort of thing.. Not sure what to call it) Alpha/Beta Testing? > [@yaxu](#): > > Here's how you install tidal 1.7: I installed from source at `d82f68638a622a6707b06fc45d03fa3b8fae0b64` and by cleaning out `~/.ghc` and `~/.cabal` as you suggested. ``` $ cd path/to/tidal/src $ cabal v1-update $ cabal v1-install ``` > [@yaxu](#): > > Ok here's the main thing to try, control busses. This lets you route an effect via a bus. All this is working fine though it didn't immediately click why I need this feature. I guess I just never tried to pattern FX over a single sample, only over cycles. Are there other user cases? > [@yaxu](#): > > A simpler function that I'm excited about is `press`. In mininotation terms it basically turns every instance of 'a' into '[~ a]'.. Every beat then becomes an offbeat and so the overall effect is to syncopate a pattern. This is very useful for me and I normally do similar things by shifting patterns in time. I'll test deeper over the next days as I'll be working in the studio on new material. Thank you! ---
**Author:** ![cleary](https://uzu.lurk.org/user_avatar/uzu.lurk.org/cleary/32/177_2.png) [@cleary](https://uzu.lurk.org/u/cleary)\ **Post date:** [2 March 2021 03:09 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/18 "2021-03-02T03:09:20Z")
> [@msp](#): > > Are there other user cases? Manually controlling the effects with midi cc? > [@Tidal 1.7 control busses + midi control input = heart](https://club.tidalcycles.org/t/tidal-1-7-control-busses-midi-control-input/2934): > > Hi all, [update] there is now control bus documentation! [https://tidalcycles.org/docs/reference/control\_busses](https://tidalcycles.org/docs/reference/control_busses) I thought I'd share a very short experiment with the new control busses and midi input in tidal 1.7 - this immediately reactive control is something that I really missed when I first started getting into tidal, and I didn't have the patience to plumb the setup externally. I'm twiddling knobs on a novation launchkey mini, mapped to djf, squiz, room and size respectively d1 $ ā€¦ ---
**Author:** ![mrreason](https://uzu.lurk.org/user_avatar/uzu.lurk.org/mrreason/32/3203_2.png) [@mrreason](https://uzu.lurk.org/u/mrreason)\ **Post date:** [1 April 2021 20:00 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/19 "2021-04-01T20:00:41Z")
Today I found something curious with midi control busses. When I try to use `ccv` with `ccn` then everything works fine like ```haskell d1 $ s "midi" # midichan 0 # ccn "100" # ccv "<60 127 0>" ``` But when I try to replace the `ccv` with `ccvbus` then the returned value is always `0` like (I debugged this with MIDI Monitor) ```haskell d1 $ s "midi" # midichan 0 # ccn "100" <| ccvbus 1 (segment 256 $ ((saw * "<0 0.5 0!>") + 0.5) * 127) ``` But the [TidalCycles code on GitHub](https://github.com/tidalcycles/Tidal/blob/d3c3745b497f2328b09d7564ffc5c1f459939058/src/Sound/Tidal/Params.hs#L569) looks fine to me. Am I doing something wrong or is this is a bug? Does someone made some experiences with ccv control busses? ---
**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\ **Post date:** [1 April 2021 21:34 UTC](https://uzu.lurk.org/t/testing-tidal-1-7/2792/20 "2021-04-01T21:34:13Z")
I think the busses won't work with midi unfortunately, they are a way of talking with scsynth. CCs are manipulated independently from notes anyway, so there is no need for busses there. [Next page](https://uzu.lurk.org/t/testing-tidal-1-7/2792.md?page=2)