pattrhub bug - what happend to c74 support?

    Bernhard
    Nov 21 2008 | 12:57 pm
    Dear c74,
    first of all, I like max 5. The way workflow has improved is great and makes patching much more effective, easier and more fun. Of course there are many other small improvements which also make max a better package.
    I am not too happy with the performance of max 5, especially when it comes down to working with large, nested bpatchers. This has been discussed here extensively and I am hopeful for improvements on this.
    What strikes me more than that is the fact that c74 support is not what it used to be...
    With the release of max 5.0.5 (a couple of months ago or so) a really nasty bug in pattrhub has been introduced (pattrhub no longer responds to the parent address). This bug has been reported several times to this list. see:
    https://cycling74.com/forums/index.php?t=rview&th=35773&rid=3
    The introduction of the pattr system was a huge improvement (I think in 4.5 this was) and I can hardly believe I am the only person who relies on this feature.
    I remember times when a fix for a MAJOR bug like this was available within a few days. And now? What happened?
    Thank you.
    Bernhard
    • Jeremy
      Nov 21 2008 | 1:26 pm
      If you absolutely rely on this feature, please back down to 5.0.4. I have stated in the thread you linked to, as well as in others, that the bug lies not in the pattrhub object, but in the kernel itself, and that it was fixed more or less as soon as it was reported.
      As you can imagine, there are any other number of bugs in the kernel which require fixing, and preparing a special release of Max, with all of the required packaging and testing, for the purpose of solving a single bug with a single object, is simply impractical and unrealistic.
      Rest assured that we are diligently working on getting version 5.0.6 out (you might have noticed that we recently released an SDK, btw, which was taking up some of our attention). As we don't announce release dates, I can't say when it's expected. So, at risk of repeating myself, use 5.0.4 for now, if you simply can't work without the feature broken by the 5.0.5 update.
      Jeremy