Recommended Posts

3 hours ago, wetworker said:

Has anyone experience this.

When I have Dopamine playing music no other Audio plays on my computer, that includes YouTube videos.

The only way I can get YouTube audio is to kill both the browser and Dopamine.

 

I get the same results on FF,Chrome and Edge.

Maybe a problem with "Exclusive Mode" in the settings of Dopamine.

 

Works good on Windows 10 x64 14393.82 with a Asus Xonar U7 and Edge (headphones or speakers mode).

  • Like 1

Thanks for the response guys.  I tried the latest version but the only version that works is Version 1.0.0 (Build 650)

 

Thank goodness because I usually record my Street Fighter 5 game-play while Dopamine is playing. Even street Fighter would have no Audio if Dopamine was playing at launch.

 

16 hours ago, wetworker said:

Has anyone experience this.

When I have Dopamine playing music no other Audio plays on my computer, that includes YouTube videos.

The only way I can get YouTube audio is to kill both the browser and Dopamine.

 

I get the same results on FF,Chrome and Edge.

Did you enable "Exclusive mode" in the audio settings? All reports I got about sound issues in other apps are caused by the user enabling that mode. 

 

I wonder if I shouldn't just remove it, as I'm getting a lot of such reports. Exclusive mode is a WASAPI feature that allows direct access to your audio device. It should allows lower latency audio, but also takes exclusive access to the audio device (that's by WASAPI design), which means no other software can play audio while another application has  exclusive access.

 

Or maybe I should pop up an enormous warning when the user tries to enable this mode :) 

2 hours ago, wetworker said:

Thanks for the response guys.  I tried the latest version but the only version that works is Version 1.0.0 (Build 650)

That's strange. Dopamine has had exclusive mode since before that build. Could you verify that exclusive mode is disabled when you use the latest build? 

4 hours ago, Raphaël G. said:

That's strange. Dopamine has had exclusive mode since before that build. Could you verify that exclusive mode is disabled when you use the latest build? 

I can't remember turning  "Exclusive mode" on but it's possible I did.  In 1.0.0 (Build 650) "Exclusive mode" was turned off by default  because I did a clean install.

I also just updated to the latest version 1.1 ( Build 681) and I can now play YouTube audio while Dopamine is playing. "Exclusive mode" is also off. 

 

Yes maybe a message about  turning "Exclusive mode" on might help :) 

 

Thanks for the help.

  • Like 1

Hi everyone,

 

 

Another build has been released: 1.1 Build 685.

 

 

This is the changelog:

 

– [Added] Added a confirmation dialog when enabling WASAPI Exclusive mode
– [Added] Added Bitrate column on Songs screen
– [Fixed] Duplicate semantic Artist and Genre groups appear after performing a search
– [Fixed] Removed songs can still be played when pressing the play button

 

Only 2 issues remaining before the release of 1.1 final.

 

Download here.

 

Enjoy!

  • Like 4

I need some help :) I've been asked to add a "Shuffle all" button, a la Groove (see screenshot). I like the idea, as it would minimize the amount of clicks required to shuffle all songs of the collection. However, I can't find the best spot to add this, without breaking the design.

 

Where would you see this button?

shuffle all.png

On ‎27‎/‎08‎/‎2016 at 9:39 AM, Raphaël G. said:

I need some help :) I've been asked to add a "Shuffle all" button, a la Groove (see screenshot). I like the idea, as it would minimize the amount of clicks required to shuffle all songs of the collection. However, I can't find the best spot to add this, without breaking the design.

 

Where would you see this button?

shuffle all.png

You could try a combination with the other shuffle button, like repeat button ?

2 hours ago, accuratecopy said:

You could try a combination with the other shuffle button, like repeat button ?

Not sure. Pressing "Shuffle all" should immediately queue all songs. Th other shuffle just shuffles what's already queued. It might be confusing to combine both.

5 minutes ago, jasondefaoite said:

Raphaël, did you make a change for the Album Artist tag? I've re-added my entire collection back into the latest release and they are tagged based off the Artist if the Album Artist is blank, which is exactly what I needed. Great!!

Yes. Actually, somebody did it for me. The wonders of open source :) 

  • Like 4
On 8/27/2016 at 2:39 AM, Raphaël G. said:

I need some help :) I've been asked to add a "Shuffle all" button, a la Groove (see screenshot). I like the idea, as it would minimize the amount of clicks required to shuffle all songs of the collection. However, I can't find the best spot to add this, without breaking the design.

 

Where would you see this button?

shuffle all.png

I've seen some music players place the "shuffle All" option at the top of the music list (list goes "Shuffle All" then #d songs, As. etc) and I personally like it that way

On 27/08/2016 at 8:39 AM, Raphaël G. said:

I need some help :) I've been asked to add a "Shuffle all" button, a la Groove (see screenshot). I like the idea, as it would minimize the amount of clicks required to shuffle all songs of the collection. However, I can't find the best spot to add this, without breaking the design.

 

Where would you see this button?

shuffle all.png

It may not be completely obvious but shuffle all is already easily possible by simply opening up the app and then double clicking any song from the artists songs on the right whilst having shuffle enabled - this is how I've used Dopamine and probably MusiX from the start.

 

Other than that I think the only other possible option would be to maybe double press on the shuffle option? so you have three states to switch between - normal top to bottom, shuffle playlist, shuffle all and then back again?

A new preview is available: Dopamine 1.1 build 694 Preview.

 

This is the change log:

 

– [Added] Added customizable online search for videos and lyrics
– [Changed] Updated the Portuguese translation
– [Fixed] Playlist window visibility incorrect when switching between Mini players
– [Fixed] Left part of Mini player playlist is unclickable
– [Fixed] Bluetooth headset play/pause button not detected

 

Download here

 

Edit: I also fixed creation of multiple instances of Dopamine when changing audio device. That's however not listed in the change log as it was a regression from version 1.0.

On 8/30/2016 at 9:46 AM, Skiver said:

It may not be completely obvious but shuffle all is already easily possible by simply opening up the app and then double clicking any song from the artists songs on the right whilst having shuffle enabled - this is how I've used Dopamine and probably MusiX from the start.

 

Other than that I think the only other possible option would be to maybe double press on the shuffle option? so you have three states to switch between - normal top to bottom, shuffle playlist, shuffle all and then back again?

Your way of shuffling all, is indeed how I designed it since the beginning.

I'd like to avoid double press on the shuffle button. But thanks for thinking about it. This feature is so hard to add :) 

7 minutes ago, dakn said:

How's about like this? Combining Groove into your layout:

 

shuffle.png

 

Shuffle icon is a bit massive but it was a quick mock up :)

This idea makes sense :) Maybe not 100% like this, but it looks like a good spot to but the shuffle all button. I'll try it out tonight. Thanks!

6 minutes ago, dakn said:

^ That image highlights a small issue: Artist names are case sensitive.

Indeed. It has been logged :) : https://github.com/digimezzo/Dopamine/issues/63 

  • Like 1
3 minutes ago, Raphaël G. said:

This idea makes sense :) Maybe not 100% like this, but it looks like a good spot to but the shuffle all button. I'll try it out tonight. Thanks!

Indeed. It has been logged :) : https://github.com/digimezzo/Dopamine/issues/63 

I do use shuffle all a lot when I use Groove on the kitchen tablet but it's not something I've ever thought Dopamine needed due to what Skiver mentioned. Would still be a nice addition though. :)

@Raphaël G., how can I manually delete my library?

 

For the past two builds, Dopamine has wanted to scan my library each time I start the program. It scans the music and then proceeds to update the album covers, but this process never ends. And because of that I can't delete folders from the settings option, because it keeps saying "Refreshing your collection".

On 8/24/2016 at 9:59 AM, Raphaël G. said:

Did you enable "Exclusive mode" in the audio settings? All reports I got about sound issues in other apps are caused by the user enabling that mode. 

 

I wonder if I shouldn't just remove it, as I'm getting a lot of such reports. Exclusive mode is a WASAPI feature that allows direct access to your audio device. It should allows lower latency audio, but also takes exclusive access to the audio device (that's by WASAPI design), which means no other software can play audio while another application has  exclusive access.

 

Or maybe I should pop up an enormous warning when the user tries to enable this mode :) 

I think you most definitely should keep it. I, personally, much prefer a warning dialogue—and actually think it's a good idea—over losing such an important feature.

  • Like 1
2 hours ago, Setnom said:

@Raphaël G., how can I manually delete my library?

 

For the past two builds, Dopamine has wanted to scan my library each time I start the program. It scans the music and then proceeds to update the album covers, but this process never ends. And because of that I can't delete folders from the settings option, because it keeps saying "Refreshing your collection".

Can you send me your logfile? I'd like to know what it is trying to do.

You can delete Dopamine.db. You can find it in folder %appdata%\dopamine

 

1 hour ago, Jub Fequois said:

I think you most definitely should keep it. I, personally, much prefer a warning dialogue—and actually think it's a good idea—over losing such an important feature.

I decided to keep it. There is a warning popup now since a few builds.

  • Like 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!