![]() ![]() the data transfer to a recording interface is done via a serial bus system (PCIe, USB, Firewire, Thunderbolt), which takes time. This problem also depends on other things like system load or also how the DAW has been coded and is able to distribute the DAW load efficiently across many cores.Ģ. If the driver occupies a CPU core for too long where also an audio related task is waiting for execution on this CPU, then you can get problems and audio loss occurrs if audio can not be processed in time. Some drivers are written good, but not all. Instead of this its pure programming conventions when a driver detaches from a CPU. The various drivers run on highest execution priority and may not be interrupted by a process scheduler for e.g. Both operating systems are not real-time operating systems by design. ![]() Now with a PC or even Apple computer, several things come together:ġ. With an Eventide, everything is built discretely and you will achieve the latency values reliably and independend on any "load" situation, that on a PC can easily occurr, as it has also to process many other things and drivers and settings might not be optimum. My overall impression is that your expectations of a PC recording system are too high overall if you expect to be able to achieve the same low latency values of a hardware-only solution with a PC. Let it run for 10 minutes, then the values are more accurate and its more likely to catch a spike issues by background processes or scheduled tasks.įor a final validation let it run for several hours. All that I can say is to use it on an IDLE system as this tool itself creates already a DAW load on its own. It needs some experience to use this tool. If you want to measure the agility of your system and whether your system is suited for audio, then you can use LatencyMon, you can find a lot of threads here in the forum. It is very different from system to system, best is to contact a company which is specialized for audio PCs, then you can expect least hassles. tweaking can take time and in some cases the design/BIOS of a mainboard can be bad, so that even the best tweaking can have limitations that results in a difference of around 200+ microseconds latency (or not), sounds less, but on system level this makes a difference how agile the system can react on a concrete workload especially drivers and different versions of the same driver can have severe impact in terms of DPC latencies only some settings can be generalized / recommended for every system > and if so, what are the windows or driver tweaks i could do to achieve this? Has anyone managed to use buffer 32 without pops ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |