By HouseWithoutMouse
Sun Apr 02, 2023 3:07 pm
I'm not complaining about the RAM size by the way, but the "when I was yooooor age" crap. 
HouseWithoutMouse wrote:I'm not complaining about the RAM size by the way, but the "when I was yooooor age" crap.

HouseWithoutMouse wrote:I think what I'm trying to say is, 2 gigs should be nice and good for a standalone machine even for producing modern stuff, with multisamples and plugins etc. Problems come from the lack of disk streaming. All sensible DAW and sampler products have had disk streaming for decades now. Who in their right mind tries to do "audio tracks" without disk streaming, that's an absurd idea. It was absurd in the 90s and it is absurd today. "We do audio tracks, but we're not streaming them off the disk, we load them all in RAM." YOU WHAT??? Or what kind of a genius does large piano and orchestral libraries without disk streaming. Hello? The LARGE amount of RAM available was the only reason why it was even possible to try such dumb things.



Certified Beatz wrote:For all complaining about memory in there MPC.. you won't be happy with 4gb or 64gb..
Certified Beatz wrote:just admit you suck at making music![]()
![]()

MPC-Tutor wrote:I was surprised that disk streaming wasn't utilised in the multisampled plugins, for example studio strings takes up 31% ram per instance, just not practical for the 2GB models. I assume though that is is ultimately a CPU problem, which is why they made disk streaming automatic only for audio tracks in the Force. There you can stream individual samples from an XPM file from within the project window, but you have to manually switch it on for each file individually, they clearly don't want to encourage it.
But upgrading ram to 4GB is really a bit of a sticking plaster, it doesn't really address the inherent limitations for people wanting to run lots of audio tracks, nor the 8 plugin limit, which I assume is ultimately CPU related.
HouseWithoutMouse wrote:Well people are not constructing songs from samples at all. They're trying to load full multitrack stem sets (see other threads) and use the huge multisampled libraries that are being marketed down their throats by the same company who doesn't give them disk streaming to be able to realistically cope with the libraries.
Certified Beatz wrote:HouseWithoutMouse wrote:I'm not complaining about the RAM size by the way, but the "when I was yooooor age" crap.
Not when I was your age..... more like try to be creative.. why do u need to load example a 500mb stem?

Certified Beatz wrote:To determine if 4gb matter anyone have Key61 with studio strings? If so what % of ram per instance when loading?.. also I understand all points there will aways be I need more..
