title: waveOut (Win32API) and multithreading
body: <p>I cannot find any information about the thread-safety of the waveOut API.</p>
  
  <p>After i creating new waveOut handle, i have those threads:</p>
  
  <p>Thread 1: Buffers handling. Uses those API functions:</p>
  
  <ul>
  <li>waveOutPrepareHeader</li>
  <li>waveOutWrite</li>
  <li>waveOutUnprepareHeader</li>
  </ul>
  
  <p>Thread 2: Gui, Controller thread. Uses those API functions:</p>
  
  <ul>
  <li>waveOutPause</li>
  <li>waveOutRestart</li>
  <li>waveOutReset</li>
  <li>waveOutBreakLoop</li>
  </ul>
  
  <p>Those two threads are running while using concurrently the same waveOut handle.
  In my tests, i didn't saw any problem with the functionality, but it doesn't mean that it safe.</p>
  
  <p>Is this architecture thread-safe?
  Is there any documentation about the thread safety of the waveOut API?
  Any other suggestions about the waveOut API thread-safety?</p>
  
  <p>thanks.</p>