MOTUnation.com

Is it just me or does Mach 5 - 2 really not allow you to "not" stream samples. I have 8 gigs of RAM that I was hoping I could use over streaming from my hard drive. Everytime I unclick the stream function it either crashes or simply does not work.

CC

conleycd wrote:Is it just me or does Mach 5 - 2 really not allow you to "not" stream samples. I have 8 gigs of RAM that I was hoping I could use over streaming from my hard drive. Everytime I unclick the stream function it either crashes or simply does not work.

CC

Any mac App can currently address 4 GB.. So if you're running M5 standalone, you can address 4 GB(for M5). If you are running it as a plug-in. It's the sequencer that addresses the 4 GB. In DP that means you have about 3.5 GB to play with.
With Leopard things will be different you can adress some ungodly amount of ram. The apps need to be rewritten though...


You can toggle streaming on/off for every part, check the manual, it's there (I don't have it available right now and don't remember what it's called)....


/B

I've had success on some presets, and not on others. The MachFive2 piano, for instance, never seems to load in RAM. But some of my smaller instruments do fine.

Shooshie

Shooshie wrote:I've had success on some presets, and not on others. The MachFive2 piano, for instance, never seems to load in RAM. But some of my smaller instruments do fine.

Shooshie

Seem to remember magicd saying it's about 7 Gb.. so that might be the reason...



/B

conleycd wrote: Everytime I unclick the stream function it either crashes or simply does not work.

My experience is that if you try to load a preset whose size is in excess of available RAM, it churns for a while, then DP quits. Extremely annoying if you havent saved lately, and, well, we all make that mistake from time to time, dont we?

This should be addressed, I think, as it's an easy mistake to make; a simple error message saying, "no can do" instead of a quit would be nice, n'est-ce pas? Magic D?

Gavin

[quote="gavspen"]
My experience is that if you try to load a preset whose size is in excess of available RAM, it churns for a while, then DP quits. Extremely annoying if you havent saved lately, and, well, we all make that mistake from time to time, dont we?

This should be addressed, I think, as it's an easy mistake to make; a simple error message saying, "no can do" instead of a quit would be nice, n'est-ce pas? Magic D?
/quote]


Gavin, of course you are right. No errors that cause a crash should go un-trapped.....


Does it work the same in stand-alone as in Plug-in mode ( = crash ) ?


/B

bjornln wrote:Does it work the same in stand-alone as in Plug-in mode ( = crash ) ?
/B

You mean, "does it NOT work the same", dont you??.....

Dont know, never tried it.

Gavin

gavspen wrote:

bjornln wrote:Does it work the same in stand-alone as in Plug-in mode ( = crash ) ?
/B

You mean, "does it NOT work the same", dont you??.....

Dont know, never tried it.

Gavin

But it's guaranteed not to take down DP!

Well, most likely not

Ok i just turned off streaming while i had one of the big electric pianos loaded (standalone machfive)... Immediate pinwheel, and memory being sucked down rapidly.. I didn't wait for it to crash but it was hung for several minutes eating RAM every second so i force quit it... Guess it should do some quick math on the size of the samples you have loaded and give a stern warning (and of course not crash in any case). I could see someone inadvertently clicking that shiny orange button and... oops.

blackcrayon wrote: Ok i just turned off streaming while i had one of the big electric pianos loaded (standalone machfive)... Immediate pinwheel, and memory being sucked down rapidly.. I didn't wait for it to crash but it was hung for several minutes eating RAM every second so i force quit it... Guess it should do some quick math on the size of the samples you have loaded and give a stern warning (and of course not crash in any case). I could see someone inadvertently clicking that shiny orange button and... oops.

blackcrayon,
Could you try to do the same test again, but have the "Activity monitor" open, and check what happens to M5 (VM, RM %CPU, #threads), while it's churning away ?
(I would try it myself, but I'm not near my M5 machine at the moment)


/B