ptpd server installing and running on Super Collider and Tidal Cycles

ptpd-tidal

## ptpd installation on Mac OS X HIGH SIERRA ##

#### update brew #### 
``` $ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null```

``` $ brew install automake```

``` $ brew install libtool```

``` $ brew install autoconf```


#### Then follow the installation process in the following document if below is failed
If building from a repository such as Subversion, CVS or GIT, run:

   autoreconf -vi

3. If building from a distribution .tar.gz package, you may run autoreconf -vi,
   but in most cases running ./configure should be enough - you must run
   autoreconf if configure or result in errors.

4. ./configure

5. make

6. Read the manual pages ptpd2(8) and ptpd2.conf(5). The man pages
   are the most complete source of configuration information.
   ptpd2 itself also provides an extensive help:
   run ptpd2 --help to see the short help
   run ptpd2 --long-help to see the long help for all settings
   run ptpd2 -e [key:setting] to display help for a single setting

7. Update test/client-e2e-socket.conf so that its
   "ptpengine:interface = " setting points to a network interface on
   your test machine that can see PTP packets from a grandmaster.

8. Test it in place: ./src/ptpd2 -c test/client-e2e-socket.conf

9. Check the log output of the daemon in /var/run/ptpd2.event.log
   Check statistics output of the daemon in /var/run/ptpd2.stats.log
   Check the status file /var/run/ptpd2.status.log

10. If the results look good, make install
11. 
->>>>>>> Check carefully``` https://raw.githubusercontent.com/ptpd/ptpd/master/INSTALL ```


#### to run ptpd as master, open terminal app ####
``` $ sudo ./ptpd2 -M -V -i en1 -L -C ```


#### to run ptpd as slave, open terminal app ####
``` $ sudo ./ptpd2 -s -V -i en1 -L -C ```

#### notes ####
**-M :** master only

**-V :** verbose

**-i :** interface

**-L :** lock

**-C :** forground

**-t :** g8265-e2e-master(optional template config)

#### To run Tidal Cycles in sync on both laptops
1. Connect machines with eth cable via modem
2. run ntpd on both machines, wait for slave notification on Master ``` $ sudo ./ptpd2 -M -V -i en1 -L -C ```
3. on Slave ``` $ sudo ./ptpd2 -s -V -i en1 -L -C ```
4. Open SuperCollider app on both computers
5. Open code editor as follows
``` $ TIDAL_TEMPO_IP=“<ip-of-the-master-machine>” <name-of-the-code-editor> ```
e.g
``` $ TIDAL_TEMPO_IP=“192.168.1.100” atom ```

#### Troubleshoot:
1. It doesn’t matter once the computers synced together, if you stop ptpd servers
2. If SC fails or quits but ntpd is running on slave machine , close the code editor and repeat **4th** step on slave machine
3. If SC fails or quits and ntpd is not running on slave machine/master machine, repeat **2nd**, **3rd** and **4th** steps in sequence