FREE collection of 85 Jitter objects for Max 5 (OS X). Auvi performs unique complex video effects in real-time, and is optimized for extremely fast performance.

    • Sep 20 2010 | 8:52 pm
      Totally awesome package. Thank you!
    • Feb 03 2016 | 6:58 am
      domain name expired
    • Oct 20 2018 | 3:19 pm
      Has this been updated for 64 bit?
    • Dec 05 2019 | 8:17 am
      Hi, many of us are dreaming for a 64bit version of the awesome Auvi package. Is there ANY possibilities to have them back? I got so many patches using those externals, I’ll be happy to donate for an upgrade. Thanks in advance!
    • Dec 05 2019 | 9:51 am
      I met Kurt Ralske recently and spoke with him about Max & Auvi. It seems that he doesn't use those tools anymore but as I understood would probably accept that somebody ports his objects. Maybe someone should contact him there. (he doesn't read this forum).
    • Dec 05 2019 | 10:16 pm
      Please, please could some C guru port these wonderful objects? Ric
    • Dec 05 2019 | 11:43 pm
      It would be great if Cycling 74 could integrate this package officially, alongside with a selection of essential “lost” objects that made history... I always thought that the week point of Max was that they were not always releasing official tools fully supported and plug and play. In the other hand, I also find interesting and important to leave space to third party developers to experiment and maybe come up with innovative ideas...but if they come up with some unique tools, its hard to drop them when they have been used for so long and part of your workflow. Kurt Ralske with the Auvi package (alongside with many other developers) made an amazing contribution to the Max community, in a time where 32bit is dead, it‘s hard to see all this precious work fading away like this...
    • Dec 07 2019 | 4:24 pm
      I agree almost completely to your post, but I think that the actual Max distribution has a lot of useful objects (easily integrate with package manager) . It is'nt a C74 task to keep old externals running. Maybe it's time to start a new thread about the tools we wish to have back.
    • Dec 07 2019 | 8:09 pm
      I have pondered this issue many times.  I was an enthusiastic Auvi user until it died.  I also used and depended on several other packages that passed away leaving substantial damage to my creativity.
      Perhaps it IS a C74 task to keep old externals running.  Unlike many other developers, C74 has always been supportive of its users both large and small. 
      In the past, I have suggested that Independent developers deposit the source code of their packages C74 with the stipulation that developers continue support until they are unable to do so. Then support would pass to C74. We are an aging community and life changes happen. Perhaps a kind of will.
      Perhaps users could be polled to identify the packages that should be supported in this way.
      I started using Max before IRCAM and OpCode made it a product. I developed a package of seedable random number objects before Max had that capability.  I was able to keep up with new versions of Max for a while but, eventually, I forgot how to program objects in C. Many users depended on support I became unable to give.  Fortunately, my former student Jeremy Bernstein came to my rescue. I shared my code with him. He very kindly the package current. He generously shared a skill that, for him, is current while mine has withered.  This was the spirit when Max began and the spirit that should continue as individual parts of our creative community change with time.
      My software is copyrighted but I have never charged for it.  I would be happy, even enthusiastic, to transfer my copyright to C74 if they could find a way to maintain it as a legacy. Specifically, I suggest that C74 designate a corner of the programming lab to such things.
      Max was designed to encourage individuality and sharing. The cost of keeping the smaller pieces alive would be a sound investment in the future of the art that Miller and Max envisioned and inspired.
    • Dec 08 2019 | 12:48 am
      Totally agree with Gary. g
    • Dec 08 2019 | 2:38 am
      The kind of developer participation I am suggesting would include guidelines from C74 about the format to be used to qualify. The developer would follow these guidelines in preparing and maintaining their software. The current packages format provides a good model for this.
      When a developer becomes unable or unwilling to maintain the software, THEN it would be transferred legally to C74. If the value of the software is in question, users should be polled to gauge the value of continued support. In addition, we might encourage the formation of a pool of "angels" who would volunteer to maintain orphaned software - perhaps for free updates as long as they remain in the pool and participate effectively.
      Again I will note that, more than any other, Max users are part of a community that benefits from the welfare and productivity of all its members.
    • Dec 09 2019 | 7:14 pm
      Totally agree with Gary. In addition I think that there is still place for "externals" by independent developers, following the packages format. I also encourage the pool of angels, because I'm totally unable to program or compile in C. R