64-bit S1 in 32-bit Mac?

having just switched to mac, i am wondering how the whole 32bitOS/64bit plugin thing works in S1... will S1 be able to address 4+ GB of RAM and use 64 bit processing on my plugins in the 32 bit version?

sdrr00 wrote:having just switched to mac, i am wondering how the whole 32bitOS/64bit plugin thing works in S1... will S1 be able to address 4+ GB of RAM and use 64 bit processing on my plugins in the 32 bit version?

Nope, on Mac it works the same as on Windows, you need to enable S1 to run in x64 bit mode. Find the the S1 icon in your application folder. Select it and hit Apple+I. This will open the info dialog. In order to run S1 in x64 bit mode, uncheck the Open in 32-bit mode checkbox. From now on S1 will run in x64 bit, but will only support 64-bit plugins.

Motoko wrote:

sdrr00 wrote:having just switched to mac, i am wondering how the whole 32bitOS/64bit plugin thing works in S1... will S1 be able to address 4+ GB of RAM and use 64 bit processing on my plugins in the 32 bit version?

Nope, on Mac it works the same as on Windows, you need to enable S1 to run in x64 bit mode. Find the the S1 icon in your application folder. Select it and hit Apple+I. This will open the info dialog. In order to run S1 in x64 bit mode, uncheck the Open in 32-bit mode checkbox. From now on S1 will run in x64 bit, but will only support 64-bit plugins.

thanks for the response

all this is even when osx boots in 32 bit mode? is there a difference between booting in 64 bit and just running the app as 64bit?

If the OS boots into 32-bit mode, the application won't be running in 64-bit mode as far as I know.

I'm not sure but I remember reading somewhere that the latest OS X version automatically boot into 64-bit mode.

No - not exactly. On Mac OS 10.6 you can run a program either in 64-bit or in 32-bit mode - no matter if the OS runs in 32 or 64 Bit - but adressing more than 4GB RAM won't work in 32-Bit mode. (some plugins can still)

Running S1 in 64-Bit mode has the limitation that only 64-Bit coded Plugins will work - there is no bit-bridge for MacOS.

That also is not to be mistaken with the 64-Bit floating-point audioengine - that double precision has nothing to do with the 64-Bit programming code.

exactly - some Macs are unable to load 64bit kernel in SL due to Apple being ridiculous (and greedy trying to force people to upgrade their machines this way) but still even SL with 32bit kernel mode can run 64bit applications. The rest is exactly like Markus explained (it's really very often when people confuse floating-point precision bits with addresing space bits)

So basically it works the same in the end in terms of memory usage. With some plugins being the exception. Any ideas as to which supersede the host limitations?

as far as I know 64bit software take full advantage of 64bit extended addressing, most of system apps etc run in 64bit with just a few exceptions.

I'm aware of the whole architecture and stuff, but I was curious which plugins can access extra memory, even when the host doesn't. As mentioned by Markus.