Max 7.0.6 Released
We are happy to announce the release of Max 7.0.6. This release features over 60+ bug fixes. As always, you can download the new installers here:
https://cycling74.com/downloads/
This can be installed over your previous Max 7 installation, and will not affect installs of Max 6.x or lower.
Enjoy!
-Ben
• amxd~: header name appearance fix
• attrui: style attribute is a menu in inspector
• Audio Driver: fixed issues Logitech camera audio input
• BEAP: misc fixes
• Debug window: improved highlight color
• file paths: improved path normalization implementation
• filtergraph~: attrui updates when sending message to object to change filter
• Find bar: closes when patcher is locked and Format Palette is open
• gen~: fixed local variables "leaking" between codeboxes in the same genpatcher
• gen~: properly determines variable type in a control-flow sub-block
• gen~: work is no longer lost if the gen~ was named but the gendsp was not found
• inspector: remembers setting of show column header state
• jit.dx.grab: adapt functionality
• jit.dx.grab: output_texture support
• jit.gen: noise() works with float64 matrices
• jit.gl.camera: capture works when bound to a gl.node sub-context
• jit.gl.graph: no longer breaks when changing drawto
• jit.gl.sketch: fix for opengl errors with jit.pwindow in a bpatcher
• jit.grab: Native Blackmagic driver improvements
• jit.gradient: fixed crash with large dim
• jit.matrixset: importmovie message imports all requested frames
• jit.playlist: fixed crash with qt engine when connected to jit.world
• jit.playlist: preview strip display fixes
• jit.pwindow: fixed excessive rebuilding of the gl context view on instantiation
• jit.pwindow: fixed issues when in a bpatcher
• jit.vcr: better audio sync with video
• JUCE: fixed WebKit cursors crash on El Capitan
• live.param~: fixed crash when deleting object
• M4L: fixed crash in jit_gl_render_setup on closing a Live set
• M4L: mapping_index shown for parameters
• Max app: cleaner quit routine
• MFL: fixed OpenGL errors when changing visibility of MFL device
• MIDI in Max For Live: works in the editor when Max is not authorized
• MIDI: fixed crash when changing midi port x64
• midiparse: fixed issues with bogus bytes
• mtr: fixed issues in 64 bit mode
• mxj / mxj~: fixed error when saving a patcher that uses mxj
• mxj: classpaths no longer printed twice
• mxj: fixed 64 bit crashes
• Objects: editing text of object box no longer sets fontface attribute to default
• opendialog: removed errant multiple file selection option
• Parameter window: visual improvements
• pattrstorage / autopattr: changing subpatcher's name updates in client objects window
• pattrstorage: autopattr_vis updates in client/storagewindow
• pitchshift~: fixed using attribute as arguments
• portaudio: removed availability for Windows 10
• presentation mode: fixed fade when objects are selected that aren't in presentation
• Projects: added developer directory for Max For Live dev and export
• Projects: fixed crash when reopening Max when there is an image in the opened patcher
• Projects: fixed Export Max for Live device typo (Liv&e) (Win-only)
• Reference sidebar: all message / attribute entries are shown
• rslider: fixed graphical glitch when mousing
• savedialog: extension works in MFL device
• seq: misc fixes including read functionality
• snippets: BEAP-seqsynth.maxsnip properly instantiates
• Standalone: jit.movie able to find find embedded media
• Standalone: more trimming of app size
• Styles: Library style properly applied
• Templates: workspace restore uses default template
• thispatcher: window exec messages no longer stop openGL rendering
• umenu: Windows folder population no longer lists parent folder names
• Vizzie: misc fixes
• vst~: fixed issues when plug has less input channels than output channels
• waveform~: selection is properly visible with large buffers
Delighted to see old bugs have been fixed, and excited to see the "no cef" Runtime option. It looks like 7.0.6 is the update some of us were hoping for to really start using Max 7 seriously. Thanks.
Max 7.0.5 was working ok --- downloaded 7.0.6 and ran it, it crashed immediately.
----------------------------
Process: Max [28553]
Path: /Applications/Max7/Max.app/Contents/MacOS/Max
Identifier: com.cycling74.Max
Version: 7.0.6 [89abea6] (7.0.6)
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: Max [28553]
User ID: 501
Date/Time: 2015-10-01 17:08:17.925 -0400
OS Version: Mac OS X 10.10.5 (14F27)
Report Version: 11
Anonymous UUID: 1196E8DC-5C84-5445-BDFF-E71037C7A3DD
Time Awake Since Boot: 460000 seconds
Crashed Thread: 31
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000002e0f8
VM Regions Near 0x2e0f8:
-->
__TEXT 0000000000086000-000000000082e000 [ 7840K] r-x/rwx SM=COW /Applications/Max7/Max.app/Contents/MacOS/Max
Application Specific Information:
Performing @selector(menuItemInvoked:) from sender NSMenuItem 0x7ee46d70
Thread 31 Crashed:
0 com.cycling74.Max 0x004129cb maxdb_tags_append + 100
1 com.cycling74.Max 0x00409bcd maxdb_tags_fromstring + 141
2 com.cycling74.Max 0x00409c57 dbthing_set + 73
3 com.cycling74.Max 0x0040bc8d maxdb_insertfile + 3587
4 com.cycling74.Max 0x0040c30f maxdb_addfolder_do + 1126
5 com.cycling74.Max 0x0040f078 maxdb_update_do + 391
6 com.cycling74.Max 0x001329eb systhread_threadproc + 78
7 libsystem_pthread.dylib 0x99135c25 _pthread_body + 138
8 libsystem_pthread.dylib 0x99135b9b _pthread_start + 162
9 libsystem_pthread.dylib 0x99132e32 thread_start + 34
"gen~: work is no longer lost if the gen~ was named but the gendsp was not found"
is this a fix for this problem?
I've been patching with gen for about a dozen hours now since downloading the new update and have not lost any subpatchers yet--! Fingers crossed this will continue.
Hi Jaren,
If you haven't already, please drop a line to Support so we can try and track down the problem you are seeing. I'd be very keen on trying to repro.
-Ben
Hi Jaeho,
Support has tried to reproduce your Changing "Output Device" crash and is unable to. Could you send the full crash log to support at cycling 74 dot com?
Also, please include 'support info'. To do this:
- Select the "About Max" window (Max menu on Mac, or Help menu on Windows).
- Click the link in the About Max window which reads "Copy support information to clipboard".
- Paste the results in the "System and Max Version" field into your email.
Be sure to include what kind of audio devices you have tried and reproduced on.
All the best,
-Ben
I sent the info you asked to the support email.
I'm going to clean-install Mac OS X El Capitan today and see if it resolves the issue.
Hello,
Once again, I tried to install the new update, thinking "Oh my gosh, this may change all my patch, extras, externals, helps, etc…". And once again I was right. Thanks to Time Machine I haven't lost all of them, but now I need to copy files directory by directory, hoping older files will not deleted new ones...
Making just one file (metadata) for the application was a good way, but why can't we just have a installer who just replace/add new files and let the older as they are and not delete them ?
Sorry, you make good job either, but it was a "sad tought" just after updating.
Thanks for the reply,
Hieros Gamos.
Hieros, where exactly do you install your custom patches/extras/externals/help whatever ? Right now, with the packages, projects, and shared users directory for examples, there's a lot of solutions to not lose anything between 2 max installations
I used to place them in their own directory (by opening them with "package content" - I'm not sure about the translation).
And put somes in Packages (Document shared). But do you means that I can put any help or externals here ?
For the "extras" I was forced to put them in "package content" to see them in "Extras" of Max.
so, indeed it seem syou're unaware of how the /Documents/Max/Packages folder works. It's not that startling - there used to be a very concise readme, "about packages.txt", in Max 6.1/packages folder, but since 7 i can't seem to find it ?
Turns out it's integrated in the max built-in documentation : menu Help->Reference ; type "packages" in search box, you'll find "about packages" which i think you should read - it should help you :)
I'm getting a strange behaviour from jit.movie.
I've opened a patch that mixes from video sources and was running fine on 7.0.5 and now it shows big white squares all over the video screen.
Any idea? Maybe something has been changed in how the jit.movie object behaves with some settings?
ALEX_K, please send the patch to robr@cycling74.com
My original post was about Audio Status window, but it turned out that JUCE and Korean Input Method cause the crash. When English or Any other input method such as Japanese are chosen as the current input method, Max does not crash, but when Korean chosen, Max crahses as soon as I close any window in Max.
I sent a few emails to support but they no longer answer to me, so I leave this message here.
(I clean-installed El Capitan but it did not help. And this is not just me. Another friend of mine has the same problem.)
I seem to be getting no video output from the jit.gl.imageunit object on OSX 10.11.1 beta.
The device is outputting the effect list and attributes but no video.
I haven't got an older copy of max or OSX to test. can anyone confirm if its working or not? (jit.gl.imageunit help patch)
Cheers
Chris.
hi chris. i can reproduce this. from searching the internet, it appears that apple has deprecated image units, and may have stopped supporting them with the latest update.
Rob, please help me and my friends in Korea. We all suffer from this problem;
When closing any window in Max when Korean Input method is selected, Max crashes. I guess this has something to do with JUCE.
No answer from support, no answer from this forum... this is really frustrating.
I think you can reproduce this easily. Adding "2-Set Korean" in "Input Sources" tab of "Keyboard" of System preferences, and test. That will make Max crash.
(* crash occurs only on Mac OS X El Capitan)
Hi Jaeho,
I've responded to you several times via Support, and then did not hear back from you.
I've said all of this in my emails, but it sounds like there is something installed on your machine that we don't have, that is causing this crash. Perhaps a driver, a plug-in, or something else. As we cannot reproduce, we will need to get more information from you and run through some things off-list. Just respond to the Support emails and we can continue working with you.
-Ben
ㅑ ㅓㅕㄴㅅ ㅅ갿ㅇ ㅑㅜㄴㅅ미ㅣㅑㅜㅎ
whoops lol. I just tried installing, then turning on in menubar 2-set korean and it crashes max on xing window for me too.
Not crashing for me with these instructions
-A
Ben, no, I never received emails from you. I just got emails a few times from Tom Hall and the last email was on Oct. 13 which said that my email was received by tech support (looked like an automatic reply). (case # 23524)
I clean-installed El Capitan so I'm pretty sure that it's not a driver or plug-in issue. And please note that this is not just me. I asked people around me who are using Max and they all have the same problem.
Jonah and Andrew, thanks a lot for your test.
*Ben, to what email address did you send your email. I just checked my profile if there was something wrong with my email address and found that a strange problem. Please see the attached image (two email addresses?)
I'm really sorry to make this thread messy, but please forgive me. This is very critical for me, because I have a concert next week and do not want to see Max crashes during the performance.
To reproduce this problem:
1. Adding "2-Set Korean" in "Input Sources" tab of "Keyboard" of System Preferences.
2. And also turn on the "Show Input menu in menu bar".
3. Select the Korean input method under the menubar as shown in the attached image.
4. Run Max.
5. Create a new patcher window or open an any patch file.
6. Close it. (make sure that Korean input method is still selected.)
* Max 7.0.6 but Max 6.1.9 also crashes
* Mac OS X 10.11 or later (El Capitan)
Hi Jaeho,
As mentioned, we cannot reproduce here on El Capitan or any other OS. Clearly there are some other things in play here. Perhaps something about your system setup, screen configuration, external devices connected, etc. But we won't know until we dig a little deeper with your exact setup.
Anyone who can reproduce this problem, please drop a note to Support so we can track this issue down.
-Ben
Hi Ben,
Thanks for your response.
I already uploaded a crash report and a support info in one of my posts in this thread. What else do you need?
I know 6 people who has the exact same problem (from Max community in Korea, they all use El Capitan, and others who do not have this problem still use Yosemite). If you let me know what you need, I can ask them and collect all the info and send them to you.
Jaeho,
Please email and/or have your friends email Support and we will deal with it there.
-Ben
Just a follow-up here. We can now reproduce the Korean input crash. The only workaround that we know of now is to not use Korean input when using Max, or downgrade your OS until we can either fix the bug or determine if there is a bug in the OS.
Just to reiterate, especially for crashes, I strongly encourage people to contact Support so we can run through machine-specific debugging.
-Ben
Hi Ben,
I'm glad to hear that you can reproduce this, and hope to see an update soon. I understand this could be a problem of Mac OS X, not Max.
Some hints:
- When closing a window in Max :
1. Max does not crash if it is not the front application.
2. Max does not crash if Japanese or Chinese input method is selected.
3. Max v6.1.9 crashes as well as Max 7.0.6.
I have been enjoying ej's Sublime style (not just his panache, but his actual Sublime Text snippet and style theme) - however, I often find myself back in my patch, making edits inside of Gen.. and then..... when I least expect it... *crash* All gone. :(
It would be great of there was a way to recover pre-compiled code in Gen...
And keep up the great work..