n-Track Frequently Asked Questions

FAQ Index | Soundcards, software and hardware configuration

• Does n-Track have the ability to utilize quad-core or dual-core processing?
  
  

  Yes, n-Track takes advantage of quad core and dual core CPUs. The gain from switching from 2 to 4 cores depends on both the structure of the song(s) and the audio buffering used.
  The more channels (i.e. tracks, groups, auxs) and/or effects per channel you have, the more n-Track will be able to split the work among the available cores.
  
  Buffering comes into play because the less buffering you have the smaller must be the chunk of work that n-Track assigns to each core, so as buffering decreases the efficiency of splitting the work decreases too and you reach a point where it's faster to just use a single core. It's kind of like dividing work between people: if you have many dishes to wash you finish quicker if you many people and assign to each a portion of the available work. But if you put 4 people to wash 1 single dish you're likely to be slower than one lone washer.
  
  Again depending on the song and CPU type (speed, number of cores, cache, shared vs non-shared cache) the point where single core may perform better than multiple cores may be from 64 to 256 samples per buffer. You can test this by toggling the 'Multithreaded audio processing' box in Preferences/Options and then performing mixdowns of a test song and measuring the time each mixdown takes for decreasing buffering settings. Follows results mixing down a benchmark song on various systems. The benchmark song consists of the Sometimes n-Track sample song (that can be download from the download page), with an instance of the n-Track Reverb (with default preset) on each track (instead of on just a couple of tracks in the original song) to make the song more CPU heavy.
  
  

  • Hardware: Intel Core 2 Quad Q6600 / 2.4 GHz processor, 1066 MHz FSB, 8MB L2
    4 Gb RAM installed (3.25 Gb recognised by 32 bit XP) n-Track 32 bit on XP 32 Bit Service Pack 3, all meter windows closed.
    Measuring the time it takes to mixdown the whole song to a 16 bit .wav file.
    
    
    • 8192 x 4 (Default buffering)
      No multithread: 37 sec.
      Multithreaded: 15 sec. (60% speedup)
    • 256 x 2 buffering
      No multithread: 37 sec.
      Multithreaded: 22 sec. (40% speedup)
    • 128 x 2 buffering
      No multithread: 39 sec.
      Multithreaded: 29 sec. (26% speedup)
    • 64 x 2 buffering
      No multithread: 43 sec.
      Multithread: 41 sec. (5% speedup)
      
      
  • Hardware: Core 2 Duo T7300, 2.0 Ghz, 800 Mhz FSB, 4 Mb L2 Cache (shared between the 2 cores)
    4 Gb RAM n-Track 32 bit on x64 Vista, all meter windows closed.
    Measuring the time it takes to mixdown the whole song to a 16 bit .wav file
    
    
    • 8192 x 4 (Default buffering)
      No multithread: 42 sec.
      Multithreaded: 27 sec. (36% speedup)
    • 256 x 2 buffering
      No multithread: 47 sec.
      Multithreaded: 33 sec. (30% speedup)
    • 128 x 2 buffering
      No multithread: 50 sec.
      Multithreaded: 39 sec. (22% speedup)
    • 64 x 2 buffering
      No multithread: 55.4 sec.
      Multithread: 51.6 sec. (7% speedup)
      
      

  The speedup from using two cores instead of one decreases as the buffer size decreases, but it remains positive even for very low buffering. Adding a 2nd reverb for each track yields for 64 samples buffering 1:12 vs 1:30, i.e. 20% speedup, which means that increasing the song CPU load the relative advantage of using multiple CPU cores increases even for very small buffering.

  
  
  

FAQ Index | Soundcards, software and hardware configuration