Max 8.0.3 Released
We are happy to announce the release of Max 8.0.3. This update is limited in scope and focuses on regression bugs, follow throughs on a few Max 8 features, and issues related to Max For Live. Take a look at the change log below, and, as always, you can download the installers here:
New Features:
• mc.ifft~: added MC version
• mc.plugin~: @chans attribute (like mc.plugout~)
Fixed Bugs:
• dialog: fixed colors of Windows version (follows Theme)
• jit.cellblock: fixed crash on clear all when using refer to coll
• jit.gl.slab: fixed crash when opening text editor with shader that has errors
• Jitter: fixed crash when processesing XML
• Max For Live: fixed MIDI output after opening device in editor
• MC Wrapper: accepts ints in inlets
• mc.dac~ arguments no longer ignored
• mc.gradient~: fixed crashes
• node.script: improved finding .js files in amxds
• regexp: fixed intermittent crash with empty symbol replacement
• scope~: fixed issues with intermittent drawing
• signal probe: fixed potential crashes if object is deleted
• sqlite: fixed db errors when using certain characters in an object box
• vst~: fixed right channel input for some plugs
• vst~: generic controls are visible in presentation mode
Hello Ben, unfortunately the Closebang object still does not work if it is in a subpatcher. (Max For Live) Reported on December 10th
Hello! It was mentioned in release note that few jit. objects are no longer supported. Is there any new objects to replace them?
This list of unsupported objects is not new. Compare it with the (almost) the same list in Max 7 release notes: http://cycling74.s3.amazonaws.com/support/version_7_0_0.html. Around five years ago Max switched from QT engine to AVF engine, leaving several 32-bit objects not supported. No, there is no direct replacement for them, but most of their functionality is covered by other objects.
Hi Ben ) would you be able to assure me that 8.0.3 will mean the audio outputs from mc.dac~ will show up in the audio status I/O mappings window on Windows 10? I was able to get this working with a regular dac~ for a rewire client when I was experimenting with it five years ago, but now I finally have a multichannel design almost done, I suddenly find the outputs don't show up even with a regular dac~ object. All I get are outputs 1 and 2 from a regular ez.dac~. I thought even with a 2-channel audio driver I should be able to select which two from those available with the mapper. Am I doing something else wrong? I don't think I got stuck on this the last time, but I can't remember.
Well in 8.2 I find the regular dac~ is working in the example below, and that there are now 1024 mappable destinations, but symbols no longer name the virtual channels, and instead route the audio to the hardware mixer's channel zero. But I can get the audio channels mapped out, which is what matters. Thanks for the update )
there are 1024 outputs in max v.4, too.