Max 6.1.9 Released
We are happy to announce the release of Max 6.1.9.
This update is to primarily fix issues related to the Gen optimizations and additions that were in Max 6.1.8. There are a number of other fixes for more recently introduced bugs as well, including work on MFL, vst~, and more.
As always, you can download the update here:
Max 6.1.9 will install over top of your previous Max 6.1.x installation.
Enjoy!
-Ben
Fixed Bugs:
• closebang / freebang: no longer crashes when using to close Max
• Dict: embedded dict appropriately dirties the patcher
• Gen & MFL: fixed memory corruption triggered during editing of amxd with gen~
• Gen: caching respects connection count
• Gen: fix for .genexpr not loading
• Gen: fix for gendsp use when the 'require' is outside codebox
• Gen: fixed crash when param name has non-alpha-numeric character
• Gen: fixed crash when editing nested genpatcher via Modify-Read-Only
• Gen: fixed inlet creation issues in Max For Live context (and more)
• Gen: fixed inlet/outlet and crashing isssues (gen_patcher_load)
• gen~: fixed pfft usage
• gen~: fixed samplerate in nested poly~
• Inspector: fixed crash when hovering over "boxtextinfo" attribute
• Jitter Gen: respects the block level of declared values
• Max For Live: fixed dict save bug
• Max For Live: re-instate Java check
• Parameters: fix for parameter list corruption
• Parameters: fix invalid focus crash when deleting objects under certain circumstances
• pattrstorage: fixed 'writexml' crashes
• regexp: fixed memory leak
• udpreceive: improved crash protection
• vst~: fix for invalid memory access of plugin program and presetname
• vst~: improvements to parameter change audio 'clicking' artifacts
[udpreceive] stability improvements + [regex] memory leak fix!!!!!!! Thanks Guys :)
I am not sure but I just downloaded 6.1.9 and the bug for which by turning dac~ on max crashes has come back.
Anyone with same problem?
Please let me know
Regards
Tom
OpenSideBar isn't working. Could it be a bug or just me?
Hi all,
I just downloaded Max 6.1.9, and it crashes in 32 bits during startup half the time. In 64 bits it seems to start up without any trouble. Here are two different crash logs. It's always Appkit crashing with an EXC_BAD_ACCESS, but not always. Most of time however, the function where the crash occurs is:
com.apple.CoreText 0x90ed1700 TRun::DrawGlyphs(CGContext*, CFRange) const + 282
Regards,
Alexis
Short update: I reinstalled 6.1.9, and it seems now to be stable in 32 bits, at least during startup.
It crashes when I use any patch in 64 bit version (not during start up)
I got crashes or not complete quits on standalone apps rebuilded with this new version (never happened with 6.1.8, same standalone apps).
Every standalone contains a vst and a closebang obj.
Process: Prime Studio VST Host [20553]
Path: /Users/USER/Desktop/*/Prime Studio VST Host.app/Contents/MacOS/Prime Studio VST Host
Identifier: com.cycling74.MaxRuntime
Version: 6.1.9 [c65762b] (6.1.9)
Code Type: X86-64 (Native)
Parent Process: launchd [155]
User ID: 502
Date/Time: 2014-10-19 22:30:33.307 +0200
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report: 35763 sec
Crashes Since Last Report: 7
Per-App Interval Since Last Report: 453 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: B5711B51-7AB8-4891-C539-789BF3E18761
Crashed Thread: 0 Java: AWT-AppKit Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000003
VM Regions Near 0x3:
-->
__TEXT 0000000100000000-000000010069b000 [ 6764K] r-x/rwx SM=COW /Users/USER/Desktop/*/Prime Studio VST Host.app/Contents/MacOS/Prime Studio VST Host
Application Specific Information:
objc_msgSend() selector name: nextKeyView
Java information:
Exception type: Bus Error (0xa) at pc=7fff912d4256
Java VM: Java HotSpot(TM) 64-Bit Server VM (20.65-b04-462 mixed mode macosx-amd64)
Current thread (10b001800): JavaThread "AWT-AppKit" [_thread_in_native, id=2101039488, stack(7fff5f400000,7fff5fc00000)]
Stack: [7fff5f400000,7fff5fc00000]
Java Threads: ( => current thread )
10b10d000 JavaThread "AWT-Shutdown" [_thread_blocked, id=322936832, stack(1132fa000,1133fa000)]
10b067800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=316735488, stack(112d10000,112e10000)]
10b067000 JavaThread "C2 CompilerThread1" daemon [_thread_blocked, id=315674624, stack(112c0d000,112d0d000)]
10b066000 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=314613760, stack(112b0a000,112c0a000)]
10b065800 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=313552896, stack(112a07000,112b07000)]
10b064800 JavaThread "Surrogate Locker Thread (Concurrent GC)" daemon [_thread_blocked, id=312492032, stack(112904000,112a04000)]
112046000 JavaThread "Finalizer" daemon [_thread_blocked, id=311431168, stack(112801000,112901000)]
112045800 JavaThread "Reference Handler" daemon [_thread_blocked, id=301232128, stack(111e47000,111f47000)]
=>10b001800 JavaThread "AWT-AppKit" [_thread_in_native, id=2101039488, stack(7fff5f400000,7fff5fc00000)]
Other Threads:
112040800 VMThread [stack: 111d44000,111e44000] [id=300171264]
10b079800 WatcherThread [stack: 112e13000,112f13000] [id=317796352]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
par new generation total 19136K, used 3778K [7eae00000, 7ec2c0000, 7ece00000)
eden space 17024K, 22% used [7eae00000, 7eb1b0b40, 7ebea0000)
from space 2112K, 0% used [7ebea0000, 7ebea0000, 7ec0b0000)
to space 2112K, 0% used [7ec0b0000, 7ec0b0000, 7ec2c0000)
concurrent mark-sweep generation total 44288K, used 0K [7ece00000, 7ef940000, 7fae00000)
concurrent-mark-sweep perm gen total 21248K, used 6515K [7fae00000, 7fc2c0000, 800000000)
What I can say is that in my stadalones are present 3 vst objects. When I open a plug edit window, let them open and quit the app, then I become a crash, If I close the edit window and then quit the app, this quits without problems.
Using a closebang connected to a wclose message to the vst object, gives anyway a crash by quitting the app.
And that happens only in this new Max 6.1.9 version, and I think the issue is regarding only the modified vst object.
Try this patch, build a app, open a plugin, open his edit window, quit the app…. you will get a crash.
indeed, i seem too to experience random crashes during play with a patch featuring a vst plugin
I found the first problem ;-)
After upgrade to Yosemite and Max 6.1.9 I'm experiencing very low performance, when I'm working with [jit.gl.hap]. I reinstalled hap codec and the [jit.gl.hap] (latest versions), but without any positive change.
I'm working on MacBook Pro 17inch (i7, 16GB RAM).
Does anyone of you encountered this problem?
I've just reinstalled the 6.1.8
The vst~ standalone crash is not reproducible here, so we'll need more details of plugs, and some crash reports. Please send them to support
Cheers
-A
Could you send again 6.1.8 version please? I don't find it in the web site.
This 1.9 version does not works properly in 64 bit.
a bpatcher in a patcher doesn't refresh when I modify it and save it.
Ho un problema con l'oggetto scope~ non funziona su windows 32 bit. ho provato a reinstallare max ma continua a non funzionare. ho controllato la patch su un altro computer e li funziona perfettamente.