Systemwide and True-Fi driver

Comments

5 comments

  • Avatar
    Matīss (Edited )

    Thanks for the feedback - we're super glad to hear that the calibration has improved your listening experience on your headphones!

    As to the drivers - we do support WASAPI, but ASIO support is also on the way (I know, some of the people will bash this, as we've promised ASIO for an embarrassingly long time now and never delivered it, but we are actually super close of having free development resources dedicated to it). I'll ask our QA department to test out WASAPI and Foobar2000/Liqube’s Resonic Player issues for you here and see if we can recreate this in-house.

    Which Windows version do you have?

    I'll update this post once I have some more details!

    0
    Comment actions Permalink
  • Avatar
    John Norris

    Thanks for the quick response!

    I'm using Windows 10 v1709 (Fall Creators Update).  More info - the WASAPI output works on Resonic and a player called "1 by 1".  It seems Foobar is the only one with an issue.  Are there guides to setting up Foobar to work reliably with SystemWide?

     

    One other quick question.  Are the headphone compensation profiles used by True-Fi and Reference 4 Headphone the same?

    0
    Comment actions Permalink
  • Avatar
    Matīss

    Thanks! So, it looks like you've found a bug that our developers will take a look at. For True-Fi this is next in line for the fixing. It seems that the main issue with not only Foobar2000 lies within exclusive mode that applications use to communicate with our driver, meaning that if an exclusive mode is used (it seems that in WASAPI mode this is set by default without a way to disable it in Foobar2000), volume control won't work, whilst disabling exclusive mode will bring the volume control back again, in software where it's possible

     

    The profiles between True-Fi and Reference 4 are the same, besides some True-Fi extra ones, that we decided to release for consumer product - those are the ones that we thought were not accurate enough to be used for referencing purposes but worked well for general improvement of sound.

    0
    Comment actions Permalink
  • Avatar
    John Norris

    Great, Matiss!  Thanks for the information.

    And while you have your bug-swatter out...

    I have SystemWide set to launch with Windows.  When you first log in to Windows, the SystemWide icon in the Notification Area doesn't respond to a left click.  You have to either right-click it first and cancel out of the options box, or run the SystemWide app from the Start Menu before you can left-click the icon to bring up the headphone selection and enable/disable dialog.

    I hope I've made myself clear.

    0
    Comment actions Permalink
  • Avatar
    Matīss

    Yeah, this is a common issue that we are aware of, but have not yet had time to take a look at it closer. Initially we thought that it's something to do with the time it takes driver to load up fully, but even after giving it a few minutes, it still takes two left-clicks to open up the initial pop-up. I'll poke around the development team and see if I can get this issue to move up the ladder. Thanks for informing :)

    0
    Comment actions Permalink

Please sign in to leave a comment.