I am usually working with tracks recorded live of a worship set done at my church. The wav files tend to be 30-45 minutes long, times 8-16 tracks.
If I first split the whole set of tracks between the songs in the set, then save out separate "edits" containing only an individual song, would this allow Tracktion to not have the entire length of the wav files loaded?
If not, do I have to export these separate song clips, then import them into new projects?
The CPU overload problem seems to only come in to play when I'm using several effects at one time. Playing back of the raw tracks doesn't seem to be an issue.
Any advice here is appreciated!
Track Splitting to Alleviate CPU Overload?
-
- KVRist
- 33 posts since 18 Jun, 2004 from Cedar Rapids, IA
-
- KVRAF
- 6937 posts since 4 Jun, 2004 from Utrecht, Holland
You could try your suggested approach (cut up the long tracks in parts of seperate songs) and see what it does. However I suspect its the effects that take too much CPU.
Which effects specifically do you apply? Long reverbs? What type of system do you use? Maybe the combination is just too much: a system with not much power and very cpu hungry effects.
And there is always the "freezing" approach. You then render the effects to an audio track, so it doesn't take as much CPU anymore.
Good luck!
Which effects specifically do you apply? Long reverbs? What type of system do you use? Maybe the combination is just too much: a system with not much power and very cpu hungry effects.
And there is always the "freezing" approach. You then render the effects to an audio track, so it doesn't take as much CPU anymore.
Good luck!
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
No, and Yes.brucerothwell wrote: If I first split the whole set of tracks between the songs in the set, then save out separate "edits" containing only an individual song, would this allow Tracktion to not have the entire length of the wav files loaded?
Your separate edits will still be refering to the full length audio files, as clip editing in Tracktion is totally non-destructive.. however, T doesn't "load" the files so much as stream them from the hard disk, so there is no cpu penalty in working this way.. it sounds like you intend to work on the whole recording, but split into several sections (?) in which case you need the whole thing on your HD anyway.. might as well be the original large files, with seperate edits refering to different bits of them. (just make sure you don't apply any off-line procesing that you don't intend..)
If you really need them as seperate files, export the edit as a single archive: you will get options to save the entire files, or just the sections you used (with optional "handles"brucerothwell wrote: If not, do I have to export these separate song clips, then import them into new projects?
) .. you can then import these archives into new projects. (and burn them onto cd as back-up while you're at it 
)yeah, CPU is not an issue when just playing back audio (hard disk speed is more important here)brucerothwell wrote: The CPU overload problem seems to only come in to play when I'm using several effects at one time. Playing back of the raw tracks doesn't seem to be an issue.
as far as effects go.. either use less hungry plugs, upgrade your machine, or use T's freeze & render functions..