Dear Ableton

[Khazul]

Whatever - ok so would have died when trying to allocate past the 3.6GB mark.. but thats close enough.




Someone maybe talking BS - but I dont think its me..?

[zee verkawound]

Whatever




Someone maybe talking BS - but I dont think its me..?

LOL! This and .25 will get you a gumball pal.

Listen friend, if you don't know that on a 32bit framework system the most ram that ANY program can use including the operating system is about 2.75 gigs of ram, there is some BASIC education in order.

[ollyb303]

Like I said earlier, back in your box! Come out again when you know what you're talking about.

Not getting into further discussion with this troll.

[zee verkawound]

Like I said earlier, back in your box! Come out again when you know what you're talking about.

Not getting into further discussion with this troll.

seems to me it's you two that are lost. you don;t even seem to understand what 32 and 64bit is and what it means in terms of basic program memory access.

[jamief]

Live is fine.

[Khazul]

Like I said earlier, back in your box! Come out again when you know what you're talking about.

Not getting into further discussion with this troll.

Ack...

[zee verkawound]

So, here's the bottom line despite what the "experts" seem to babbling about. Ableton Live presently CANNOT access more than 1.6 gigs of ram without extreme shakiness and crashes galore. This is simply because it's 32bit. When it becomes 64bit the amount of ram accessible to the program (HOST program, not slave, bitbridged or any other clunky contrived nonsense) will be HUGE by comparison. No more sample library issues. Keyboard players will actually be able to use the program live and those of us that actually want to use the program as a DAW and not just a slaved sequencer will have something that actually just industry standard at this point.

I don't need to argue to KNOW how much a program in a 32bit operating system can access. Old stuff here people and no matter how the fanboys and girls want to paint the picture, it's just a cartoon strip until the day Ableton Live 64bit is a reality.

[[nis]]

The maximum amount of memory Live can utilize depends on your operating system.

- a 32-bit Windows OS can only address up to 2 GB to an application (ANY application for that matter) or max 3 GB if the so called "3 GB" switch is enabled.

- a 64-bit Windows OS can address up to 4 GB to a 32-bit application.

- Mac OS X can address up to 4 GB to a 32-bit application.

Note that all these limitations apply to virtual address space, which should not be confused with sheer physical RAM.

Best,
Nico

[ollyb303]

Correct. Where he's getting 1.6 from, I have no idea...

[Rationalizer]

I don't need to argue to KNOW how much a program in a 32bit operating system can access. Old stuff here people and no matter how the fanboys and girls want to paint the picture, it's just a cartoon strip until the day Ableton Live 64bit is a reality.

I'm all for 64 bit Live, but you seem to offer the same argument without any further evidence. Other people here have been given facts even in a graphical form. Where does your arguments (which you seem to "know" so well) come from?

[Khazul]

The maximum amount of memory Live can utilize depends on your operating system.

- a 32-bit Windows OS can only address up to 2 GB to an application (ANY application for that matter) or max 3 GB if the so called "3 GB" switch is enabled.

- a 64-bit Windows OS can address up to 4 GB to a 32-bit application.

- Mac OS X can address up to 4 GB to a 32-bit application.

Note that all these limitations apply to virtual address space, which should not be confused with sheer physical RAM.

Best,
Nico

The 3GB (Part of 4GT, or 4-gigabyte tuning) switch is for 32 bit operating systems and as you will (should) know goes with the IMAGE_FILE_LARGE_ADDRESS_AWARE flag or /LARGEADDRESSAWARE linker option in terms of enabling use of memory above 2GB on a 32 bit OS.

On a 64 bit OS, the IMAGE_FILE_LARGE_ADDRESS_AWARE flag or /LARGEADDRESSAWARE linker option again enables access to over 2GB virtual address space for a 32 bit exe, however in this case the upper limit of the virtual address space (as returned by a GetSystemInfo() call) can be upto 4GB, however in practice a large chunk gets reserved by the Kernel.

Either way - the OP complaining about an apparent 1.6Gb limit might depend upon how Ableton Live locks virtual memory pages into phsyical memory along with total memory limit (and if he was referring to a mac - then god knows how that deals with it) - I am guessing it may make considerable use Virtualxxx Win API calls, so perhaps on his machine while he might have plenty of virtual address space, locking too many pages in memeory could use up all phsyical memory long before exhausting virtual address space?

@zee troll - you may want to takle a look at http://msdn.microsoft.com/en-us/library ... s.85).aspx- I guess they talking porkies too?

[8O]

/subscribe...





Edit: (MBP 2.2GHz / 4GB RAM / OS X 10.6.5)

[xzusa8ky]

Since i got a new MacPro 2.8 Ghz 8 core Live have been amazing stabel for me with no crashes at all!

Before i was running Live 8 on a PPC G5 Dual 2.5 with nothing than problems. My advise! Buy a faster computer and Live will be stabel for you too.......

But i feel for you!