Configuration is difficult

[yaxu]

Since the changes to stream/clock, tidal has become more difficult to configure.

There used to be a single config structure defined in Sound.Tidal.Config, in the currently released v1.9.5:

data Config = Config {cCtrlListen :: Bool,
                      cCtrlAddr :: String,
                      cCtrlPort :: Int,
                      cCtrlBroadcast :: Bool,
                      cFrameTimespan :: Double,
                      cEnableLink :: Bool,
                      cProcessAhead :: Double,
                      cTempoAddr :: String,
                      cTempoPort :: Int,
                      cTempoClientPort :: Int,
                      cSkipTicks :: Int64,
                      cVerbose :: Bool,
                      cQuantum :: CDouble,
                      cBeatsPerCycle :: CDouble
                     }

Now there is this in Sound.Tidal.Stream.Config:

data Config = Config
  { cCtrlListen :: Bool,
    cCtrlAddr :: String,
    cCtrlPort :: Int,
    cCtrlBroadcast :: Bool,
    cVerbose :: Bool,
    cClockConfig :: Clock.ClockConfig
  }

and this is the the tidal-link package, under Sound.Tidal.Clock.Config:

data ClockConfig = ClockConfig
  { cQuantum :: CDouble,
    cBeatsPerCycle :: CDouble,
    cFrameTimespan :: Double,
    cEnableLink :: Bool,
    cSkipTicks :: Int64,
    cProcessAhead :: Double
  }

I expect this split was to allow tidal-link to be used separately from tidal, however this makes configuration more difficult.

We can add setters like in #1162

But this is not too easy to deal with either, as different parameters have to be set in a different way.

[yaxu]

One solution would be to reinstate the single Config structure (probably without the no longer used cTempo... fields).

The ClockConfig could then be constructed from that. To avoid confusion perhaps the field names of the ClockConfig datatype could be prefixed with clock instead of c.

@polymorphicengine I think you are using the tidal-link package in zwirn - any objections?

[yaxu]

PR #1203 means the previous configuration style would now work.. Or would if it wasn't for the name change of transitions in Sound.Tidal.Transition.

Maybe we could reinstate the old names for now..

[polymorphicengine]

I'm fine with renaming - another option could be to rename as you suggested and import the clock config qualified to distinguish the two