Jump to content

Oleg Karavan

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. It looks like something happened to the cooling system. May be thermal paste is dried out?
  2. First of all, 40 degrees is totally not "crazy hot". Look at your CPU's specification on the manufacturer's website and find what maximum operational temperature is allowed. Most likely it will be more than 70 degrees. Second of all, what you see as CPU usage shows only CPU time usage, but not how it's blocks are used and how. Applications that make a lot of computations (like DAWs) typically use vector instructions like AVX and SSE. They process data much faster due to parallelism, but also consume more power per instruction. Most of the non compute intensive applications don't create this type of workload for CPU, therefore for them CPU consumes less power. And the third. Cooling system must handle worst case scenario. But in many many situations CPU is underused, even it is 100% busy. That means you have to stress-test it by using some benchmark application, that can create worst-case workload for CPU in terms of power consumption.
  3. When I make two exports with the same driver mode, they are binary identical (compared them with "fc /b" command). I close-open Cakewalk before export to avoid possible internal timing offsets. So yes, with this song TTS-1 renders exact same binary output every time. But for some reason changing driver mode somehow impacts offline rendering. And I can't get why this happening. I also checked old version (Cakewalk Music Creator 6), and it behaves the same way - results are equal (close enough considering dithering) for one driver mode, and differs for different. How Cakewalk desides, what data format to request from VSTi/DXi? I thought it is "Render Bit Depth" parameter in settings.
  4. I found that TTS-1 output (on export) differs depending on what driver mode is chosen for output: ASIO or MME. When I subtract one result from another, I see separate occasional notes from time to time, while pauses between them are completely silent. How this option can impact export results at all? And why the difference is like that? All I can imagine is MME forces 16-bit mode only, and Cakewalk uses this information as the default bit resolution for projects containing only software instruments. But in Trasport module in both cases I see 24 bit.
  • Create New...