I opted for some bonus side-quests on the way in order to turn out really geeky-hardcore, and got a Samsung 840 Pro (instead of vanilla) and a GTX 660 Ti (again, instead of vanilla). I'll stick to my vote for the backpack first and the off-hand next, but do as you want - it's your character and your account, after all.Īfter some days of painful deliberation, an online shopping cart I emptied and re-filled ten times with slightly different gear specs, and a shipping mistake that cost me two more business days, I have finally levelled up. If FL studio requires you to bounce to tracks and then delete/disable the original, it's way less elegant, I suppose.Īs for gaming, if you go without AA and without Vsync then yeah I agree you'll probably be fine with a GTX 660. Should still save you boatload of time overall, even compared to buying a new CPU. At worst you're routing a bunch of pre-rendered tracks through some effects busses and it's doing those effects real-time. It takes some self-training to integrate it into your workflow, but you can go very far on budget hardware and the CPU becomes a non-issue. Logic does it the same way and they both use a snowflake icon even. At least in Sonar's case, it renders each freeze track at the highest quality settings at your project's bit depth and sample rate and all the fancy iZotope Radius algorithms already, so bouncing a stereo mix down is fast fast fast. Still a fan of freeze tracks, though - if you freeze a synth when you're set and go on to tweaking the next, then when you mix down to WAV, it goes really fast. But if that's your preferred sampling rate, then you're going to work the CPU a lot harder than I am. If i'm never going to release anything higher-quality than 44.1 via CD or compressed audio, I don't mess with sampling higher, but I do appreciate having additional headroom that 24-bit audio gives, to help prevent distorting. I'm against both antialiasing and vsync on principle, so judging by the reviews and the GPU's raw specs, it would probably let me crank the handle.Īlright, fair enough. I have a project or two that literally takes a full hour to render (with all the precision maxed out), even though multithreading is supported and enabled. Right now, several of my projects underrun (sometimes constantly) when using 88.2 kHz in real time. The reason is that I have a synth or two where sound is ever so slightly different in 48 kHz and 88.2 kHz. Usually not very much, but my preferred working sample rate is 88.2 kHz (2× oversampling on finalised tracks), and I'd like to use it in real time. Although with 50% more pixels than a 1080p display, that might be tough for a vanilla GTX 660. If you're not gaming at native resolution, you should be. Once you're done with a project, move it to mechanical storage.īarring that, my second choice is off-hand. So if you don't have a backpack, I'd be getting a 240GB or so backpack and loading all the audio stuff you can fit with your OS. And it's even faster when you're freezing to an SSD. I'm sure FL Studio has something similar (AFAIK Pro Tools is the only major DAW without the feature). Great for audio tracks, too, so you can get your stutter effects, reverbs, etc committed to disk and easily undone if needed. Nowadays in Sonar it's a matter of pressing the Freeze button. Though I do come from the olden days of a 603e running Logic 4 and Logic 5, so I'm used to "printing" tracks to audio once I'm sure I'm done with the synth. Part of that is the better single-thread performance, some of it is Hyper Threading, and the rest is just due to my workload I guess. How hard are you pushing FL Studio? I'm not really seeing more than 75% total use on my i3 2100 at any point with 15-20 tracks in Sonar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |