MAX API CTL LFO


    Aug 08 2012 | 12:46 pm
    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?

    • Aug 08 2012 | 11:19 pm
      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.
      Alas, took a quick peek at the LFO but I noticed that its mostly using javascript which I'm not too fluent with.
      I did try a test case though and I can fully reproduce the behaviour:
      The value is visible set, the live.observer also confirms the value yet the crossfader does nothing.
    • Aug 09 2012 | 8:10 am
      did you report this on the ableton forum ?
    • Aug 09 2012 | 12:20 pm
      It seems that there are FOUR places that one can report a bug in Max For Live:
      1. Here.
      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".)
    • Aug 09 2012 | 1:11 pm
      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.
      Cheers
      -A
    • Aug 09 2012 | 1:22 pm
      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!
    • Aug 09 2012 | 1:30 pm
      OK this is a Live issue and is known to Ableton engineering
      -A
    • Aug 11 2012 | 4:54 am
      Thanks everyone, for responding to this message. I am having so much fun with Max 4 Live I forgot to check back in!