MAX API CTL LFO
I made two midi tracks and assigned 1st to A and 2nd to B. I then droppped a MAX API CTL LFO into master track and had it map to master track track’s mixer crossfade. I see the crossfade happen in real time, but I do not hear the resut of the cross fade. When I move the crossfade with mouse or a midi controller I hear it. Not sure why I don’t hear the crossfade under the influence of the MAX API CTL LFO. Any ideas?
From first looks I’d say you found a bug. Not too sure where from mind, first choice would be the LFO device of course but I vaguely recall having read issues with the crossfader before.
I did try a test case though and I can fully reproduce the behaviour:
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 1453.3oc6YszaaiCD9rKP+OPnyIFRxV1VK1KsXur.8zdsnvfVh1gMTjBTztI aw1e6KenWzRTVNwwIa2dQJY3ngC+lmb72e+6l3sg8.pvC7afOClL46RJSzzT TlTQXhWF7gDBrPynWFpn.tC4cS4hBzCB8B25OMJbYTTb8RDLEkv1S0qGVQEu ix3nDBN4dE8fJ5aYTQA9uQZh9S8qnS2mw1KHHQgE6FZhGyQF82yC7kp0x4nB DU.EXFcsbuDFVBBjRUJ6H0qEl+YwT+luSoBTXlVhdefigDvGYjz5CTNTjbGl tqsLmEpkyJsPiT5MHbYag1VYrNA3T89v170aC78ZcbwzpSanl3+792odKecy y2LkyY4Ht3QvAHYO502V8Dv73kZHOXtFxm0Exagryuz.KE8Mob6hqBvF.AP7 NOHZlSHZCjty6FITcyyEtBi096qTOmuv3s5.sB6GsBt3nEAe.Mkso.wOf3mI lE51s5YiUAg5H3fHsK1xvAQq.G9VUTKfGPoqkbJE+ZnPvwa1KL4amz.XS7VK CHKvEBDMA0.2U38kG24nLl.8iyD18eNvZYDqNVcQ7fnZ7aWTUidoxCbsJd.x qghtqdN9saILnXD0vhaBimqS.N2tZSWvekF0mux4mLhBTKcjXnYa4RXPf3qQ T3FBxZQiEq1TMjQSWThsshd8Bs2g8TrY28pTJqkY7TYJkVNrVqlh1NvpE4HT JAmoU+o8yh.kW3T.nGxYTjoJpCAnUewiFLpWNvzC3B7lA3HS5VNvV.oTVomS s2oW+xAqM425PPU9nNTSrP5s2xh2OfcGiKbGjXqOrzpSlphderPXzcmgzLmO eGxBSuWIK21SkHXoCgAaYF3sbwpzKubYukQ32cw5x3xzgQfIcjtzYTvfY2Wb o6vvcitRbBnPr0EHAHCVncn4vj6AY3GzoBNfSPfDNqnXKLsUeHV4d6uy3W9a qXpRZPyYK61j6S1NY5aNLZQ2K.MlRAQWqNpyAv8oX10rMECZuLdDsJOqeXv2 R7lRMVU31hInCpNSrQ3Idv77VzOp5WF7qLsrhZxBI2UCsfFZbjpzgQDwMojp 2jlypNXU+XgIvc9J+VGUoUaGgkbOJ0J2mmr94YHC4UMo8wd0iiXESO1AzZig 6Ih0VdAgS6mgsvDj6O21qntzg2NNNkQUJh82pnWskRmjHyMDrzdMKTXdeetf wHaf7V0zaL5xPCHEmAEHA1nTg9MeINKmiMIdZHZJ2dWgLuEgXKMyRG5aISxt ugSkEOrKHZODHK2t1gt1KbTHbBKKS00yMsXnNN92AebOljBdjsmaBoAnsakd E.Y7Ax5a5MW6PA+Cj.XLIAblHnL32LbgXyTchaawcMlAWk1r5MnNA4K.Z+Wd WBXiuaSUL6LUj5r4pmxGAGCBpMNgQLYhFA+NrHf+T.I3jSZXhzWIOzuLScmT zclnQzaFKym9o1xrx+LMLK9UHy0LjIHbzVl4+Jj4JFxTMxwQXXBeyXX9Cycm jMrJvIxSMAmgEWBi0c3zTjcmw8CzmBbK+oXhJuF0oQ232Lf6Gz8HIXfOIu8p aPM3mfH.caVglHfUlDTC0l0x2X1nsbV1+CrRlDT95WwKNoU5pVY2d5AGMAAx 9cRz9GOwDSVW.oyDbJv6npzP0+0nf7Sg0wqZ0Fk45GCWSvMVGd0wZL8+dPcY eQi.pCNent0DBTWs00sr0JmhAGFgB4MmSp.iRUAbjhlhJDXZ8fS9bs6wwL1T g0xdjgSyYXpnTGAeY7dOOI0OXrpevEU8qVnYnXi9GTr+AK4bdT6HrMPR4X.6 9yvbh4UMzbpFyrrbMtLW+3DFP11Ksb7sGadqFhaGy5RKmMGlzXal5ZNcXJ6c xxiV0hFips3UQ0VX4iOp33qkpo10vwXPCdUTsShZAuZp1I80l+pXPmOFUK3U Q0BFkp4+rsnJBxW+KKon0cA -----------end_max5_patcher-----------
The value is visible set, the live.observer also confirms the value yet the crossfader does nothing.
did you report this on the ableton forum ?
It seems that there are FOUR places that one can report a bug in Max For Live:
2. Cycling 74 support.
3. The Ableton forum.
4. Ableton support.
This doesn’t really seem like such a good idea!
For many technical products I’m interested in, instead of a forum there’s a mailing list, a bug tracker, and bugs for that product are automatically sent to the mailing list. With a mail client that consolidates threads (like gmail) this is a very practical way to do things.
(By the way, I love your Subject line. It reminds me of a friend’s band, "JFK LSD UFO".)
It’s tricky to know where to post a bug I agree. Because of the integration, you’re not sure whose bug it is.
I can verify the behaviour, but I don’t know which engineering team will need to look at this off the top of my head.
I have logged the issue for further investigation
We have a linked ticketing system, so you can be sure that wherever you send a problem it will end up in the right place.
It’s extremely unlikely this ticketing system will ever be publicly viewable.
Having a public bug tracker is only really possible for open-source stuff, you don’t want to reveal e.g. your upcoming plans to the world!
On my little commercial application where I wrote all the code, I have 92 open issues (and 456 closed ones). Getting all the bugs out is hard.
Thanks as usual!
OK this is a Live issue and is known to Ableton engineering
Thanks everyone, for responding to this message. I am having so much fun with Max 4 Live I forgot to check back in!
Forums > Max For Live