Bongiovi DPS

Bongiovi DPS 2.2 – The Gaming Release

Forums Bongiovi DPS 2.2 Bongiovi DPS 2.2 – The Gaming Release

This topic contains 22 replies, has 9 voices, and was last updated by  xaqmusic 28 minutes ago.

Viewing 8 posts - 16 through 23 (of 23 total)
  • Author
  • #83939


    Works great!
    As always, thanks for such a speedy fix, Joey!



    V# doesn’t want to run on my mac Mini (late 2012) running Mojave (latest v#)



    Not sure if it’s a bug, expected behaviour or a problem with my system, but on my Mac (High Sierra 10.13.6) DPS seems to preventing the PC from sleeping. I’ve run ‘pmset -g assertions’ and I get this:
    BackgroundTask 1
    ApplePushServiceTask 0
    UserIsActive 1
    PreventUserIdleDisplaySleep 1
    PreventSystemSleep 0
    ExternalMedia 1
    PreventUserIdleSystemSleep 1
    NetworkClientActive 0

    The details referring to ‘PreventUserIdleSystemSleep’ are:

    pid 196(coreaudiod): [0x0002480d000199c9] 00:00:10 PreventUserIdleSystemSleep named: “,0,1,2:0.context.preventuseridlesleep”
    Created for PID: 42489.
    pid 196(coreaudiod): [0x0002480d000199c1] 00:00:10 PreventUserIdleSystemSleep named: “”
    Created for PID: 42489.
    pid 196(coreaudiod): [0x000245dc000199ac] 00:09:31 PreventUserIdleSystemSleep named: “,0,1,2:0.context.preventuseridlesleep”
    Created for PID: 42481.

    If I quit DPS, then the Mac sleeps according to the power saving settings.

    Any thoughts?




    Let me know if you had any success with Our tests show it working well in Mojave. Please send console output if it is crashing.


    Bongiovi DPS will prevent sleep while the audio stream is open. This is necessary to capture every sound from all applications at the moment those sounds are generated. To get around the sleep issue, Bongiovi DPS will look for silence in the audio stream. You will see these messages in the console. If silence is detected for 5 minutes the stream will stop so sleep is allowed. At that point, your normal sleep timer will kick in and your Mac should sleep as usual. Let me know if you do not see that behavior.



    Sorry but subscription model is absurd given how little updates you guys make to the app. Paying 30€ a year for nearly no updates to the app is just absurd quite frankly. It took over a year and a half for update from 2.1 to 2.2. And I bet they fixed none of the stupid volume problems I’ve been having where volume levels are all screwed up when you boot the system up, nearly giving me a heart attack when Windows does “doink” sound at 3 in the morning at full volume on powerful speakers…



    And yup, you haven’t fixed ANYTHING. Rebooted system and volume of Bongiovi was at 75% even though it was at 30% when I rebooted the system. With soundcard volume at 100% (so I can at least get any kind of decent volume out of the system and fully control volume through keyboard volume buttons), this means I’m gonna kill someone at night for turning on a PC. Get your shit together before you try charging money for your broken app. This is the reason why I haven’t bought it before (v2.1) and it’ll remain a reason why I’m not buying it now either at v2.2… How the hell app doesn’t remember last set volume level and just stubbornly insists on 75% is just absurd.



    Oh god, not only that, it also turns parent soundcard volume to 10% every time. Who designed this idiocy? Useless.



    Thanks for taking the time to share, rejor. You have hit upon an issue that had dogged us for almost a decade now; Windows audio driver volume handling.

    UPDATE: To address your issue at the top of this very long post, please try this:

    Regarding the subscription and price and such, this was a necessary step for us to move the Bongiovi DPS app forward. You may not see it on the surface, but the audio processing changes under the hood between 2.1 and 2.2 are significant. I’m happy to discuss V3D, the new Virtual Subwoofer algorithm, and the myriad of gaming-centric profiles.

    Back to Windows volume control. We describe the audio system like this:.
    Windows drviers and audio path.

    On Mac computers, I think we achieved a nice level of “it just works”. This is due to the consistent nature of all Mac computers and the sensible way their Core Audio engine works. In Windows, its a lot different.

    On a Windows computer, the output driver that is set to Default Playback device receives the volume control messages from the keyboard. As you can see in the diagram, the Digital Power Station driver must be the default device so we may process the audio and send it out to the hardware device (laptop speakers, USB headphones, HDMI etc). So what do we do when DPS is launched and the hardware driver is set to some low level? If we just leave that driver’s volume as-is, that driver (let’s say it’s your laptop speakers) will be “stuck” there without keyboard volume level control. No matter how much you turn up the volume (affecting the DPS driver only) the volume will be limited to that set previously for your laptop speakers. On a laptop that’s a big problem since they are already really quiet!

    To overcome this we set the output device to 75% and bring the previous volume level of that output over to the Digital Power Station driver. This works well enough for most folks but we are now seeing a trend of Windows 10 computer manufacturers making “smart” audio systems that try to manage the audio devices for you. Also, we have to contend with several different audio chip manufacturers that (unlike Apple) do not publish their system messages for when a device (like plugging in headphones) is connected or disconnected.

    That is why we added a checkbox in the SETTINGS tab for disabling automatic volume adjustment. Read about it here.

    I hope that turning off this feature-for-some-annoyance-for-others will make your audio experience better with Bongiovi DPS! Please contact Joe or Dan by making a support ticket and they will take care of you.

    We are totally open to suggestions regarding the Windows volume issue! We understand there is no one-size-fits-all solution that is not overly complex. I have had these ideas in mind:

    1 – Take a system settings snapshot: This would save all of the volume levels for all of the drivers. You could set this snapshot to be recalled whenever the app launches or when you switch to different output modes.

    3 – Provide a specialized DPS volume control: We could provide volume sliders on the GUI for each hardware device so you could easily set and recall the volume level. The downside is a more cluttered SETTINGS tab that deviates from the Mac version.

    4 – INI file: For the power users out there, an editable initialization file could override any default behavior so all volume levels at startup are explicitly set.

    5 – A combination of all of the above?

    Let me know what you think!

Viewing 8 posts - 16 through 23 (of 23 total)

You must be logged in to reply to this topic.