I do not believe for one moment you will be able to complete a full track using this method.
I have decided that you are a complete loon.
Viber
FLS 9.6\5 has some new ram/cpu efficient tools:
2:45
daeus
I had this problem for years, even if you are carefull,less CPU still limits you from being able to have a few more VSTs/FX than you need turned on just to be able to experiement at anytime with a new sound. so I got the spec in my Sig and never looked back :O
music2dance2
I think this could be overkill but its good that he is doing this because it might help him to work in a better manner than just getting more equipment when things arent going well. It might also help him to change to a more streamline his work flow down from this way to something else in the future. Sounds like a huge work around but if its working for him then so be it.
Agreed though this method could stunt creativity when moving from one project to other.
Andy28
Im all for the "whatever works best for you" approach, but seriously you cant work from 4 different projects and expect it all just to come together.. This surly must also slow your work flow right down? Also, yes alot of trance is layered but not just for the sake of it.. Your bass for example, I get what you mean it sounds fuller but thats just because you've overloaded the area with 4 synths.. Keep it simple, Yes layer but dedicate a synth to the sub, the mid and maybe the high, cutting frqs appropriatly for each area. Keep the sub mono and you can push the others wider (or send to deley for more width) then run them to a buss along with the kick and compress them all together.
music2dance2
quote:
Originally posted by daeus
I had this problem for years, even if you are carefull,less CPU still limits you from being able to have a few more VSTs/FX than you need turned on just to be able to experiement at anytime with a new sound. so I got the spec in my Sig and never looked back :O
Good point, when you have exausted the machine and work effciently but still struggle its worth an upgrade in some manner. Machines can be very cheap nowadays. I'm upgrading soon and cant wait. I can work and save on cpu and use only what I need but its good to have the choice to experiment and not always hold back on some things to use.
UXC
I am having similar CPU issues OP. I've tried everything but I've realized that straight up computer power is needed, everything hinders creativity for me one way or another... even freezing techniques I find.
Maybe it's my technology fetish but having a crap load of CPU behind your mixing desk = win
DJ RANN
Christ this sounds like the most convoluted way of working I've ever heard, but hey whatever makes you fell good and lets you work is all that counts, at least to you.
However, I can't help feeling that there are probably so many other ways to work that would let you be more efficient so you don't have to dick around with all this bull.
Stems aren't the answer for this situation, and frankly I have no idea why it has even been brought up.
Stem mixing is really just a method of using groups of tracks that have been committed to printed stem groups for mixing later or for consildating various different groups that would be unmanageable if all left as individual tracks.
The classic usage of this is film score where often hundreds of tracks are printed in to stems to later then be mixed at the dub stage. It allows some modifacation of levels between elements but not individual track control, so you balance the dialogue and sound effects with the orchestra and synth elements.
Another classic example is for mastering - the producer wants to keep their mix balance but the stems allow a mastering engineer a limited amount of flexibility to change things without changing the mix as such, but at least offers more flexibility than a just a stereo file.
Why on earth stems would be considered for the composition, arrange, engineering, programming or primary mixing stages is completely beyond me (and any logical answer in my mind)
As I said I think there's so many more things you could be doing to make the most of your system without having to resort to a convoluted method of separate sessions for each group.
I would really explore efficient production and mixing techniques before going down this road.
kevin shawn
I used to have CPU issues on my old computer but an upgrade to a quad core solved my problems for now.
My latest track only has about 19 channels on it and logic handles it no problem (usually) Sometimes I get an "audio engine overload" error but it's a minor annoyance.
Robby your sounds complicated lol
DJ Robby Rox
I agree with the idea that more CPU is the answer, and my goal has always been to get a supermachine that has no limits CPU wise, but even working on this quad I find I'm still fairly limited.
I could get 4 more gigs of ram (only have 4 now) but I'm stuck on this quad now for at least a couple years. I don't have the cash for a phenom II but one day it would ideally be what I want.
As "complicated" as what I wrote sounds however, some people are making it more complicated than it really is. Everything winds up getting merged into the "percussion" project because obviously I don't use a lot of speed for my drums. But what I do first is the bass, save it, then bounce it to the percussion track. I lay out my percussion, then save a new project which becomes the percussion/bass.
After that I open up the synth project, and get focus on getting all my cpu heavy lead/pad sounds out of the way. Once I get something down, I simply bounce it back to the percussion track. G-con is saying I'm never gonna finish a track this way, and that *I* am the "loon", but use your ing brain bro, all I'm doing is CLICKING to reopen my percussion track, then sampling my leads into that track. It takes a whole extra 3 seconds to do.
Another thing I do when I'm working on the leads is open the bass (that I bounced) into that track, so I already know how everything will sound together.
But basically everytime I have a new element, I already have the element before it rendered to wav and playing in that project.
I see how its a confusing ass way to work, but all I'm really doing is using 3 templates/projects to bounce all my work into the 1 percussion track.
People are talking about inspiration/creativity and I have about a thousand times more working like this. Its when I have 1 project open, knowing I'm gonna max it out once I get to my leads, that kills my creativity.
This is 4 quads and STILL one cpu heavy patch from ace can kill 20% (with multi-threading obviously enabled). Down the road I plan on getting a better soundcard, more ram, and a laptop so I can use that laptop for all non-production related crap. But right now everything is on this one computer, and even with a quad I'm still fairly limited.
I don't specifically choose cpu heavy synths, nor do I ALWAYS layer like a fanatic, but even if I'm not layering I'm often using a good deal of ghost sounds and other subtle synth sounds that kill a ton of cpu. I mean I made **1** ing bass swell a couple weeks back and it threw my core2duo over 70%, now with this quad that same one sound is killing 48%. Certain sounds no matter what just eat cpu like a mfkr. I can't just keep upgrading so I felt this was the only option I really had.
And so far I like it a lot so the only thing left to see is if I actually finish tracks. Theres definitely tracks I make that only wind up using 20-25% cpu in total, but for the most part thats a rare occurence. I guess in a few weeks I'll know better as to whether or not this technique is really serving me or causing more problems than I think, but only time will really tell.
kevin shawn
I'm on a quad core with 4 gigs of ram but I'm using an external soundcard. Get a new soundcard ASAP is my advice.
Or stop making epic layered trance tracks :p
music2dance2
If you get results thats the main thing working this way. I feel you will figure out a more effcient way of working (thats what most people are saying in this thread) but until then its a journey that everyone takes to better themselves in one way or another. You've just broken everything down into sections to work on separatly. Good luck with it all.
