1. 30 Jun, 2021 1 commit
  2. 27 Jun, 2021 1 commit
  3. 26 Jun, 2021 4 commits
    • David Reid's avatar
    • David Reid's avatar
      Update test code. · 1597f6c0
      David Reid authored
      1597f6c0
    • David Reid's avatar
      Improvements to the async notification system. · 5df38de8
      David Reid authored
      These changes expand on the notification system which allows a program
      to be notified on when a sound has reached various stages in the async
      loading process. There are two stages:
      
        1) Decoder initialization
        2) Completion of decoding
      
      The previous system has the following problems:
      
        * There's no way to wait on only the decoder initialization
        * The callback doesn't work well if you want to pass it through
          multiple layers. Example:
          - Client wants to wait for the sound to complete
          - Pass the callback into ma_sound_init_from_file(), which passes
            it into ma_resource_manager_data_source_init(). The latter will
            fire the callback, but will do so before ma_sound_init_from_file()
            has returned. The client will think the sound has finished
            loading and will reference the `ma_sound` object before it's
            completed initialization.
        * It's not easy to wait on object in bulk. Clients may want to pump a
          bunch of ASYNC sounds in one go, and then just have a single
          notification for the group.
      
      The new system introduces the notion of a "fence". A fence contains a
      counter which is incremented and decremented from anywhere. It also has
      a wait routine which will block until the counter hits zero:
      
        ma_fence_acquire() - Increments the counter
        ma_fence_release() - Decrements the counter
        ma_fence_wait()    - Blocks until the counter is 0.
      
      The fence system can be used to wait for a number of sounds to finish
      decoding rather than only one at a time, which is the case with the
      previous system. Example:
      
      ```
      /* Fences must be initialized before use. */
      ma_fence_init(&fence);
      
      /* Loop over each sound and start loading them, passing in the fence. */
      for each sound in sounds
      {
          flags = MA_DATA_SOURCE_FLAG_DECODE | MA_DATA_SOURCE_FLAG_ASYNC;
          ma_sound_init_from_file(&engine, pFilePath, flags, &group, &fence, &sound);
      }
      
      ... do some other stuff while sounds are loading ...
      
      /* Wait for sounds to finish loading. */
      ma_fence_wait(&fence);
      ma_fence_uninit(&fence);
      ```
      
      The above example initializes a sound, but it can also be used by
      resource managed data sources. When loading data sources directly from
      the resource manager, you can specify a second fence which is used to
      only wait until the internal decoder has been initialized.
      5df38de8
    • David Reid's avatar
      Simplify async notifications. · b4d6c37d
      David Reid authored
      b4d6c37d
  4. 24 Jun, 2021 4 commits
  5. 22 Jun, 2021 1 commit
  6. 20 Jun, 2021 9 commits
  7. 19 Jun, 2021 4 commits
  8. 17 Jun, 2021 1 commit
  9. 13 Jun, 2021 7 commits
  10. 11 Jun, 2021 2 commits
  11. 09 Jun, 2021 4 commits
  12. 08 Jun, 2021 2 commits