Recommended Posts

6 hours ago, Raphaël G. said:

Could you test if Preview 9 improves this? I silently released preview 9 here.

I tested something as a whim, when my monitor is @60hz it works fine, but when I bump my refresh rate up to 144hz or 165hz it doesn't work.  So @ 60hz it's working great.  Not sure why it would not work at a higher refresh rate...

Spectrum Analyzer bug:
 

I have a duel monitor setup, one is 1080p @ 60hz, the other is 1440p @ 166hz, there is a bug in the NVidia drivers that causes stuttering in windows when two displays are using different refresh rates.  I tested this bug with both monitors @ 60hz and everything works fine.  When I bumped my main monitor up to 165hz is when the stuttering starts in Spectrum Analyzer.  I suspect this issues is being caused by the NVidia driver.  I have only seen this behavior in the edge browser for video playback, the new Chromium browser somehow is not affected by this bug.

Nvidia bug info

@Ravensky Thank's a lot for this information! That might explain why I have problems reproducing it on my computer. I've updated the issue information on the Dopamine GitHub: https://github.com/digimezzo/Dopamine/issues/987

 

It's indeed, not clear why it only happens on now playing.

 

Edit:

 

@Ravensky and @Jackaluichi,

 

Unfortunately I don't have any monitor which has a framerate higher than 60. So can I ask the following?

Could you try out the build that I put on my dropbox: https://www.dropbox.com/sh/fqvqotogo2jv7kr/AAC54ENOFA89y78d30bMihRWa?dl=0

That build is also called "preview 9" and you should be able to install it over your current version. That build removes the image on now playing. I'd like to know if that improves the situation.

 

Thank you!

@RavenskyThanks for all the information, mate.

 

I also have a dual monitor setup, a 24" Dell 60Hz, but it's almost always switched off, and my main one is an UltraWide 2560x1080 144 Hz. My graphics card, however, is a Radeon RX Vega 56, so I don't think this is a problem exclusive to NVIDIA drivers. I have just tested using a refresh rate of 60 Hz, and just like in your case the problem dissappears. But I've also discovered something else. Even while keeping the refrest rate at 144 Hz, if I close Dopamine in the 'Now Playing' section, when I open it again and press play, the problem goes away as well, but it returns as soon as I switch to any other section within Dopamine.

 

Cheers!

5 minutes ago, Raphaël G. said:

@Ravensky and @Jackaluichi,

 

Unfortunately I don't have any monitor which has a framerate higher than 60. So can I ask the following?

Could you try out the build that I put on my dropbox: https://www.dropbox.com/sh/fqvqotogo2jv7kr/AAC54ENOFA89y78d30bMihRWa?dl=0

That build is also called "preview 9" and you should be able to install it over your current version. That build removes the image on now playing. I'd like to know if that improves the situation.

 

Thank you!

I've just tested it, and I'm afraid it doesn't make any difference at all.

23 minutes ago, Jackaluichi said:

I've just tested it, and I'm afraid it doesn't make any difference at all.

Thanks! So I can rule that one out.

 

Your observation about starting on now playing, and then opening another screen is quite interesting. In that case, does the stutter happen on another screen than the now playing screen?

6 minutes ago, Raphaël G. said:

Thanks! So I can rule that one out.

 

Your observation about starting on now playing, and then opening another screen is quite interesting. In that case, does the stutter happen on another screen than the now playing screen?

In that case, when I go back to the general view the stutters happen for a brief moment and then they just go away on their own. This bug seems like one of the most weird ones I've come across in a while.

7 minutes ago, Jackaluichi said:

In that case, when I go back to the general view the stutters happen for a brief moment and then they just go away on their own. This bug seems like one of the most weird ones I've come across in a while.

Very strange indeed. How is the spectrum analyzer on the cover and the micro player?

While Dopamine is running and playing music on the Now Playing screen if I switch from 60hz to 120hz or 144hz or 165hz it will instantly start stuttering, (not the music playback just the analyzer) and when I switch back to 60hz while it is still playing it will correct itself and run fine.  So it is definitely tied to the refresh rate of the monitor.  If Dopamine is on the default playback window there is no affect at any refresh rate it just works fine on all.

Hi everyone!

 

Dopamine 2.0 preview 10 is ready for consumption. This release has a very short, but interesting, change log:

 

– [Fixed] Lyrics “Search again” doesn’t work
– [Fixed] High CPU and memory usage

 

For this preview, I spent quite some time optimizing memory en CPU usage. On my test system, this was a success. Hopefully this preview treats you as well as it did me 🙂

 

Enjoy!

 

As always, you can download it here

  • Like 2
  • Thanks 1

Another preview is available. I've been handling small annoyances that some people reported. Here's the change log:

 

– [Fixed] Short sound after starting up
– [Fixed] Zero-sized images which are embedded in audio files, are mistakenly treated as valid images.

 

Download here

 

 

  • Like 1
  • Thanks 1
2 hours ago, Raphaël G. said:

Another preview is available. I've been handling small annoyances that some people reported. Here's the change log:

 

– [Fixed] Short sound after starting up
– [Fixed] Zero-sized images which are embedded in audio files, are mistakenly treated as valid images.

 

Download here

 

 

Thanks, Raphaël! 😄
How's the spectrum analyzer stutter's investigation going? 🤔

58 minutes ago, Jackaluichi said:

Thanks, Raphaël! 😄
How's the spectrum analyzer stutter's investigation going? 🤔

Not good :( I have no idea how to explain what is going on. Also, the fact that I don't have the tools to reproduce it, doesn't help.

21 hours ago, Raphaël G. said:

Not good :( I have no idea how to explain what is going on. Also, the fact that I don't have the tools to reproduce it, doesn't help.

If I were rich, I would give you a 144 Hz monitor away 😜

1 hour ago, Jackaluichi said:

If I were rich, I would give you a 144 Hz monitor away 😜

Hehe thanks :) But no need. I'll find another way somehow. Maybe some other developer can assist. You aren't a developer by any chance? :)

41 minutes ago, kukata said:

@Raphaël G. Hello! When starting the player a brief moment (2-3 secs) from a song of the last played album is been played. He's been having this problem for a long time. It's not the new build.

Preview 11 is also doing that? I hoped I fixed that in preview 11.

Made this account just to ask, so sorry if that's frowned upon in this forum, but I might stick around because the community seems cool 😀

 

I've downloaded Dopamine to replace VLC and from what little time I've used it it seems awesome already, but when I try to make Dopamine the default audio player in the "Default apps" menu as well as in the control panel, it doesn't show up on the list of programs able to be selected. Additionally, searching for Dopamine in the search bar only brings up the playlist folder it creates in "C:\Users\[NAME]\Music", but not the application file itself or its own folder I installed it to.

 

I've also tried using file association in the control panel, much to the same effect of being brought back to the frustrating metro "Default apps" menu.

 

There's no problem running the program at all as far as I can tell (I pretty much downloaded it just a week ago and fiddled with it off and on), but not being able to make it the system-recognized default is kind of a bummer. I haven't found this issue with anyone else, but then again I've been known to have very specific problems nobody else has, so could it be an install problem, perhaps?

 

Sorry for long post. I have no idea what this forum's etiquette is. Every forum is different.

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!