![]() If the interface allows low latency monitoring you shouldn't notice anything while playing at 1024 or even higher buffer sizes. Maybe try upping the buffer to 1024 and recording at 48 kHz. ![]() Maybe not the most efficient system by today's standards, but not screaming to be upgraded ASAP either. The 2700K is a little old, but it is still a decent enough processor that is above the minimum recommended specs. It is better for your bank account to try what you can via settings instead of spending a bunch of money on new PC hardware that you might not even need yet. It could also possibly be an ASIO driver issue too. So, in summation, your system may or may not be in need of an upgrade, but there still might be some ways to avoid these issues via settings. ![]() I did run into some issues on that laptop with Cuebase though, but those went away after getting a new interface and messing more with the buffer and a few other settings. I have a copy of Studio One running on both my PC and on a laptop, the laptop being a real steaming pile of shit spec-wise (it is not even a quad core, it is a duo core), but don't run into crackling issues on that machine because I keep the buffer high for both recording and mixing. But if you have a more modern CPU, like a mid level quad core with 8 or more GB of RAM, you should be fine.įor example, if you had your buffer set really low for low latency recording and then forgot to raise it while mixing, you could run into cracking issues if the PC is a little under-powered, or if you simply have too much going on in your session.Ī lot of audio interfaces will allow one to record and monitor with no noticeable latency while turning up the buffer high enough that even an under-powered CPU can still handle most situations just fine. If you have a 15 year old low end CPU and 2GB of Ram, you probably shouldn't have even attempted to use it for recording (not meeting minimum system requirements). It would help if you listed your PC's specs. A lot of people are jumping on the CPU being the issue here, but it sounds like a buffer issue, which may or may not be related to the CPU. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |