jonmoore

Does re-saving Max 5 patch's in Max 6 force internal processing to 64Bit for MSP objects and in turn if those patches are M4L patches will they in turn utilise the 64Bit engine for MSP objects. I ask because it's possible to run the Gen example patches within Live so I'm assuming the same goes for 64bit MSP objects.

On a separate but connected note, does changing the Max path in Live between Max 5 & 6 have any effect on the processing of MSP objects.

These are very probably questions that can only be answered by Cycling '74 themselves but it would be great for a little more clarity on the issue.

Does re-saving Max 5 patch's in Max 6 force internal processing to 64Bit for MSP objects and in turn if those patches are M4L patches will they in turn utilise the 64Bit engine for MSP  objects. I ask because it's possible to run the Gen example patches within Live so I'm assuming the same goes for 64bit MSP objects.

On a separate but connected note, does changing the Max path in Live between Max 5 & 6 have any effect on the processing of MSP objects. 

JM
------------
http://soundcloud.com/leftside-wobble


does-re-saving-max-5-patchs-in-max-6-force-internal-processing-to-64bit-for-msp

If you run a patcher in Max 6 then MSP will use Max 6's 64 bit audio objects. Nothing about the patcher or device itself has any influence on that. You can also save a patch in Max 6, run it in Max 5 and it will use Max 5's 32 bit audio objects.

If you have set Max 6 as your MFL editor (and runtime), then MFL will use Max 6's 64 audio objects internally.

If you run a patcher in Max 6 then MSP will use Max 6's 64 bit audio objects. Nothing about the patcher or device itself has any influence on that. You can also save a  patch in Max 6, run it in Max 5 and it will use Max 5's 32 bit audio objects.

Thanks for that rapid response Andrew. This is great news as I assume (as long as they all continue to work), any M4L device (including the legacy Pluggo devices) will make use of the improved 64bit audio objects as long as the Max application path is set to 6 within Live's preferences. And if I've created a patch in 6, as long as it isn't using any 6 specific objects, it will gracefully degrade to 32bit if the Max application path is set back to 5.