• Screwtape's avatar
    Update to v104r06 release. · afa8ea61
    Screwtape authored
    byuu says:
      - gba,ws: removed Thread::step() override¹
      - processor/m68k: move.b (a7)+ and move.b (a7)- adjust a7 by two, not
        by one²
      - tomoko: created new initialize(Video,Audio,Input)Driver() functions³
      - ruby/audio: split Audio::information into
      - ws: added Model::(WonderSwan,WonderSwanColor,SwanCrystal)()
        functions for consistency with other cores
    ¹: this should hopefully fix GBA Pokemon Pinball. Thanks to
    SuperMikeMan for pointing out the underlying cause.
    ²: this fixes A Ressaha de Ikou, Mega Bomberman, and probably more
    ³: this is the big change: so there was a problem with WASAPI where
    you might change your device under the audio settings panel. And your
    new device may not support the frequency that your old device used. This
    would end up not updating the frequency, and the pitch would be
    The old Audio::information() couldn't tell you what frequencies,
    latencies, or channels were available for all devices simultaneously, so
    I had to split them up. The new initializeAudioDriver() function
    validates you have a correct driver, or it defaults to none. Then it
    validates a correct device name, or it defaults to the first entry in
    the list. Then it validates a correct frequency, or defaults to the
    first in the list. Then finally it validates a correct latency, or
    defaults to the first in the list.
    In this way ... we have a clear path now with no API changes required to
    select default devices, frequencies, latencies, channel counts: they
    need to be the first items in their respective lists.
    So, what we need to do now is go through and for every audio driver that
    enumerates devices, we need to make sure the default device gets added
    to the top of the list. I'm ... not really sure how to do this with most
    drivers, so this is definitely going to take some time.
    Also, when you change a device, initializeAudioDriver() is called again,
    so if it's a bad device, it will disable the audio driver instead of
    continuing to send samples at it and hoping that the driver blocked
    those API calls when it failed to initialize properly.
    Now then ... since it was a decently-sized API change, it's possible
    I've broken compilation of the Linux drivers, so please report any
    compilation errors so that I can fix them.
Last commit
Last update
docs Loading commit data...
higan Loading commit data...
hiro Loading commit data...
icarus Loading commit data...
libco Loading commit data...
nall Loading commit data...
ruby Loading commit data...
shaders Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
CONTRIBUTING.md Loading commit data...
README.md Loading commit data...
mkdocs.yml Loading commit data...