You say it's the data your computer stores of a project as your making it. Or is it? I know they aren't made for transport, but if I'm setting up a bunch of music effects and processors anyway, what's wrong with a desktop computer? So Homina, a 3 disk HD for scratch and a 6 disk for samples? Isn't that a bit overkill? I'm trying to understand what scratch data is. I plan on playing live shows so getting a Mac Pro isn't really realistic. I have been seriously racking my brain on how I'm going to do this with a laptop. Whatever the case, I rarely experience these kinds of errors anymore, and when I do the steps I've outlined in this thread are sufficient to handle them. It might just be superstitious, but then again it might not. I've taken to starting and stopping playback a couple of times before settling down to work. One final note: I've noticed that overload or disk too slow errors are most likely to occur during the first run of a newly opened file. Since drives WILL eventually fail, peace of mind is all about backing-up. RAID-0 is extremely fast, but everything in it becomes inaccessible if there's a drive failure. I save my session files onto a redundant RAID when I'm finished for the day and also onto a drive in another drive bay. My boot volume is in one of my drive bays, my samples are on a three-disk eSATA RAID-0, and my scratch disk is a six-disk eSATA RAID-0. If it's not up to the task, nothing will make it work smoothly. Of course, your system also has to be fast enough and large enough for what you're doing. I've found that it works pretty well in practice. Since the data flow for each of these volumes' purposes is kept separate from the other data flows, you should minimize overload and speed errors. By keeping your OS and app on one volume, samples on another, and scratch data on still another volume, you optimize the data flows for each set of functions that these volumes serve. Obviously the emptier the scratch volume is, the better, but in practical terms it doesn't really matter until the volume approaches the half-full mark. You don't generally start to encounter volume-specific bottlenecks until a volume is approximately half-full. Whether to optimize or delete depends on the volume's content and capacity. When I finish a session I back-up all my session files to another volume, and either delete those files from the scratch volume or optimize the scratch volume before I start the next session. Data files are created on a scratch volume as necessary by Logic (or whatever app you're using). This is usually the same volume from which I open a Logic control file, or where I save a new one the first time. Logic does not have the short "i" in front of it, and its not a mobile device.Īnyways, daws are like guitars.the more the merrier.Ī scratch volume is the one to which you save files as you create them. Ya can't even use the icloud on your macs without switching to Lion. I have by no means given up on Logic, but i'm not gonna get caught by "garageband pro" like they did to final cut studio. if Logic starts to wain i have already chosen an alternative that is better in some areas already and striving to s also mac and windows.you never know, Apple has publicly admitted that they are primarily in the mobile device business, all other concerns are secondary.that was right out of Jobs' mouth in an interview. I just like how far this Presonus daw has progressed given its short lifespan. I'm not flamin' Logic, its still my favorite daw, but All daws are give and take, good and bad on various features. Haven't played with it (V2) much yet, because i have not written a new song lately, and the only way to really get the feel for a new daw is to start a song from scratch and work it thru. i'll bet if surveyed it would be in Logic's top 5 pet peeves. V2 has yet to choke with the overload dilemma.and even though it is probably something in my setup or plugins, it happens far to often to a lot of people with this habitual problem. it easily dumps on Waveburner, and its built right in. you can sync the song you are working on with the mastered cd so that if you open a song/track and work on it, the changes you make are updated to that track on your master.even DDP export. How about V2's mastering your cd/digital album straight away right inside your daw. Yes, comping is a PITA, but how about Melodyne built in, straight up real time use right from the arrange window.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |