- IFREEMEM REVIEW 32 BIT
- IFREEMEM REVIEW PATCH
- IFREEMEM REVIEW FREE
- IFREEMEM REVIEW MAC
- IFREEMEM REVIEW WINDOWS
IFREEMEM REVIEW FREE
I think its going to take about a year for all these plugins to be updated and some of my favourites will never be updated (the free plugins such as DFX and MDA which I use for creative purposes)īut the bigger problem here is that I never ever had problems with memory usage on huge 100+ track projects on my 8 year old G5 which only had 3gb of ram in Logic 7. I also dont like the floating window and I have a number of plugs where the GUI doesn't even load in the 32bit bridge.
There are time when I NEED to see 3 plugins at a time working together. Why? Because I have hundreds of plugins and only 4 of them are 64bit! in the mean time I CANNOT work only being able to see one 32bit plugin at a time, and have it disappear if I touch the track mixer with my mouse. Now before you say it, at the minute NO 64bit Logic is NOT the answer. All I can do is try to submit them to Apple (somehow?) in the hope they'll fix this problem. This week im going to run extensive tests, take screenshots and videos on how it handles ram compared to Logic 8 and Ableton Live. Very strange but ive noticed Safari does something very similar so whatever Apple are doing its messing up ram usage in both. It should now read 200meg real and 100gb virutal (which is what Logic uses when you first load it with an empty song) - when I quit logic keeping an eye on the activity monitor you'll see the 300meg it should actually be using disappear first and the remaining gb's its hoarding pause for a minute before being properly flushed out of the memory.
IFREEMEM REVIEW PATCH
I might also add that the external servers (including Kontakt 4's) load exactly how big the patch is (for instance 1gb will take 1gb of ram) if you use Logic internally to do this It will use more like 1.5gb for a 1gb patch.Īnyway in the above example I loaded a hand full of patches in both Omnisphere and Trilian and put in one instance of AmpliTube 3 and a Logic channel EQ.already nearly 2gb of ram used!! I removed all the plugins and still this ram is used. Logic was still chewing up ram for each patch I opened despite the data being put into the external server (not the same of course, the external server helped, but Logic was still adding between 10mb and 30mb each to real and virtual ram upon cycling patches). In the above example I was testing simply Trilian and Omnisphere with their external server started. A lot of people have experienced the "lack of memory" error, closed Logic and reopened it only to find they had plenty of memory when they refreshed, here is a screen show to prove this massive bug. Number 3 is the biggest problem of all, which it never used to do to this degree in Logic 8. The biggest problem of all, it hordes ram and then DOESN'T RELEASE IT.
IFREEMEM REVIEW MAC
Ive not seen another application on Mac (apart from Apples also poorly programmed ram management in Safari) which uses real and virtual memory in equal doses as if its working like a Raid 1 arrary!ģ. It uses "real memory" and "virutal memory" in equal doses, which means you dont get the "in theory" limit of 4gb with 32bit, you hit 2gb of both and run out of memory. It uses more ram to load a single instance of a plugin than it did under Logic 8, or than Ableton live does (Anywhere between 300-400 meg of "real" and "virtual" ram for an empty Kontakt 4 instance!)Ģ.
IFREEMEM REVIEW 32 BIT
It has 3 major bugs (these are under 32 bit AND 64bit mode but I will concentrate on 32bit for now)ġ.
IFREEMEM REVIEW WINDOWS
Currenly Logic is using ram like a poorly programmed Windows application. Im not ready to let this drop with Apple and creating a 64bit version of Logic IS NOT the get out card. Ok, so Logics ram usage has been mentioned many times before, mainly from people who just want to make music and didnt know why they were hitting the "out of memory" message with Logic 9. (This is using Logic 9.1.1 in Snow Leopard 10.6.3)
Please note very important posts and test showing conclusive errors with certain plugins at post numbers:
0 kommentar(er)
