Hey Mads:

Creating equivalency in Tidal (someNewParam = param1) does not alter data Tidal sends to Max (as I am seeing it).

In other words, although I may type in Tidal , Tidal will still send “param1” to Max.

Consequently, inputting “someNewParam” into the Live.menu object in Max will not work, since Tidal is not actually sending “someNewParam” as data, but sending its equivalent, “param1.”

Does that make sense?

I am guessing that to send “someNewParam” to Max for recognition in the Live.menu requires deeper changes–perhaps to MaxMspOsc.hs?

Or am I missing something?

Daniel

Yes! That is awesome. Worked perfectly.

Thank you.

Hey Daniel. You can change max1 to m1 during setup by writing `m1 <- maxmspStream "127.0.0.1" 8020 1`

If you want to change it after having set it up: evaluate `m1 = max1` on a line of it's own.

After making max1 synonymous with m1 you can use the two interchangeably. The same goes for parameters. You make one thing synonymous with some other thing by declaring this in a line of it's own (as an example): `someNewParam = param1`. After this, when you write someNewParam in your tidal pattern it points to param1 behind the scenes (although it's still called param1 in max).

If you want to take it even further, in Max you can unlock the patcher, mark the dropdown and open inspector. Then, under the `range/enum` parameter you will see the entire list of parameters. You can change this however you want. If you for example want to add `someNewParam` you just double click the list of parameters in the inspector, add a space and write `someNewParam`.

Let me know if this makes sense.

Best

Is it viable for me, as someone unfamiliar with Haskell, to rename the parameters?–to replace “velocity” and “param1” etc. with parameters of my own designation?

I want to name the parameters to align with those pertinent to a particular Max patch.

Along the same lines, can I change max1 to m1–for the sake of speed when coding.

Thank you for any guidance you are able to provide, and thank you again for creating and sharing this tool.

DW

Ultimately, I wiped a laptop clean, reinstalled OSX 10.13.3, and reinstalled Haskell and Atom. Also, I installed Homebrew (per a recommendation in SuperCollider documentation; so this may be totally irrelevant as SuperCollider is not a part of the equation).

So it is hard to say where the error was (probably a misstep of mine during prior installation).

In any event, it is now running, and I am excited to explore creative possibilities at the intersection Tidal and Max.

Thank you for putting this package together.

Regards,

Daniel

Thank you, Mads, for your reply. I really appreciate it.
I am on a Mac running 10.12.6.
To complete Step 2 of the directions on Git, I do the following:
1. Open the Terminal on my computer
2. Type “cd” followed by the directory path ending tidal/MaxMspOsc
3. Type “cabal install”

Terminal reports back:

Warning: –root-cmd is no longer supported, see
https://github.com/haskell/cabal/issues/3353 (if you didn’t type –root-cmd,
comment out root-cmd in your ~/.cabal/config file)
Resolving dependencies…
Configuring MaxMspOsc-0.1.0.0…
Building MaxMspOsc-0.1.0.0…
Installed MaxMspOsc-0.1.0.0
Updating documentation index

I do not know what this means. But if I proceed to Step 4, and evaluate the import line “Shift Return,” I get the same error:

: error:tidal>
Could not find module ‘Sound.Tidal.MaxMspOsc’ It is not a module in the current program, or in any known package.

Lastly, it may not be related. But although Tidal works, and I really like it, I do get the following error message whenever I start it:

Warning: No local targets specified, so ghci will not use any options from your package.yaml / *.cabal files.
Potential ways to resolve this: * If you want to use the package.yaml / *.cabal package in the current directory, use stack init to create a new stack.yaml. * Add to the ‘packages’ field of /Users/MaxPhoton/.stack/global-project/stack.yaml Configuring GHCi with the following packages:

Thank you for any guidance or insight you are able to provide.

Regards,

Daniel

Hi Daniel. Sorry, I didn’t see your message until now. It sounds like the module isn’t installed. Did you follow point 2 on the install instructions on github? Make sure to be in the folder tidal/MaxMspOsc of the github files you downloaded.

Could not find module ‘Sound.Tidal.MaxMspOsc’ It is not a module in the current program, or in any known package.

Any guidance would be appreciated.

Kind Regards,

Daniel