There has been much written here about poor performance of GPO on a Mac but I donÕt remember this hint being talked about. If it has, dear moderator, please feel free to pull this post.
Of course, the fastest machine and the most ram you can get is most important, but I just wanted to mention something that a new user of GPO might forget. In DP on a Mac, it is very easy once you have played some music with lets say a string section, and you have worked that MOD wheel until it has been driven deep into your keyboard, to thin that incredible amount of data that has been written. I find that once IÕve achieved the shapes I want, that if I thin this data using DPÕs ÒThin Continuous DataÓ command, that it doesnÕt affect the overall sound very much. As long as you donÕt destroy the general shapes you have created at first this works wonders to free up CPU resources.
Once you have things the way you want them, and just before you convert to audio, use the same command, setting the resolution higher again. Burn one track at a time doing this for each track, and youÕll keep your expression and be able to get more instruments in at the same time.
IÕm sure that other sequences have this same command. IÕm sorry if this doesnÕt make sense, but I donÕt have a lot of time at this moment but wanted to share this wile I was thinking about it.



Reply With Quote
Bookmarks