Recommended Posts

Hi people,

 

Small status update. This has been done since the last build (no new build yet, needs more testing):

 

- Sound is now played by a separate process called "Axon"
- Adjusted some timings for a smoother experience
- Fixed several small bugs
- Added total song duration and size information

 

And a screenshot, notice something?

 

 

New dopamine.png

  • Like 2
9 hours ago, Ravensky said:

I had to restore my music folder from a backup recently I didn't have it all backed up... now my music database is all messed up, how do I reset it? Does it adjust and reset itself?

It depends what changed. Files which Dopamine cannot find on disk anymore, are automatically removed from the collection, new files will be added. Files which have a last modification date which is different from the one in the database, will be updated. To manually reset your collection, you'll have to delete Dopamine.db. I've been meaning to provide a reset button, but delayed it :)

10 hours ago, Ravensky said:

8NsYmmA.png

 

Looks nice =)

 

Yes i needed that info lately when creating a playlist for a party and making sure I have enough hours of music. I'm not 100% sure about the positioning yet. Still killing brains cells over that.

20 hours ago, Raphaël G. said:

Hi people,

 

Small status update. This has been done since the last build (no new build yet, needs more testing):

 

- Sound is now played by a separate process called "Axon"
- Adjusted some timings for a smoother experience
- Fixed several small bugs
- Added total song duration and size information

 

And a screenshot, notice something?

 

 

New dopamine.png

Damn! I can't notice what's new on the screenshot, except total song duration and size information, which is really convenient!

2 hours ago, Ravensky said:

so you have a music player for OSX, and a music player for Windows, are you going to make one for Linux next? lol

 

OSX?  have never seen anything like that on his site.

19 hours ago, TAZMINATOR said:

That was old name which he replaced it with Dopamine.

Indeed :) MusiX was my first attempt at creating a Music player. I began programming in .NET back then and learned a lot by creating that player. Eventually I learned so much, that I realized its internals were crap. So I started from scratch and renamed that new project to Dopamine.

hi, can i ask something that may be a very simple feature, but i can't figure it out.

if i just want to play all of my songs in my library on shuffle, how does one do that? it seems like you have to pick an album, artist, or song to play, but there's no master play button just to start playing everything.

thanks

7 hours ago, Ravensky said:

From the artists page, click the shuffle icon, and click play... at least that works for me.

Yeah, that way, or: when no artist or album is selected, all songs are shown on the right. Double click a song and all songs a queued. The rule is: when you start playing a song by double click, all shown songs are queued.

Work in progress. New build soon.

Work in progress.png

 

- Sound is now played by a separate process called "Axon"
- Adjusted some timings for a smoother experience
- Fixed several small bugs
- Added total song duration and size information
- Updated the French translation
- The spectrum analyzer on the Now playing screen becomes taller when the controls are hidden
- The spectrum analyzer is more responsive
- Added cover background on the now playing screen

And here it is! A new build is available:

 

17-01-2016: Dopamine 1.0.0.547 (Preview)
 

  • Sound is now played by a separate process called “Axon”
  • Adjusted some timings for a smoother experience
  • Fixed several small bugs
  • Added total song duration and size information
  • Updated the French translation
  • The spectrum analyzer on the Now playing screen becomes taller when the controls are hidden
  • The spectrum analyzer is more responsive
  • Added cover background on the now playing screen

Download and info over here: http://raphaelgodart.tumblr.com/dopamine

  • Like 3

The previous version and this update are both causing my system to slow down, and my screen to go fuzzy, like very fine white noise on a TV.

This only happens while Dopamine is in the foreground.

I'll do a fresh install in a bit.

I just updated.  It's still working great.  I did finally try out the tag editor, and it edited the tags but the changes didn't appear in the library; I had to delete and recreate the database to refresh it.

 

While I like the sorting by year I still wish I could group it by year and sort each group by album artist like I did in Zune.

 

Thanks for your hard work.  This is still the most fantastic audio player for Windows by a mile.  If you ever move forward on the mobile app you might want to consider adding support for OneDrive streaming so it can replace Groove, though, but that is an entirely different project.

2 hours ago, Darrian said:

I just updated.  It's still working great.  I did finally try out the tag editor, and it edited the tags but the changes didn't appear in the library; I had to delete and recreate the database to refresh it.

 

While I like the sorting by year I still wish I could group it by year and sort each group by album artist like I did in Zune.

 

Thanks for your hard work.  This is still the most fantastic audio player for Windows by a mile.  If you ever move forward on the mobile app you might want to consider adding support for OneDrive streaming so it can replace Groove, though, but that is an entirely different project.

Thanks for the feedback. Could you tell e exactly which tags you changed and from which one of the screens? I'd like to reproduce that issue.

I was in the Album view.  I changed tags on two albums.  To do this I highlighted all the tracks in the playlist and right-clicked>edit.  The only tag I changed was the year.  One album had extra digits appended to the year and the other album didn't have the year tagged.  They are all aac audio in the m4a container.

17 minutes ago, Darrian said:

I was in the Album view.  I changed tags on two albums.  To do this I highlighted all the tracks in the playlist and right-clicked>edit.  The only tag I changed was the year.  One album had extra digits appended to the year and the other album didn't have the year tagged.  They are all aac audio in the m4a container.

Thanks! I'll try that out tonight.

8 hours ago, FiB3R said:

The previous version and this update are both causing my system to slow down, and my screen to go fuzzy, like very fine white noise on a TV.

This only happens while Dopamine is in the foreground.

I'll do a fresh install in a bit.

Let me know how the clean install goes. That's some strange things you got there.

 

Could you give me some details about your system? (mostly interested in cpu, gpu, windows version, gpu driver).

Hey there!

 

I got an error with build 547 when i tried to play my first song with this release. When i tried again, it worked (FYI my files are on a NAS and i use last Insider Preview of Windows 10). Here is the log, if it can help :).

 

Spoiler

2016-01-18 19:28:45.7271|Info|Dopamine.Application.ExecuteStartup|### STARTING Dopamine, version 1.0.0 (Build 547). IsPortable = False ###
2016-01-18 19:28:46.2810|Info|Dopamine.Views.Splash+VB$StateMachine_15_InitializeSettingsAsync.MoveNext|Upgrading settings
2016-01-18 19:28:47.2480|Info|Axon.Axon.Main|CorePlayerService was started successfully
2016-01-18 19:28:47.6479|Info|Dopamine.Bootstrapper.InitializeWCFServices|CommandService was started successfully
2016-01-18 19:28:47.6629|Info|Dopamine.Bootstrapper.InitializeWCFServices|IndexingService was started successfully
2016-01-18 19:28:47.6629|Info|Dopamine.Bootstrapper.InitializeWCFServices|FileService was started successfully
2016-01-18 19:28:47.6754|Info|Dopamine.Bootstrapper.InitializeShell|Showing Main screen
2016-01-18 19:28:47.7199|Info|Dopamine.Common.Services.Indexing.IndexingService.TryStartIndexer|Trying to start the indexer.
2016-01-18 19:28:48.1082|Info|Synapse.Synapse.Main|<<< Synapse indexer started >>>
2016-01-18 19:28:48.1317|Info|Synapse.Synapse.Main|Validating process
2016-01-18 19:28:48.1432|Info|Synapse.Synapse.ValidateProcess|Commandline argument 1: IgnoreRemovedFiles = True
2016-01-18 19:28:48.1432|Info|Synapse.Synapse.Main|Initializing WCF proxies
2016-01-18 19:28:48.1753|Info|Synapse.Synapse.Main|Notifying the main application that the indexer is started
2016-01-18 19:28:48.1913|Info|Synapse.Synapse.Main|Waiting for the database
2016-01-18 19:28:48.1913|Info|Synapse.Synapse.WaitForDatabase|C:\Users\antho\AppData\Roaming\Dopamine\Dopamine.db was found. Proceeding.
2016-01-18 19:28:48.2068|Info|Synapse.Synapse.Main|Initializing the Indexing Worker
2016-01-18 19:28:50.2482|Error|Dopamine.Common.Services.Indexing.IndexingService.CheckLifeBeatTimerElapsed|There was no Indexer LifeBeat for more than 1 seconds. Stopping the indexing.
2016-01-18 19:28:51.2627|Info|Synapse.Synapse.Main|Initializing the LifeBeat Timer
2016-01-18 19:28:51.2627|Info|Synapse.Synapse.Main|Starting the LifeBeat Timer
2016-01-18 19:28:51.2707|Info|Synapse.Synapse.Main|Indexing collection
2016-01-18 19:28:51.2707|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_15_IndexTracksAsync.MoveNext|+++ STARTED INDEXING COLLECTION +++
2016-01-18 19:28:55.3091|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_15_IndexTracksAsync.MoveNext|Tracks removed: 0. Time required: 4023 ms +++
2016-01-18 19:28:56.8353|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_15_IndexTracksAsync.MoveNext|Tracks updated: 0. Time required: 706 ms +++
2016-01-18 19:28:56.8568|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_15_IndexTracksAsync.MoveNext|Tracks added: 0. Time required: 16 ms +++
2016-01-18 19:28:57.0297|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_15_IndexTracksAsync.MoveNext|+++ FINISHED INDEXING COLLECTION: Tracks removed: 0. Tracks updated: 0. Tracks added: 0. Time required: 5744 ms +++
2016-01-18 19:28:57.0497|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_16_IndexArtworkAsync.MoveNext|+++ STARTED INDEXING ARTWORK +++
2016-01-18 19:28:57.1318|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_16_IndexArtworkAsync.MoveNext|+++ FINISHED INDEXING ARTWORK: Covers deleted from database: 0. Covers deleted from disk: 0. Covers updated: 0. Time required: 74 ms +++
2016-01-18 19:28:57.1693|Info|Synapse.Synapse.Main|Notifying the main application that the indexer is stopped
2016-01-18 19:28:57.1833|Info|Synapse.Synapse.Main|Stopping the LifeBeat Timer
2016-01-18 19:28:57.1898|Info|Synapse.Synapse.Main|<<< Synapse indexer NORMAL stop >>>
2016-01-18 19:29:17.8631|Info|Dopamine.Common.Services.Update.UpdateService.EnableUpdateCheck|Update check: checking for updates. AlsoCheckForPreReleases = False
2016-01-18 19:29:17.8815|Info|Dopamine.Common.Services.Update.UpdateService+VB$StateMachine_16_CheckForUpdatesAsync.MoveNext|Update check: current version = 1.0.0.547
2016-01-18 19:29:19.4620|Info|Dopamine.Common.Services.Update.UpdateService+VB$StateMachine_16_CheckForUpdatesAsync.MoveNext|Update check: latest online version = 0.0.0.0
2016-01-18 19:29:19.4620|Info|Dopamine.Common.Services.Update.UpdateService+VB$StateMachine_16_CheckForUpdatesAsync.MoveNext|Update check: no newer version was found.
2016-01-18 19:30:17.4680|Error|Axon.Axon.LifeBeatTimer_Elapsed|There was no LifeBeat for more than 1 seconds. Stopping now.
2016-01-18 19:30:17.5221|Error|Dopamine.Common.Services.Playback.PlaybackService.LifeBeatTimerElapsed|Could not send lifebeat to player application. Exception: L'objet de communication System.ServiceModel.Channels.ServiceChannel ne peut pas être utilisé pour la communication car il est dans l'état Faulted.
2016-01-18 19:30:17.5221|Error|Dopamine.Common.Services.Playback.PlaybackService.TryPlay|Could not stop the Player
2016-01-18 19:30:17.6073|Error|Dopamine.Common.Services.Playback.PlaybackService.TryPlay|Could not play the file \\Diskstation\mp3-m4a\Albums\I\In Flames\In Flames-Soundtrack To Your Escape-CD-2004-M4A\03-in flames-dead alone.m4a. LoopMode=None, Shuffle=False. Exception: Une erreur s'est produite lors de la lecture du canal : Erreur non reconnue 109 (0x6d).. StackTrace:
Server stack trace:
   à System.ServiceModel.Channels.PipeConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
   à System.ServiceModel.Channels.DelegatingConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
   à System.ServiceModel.Channels.SessionConnectionReader.Receive(TimeSpan timeout)
   à System.ServiceModel.Channels.SynchronizedMessageSource.Receive(TimeSpan timeout)
   à System.ServiceModel.Channels.TransportDuplexSessionChannel.Receive(TimeSpan timeout)
   à System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceive(TimeSpan timeout, Message& message)
   à System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   à System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

 

Exception rethrown at [0]:
   à System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   à System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   à Dopamine.Core.Audio.IPlayer.Play(String iUri)
   à Dopamine.Common.Services.Playback.PlaybackService.TryPlay(TrackInfo iTrackInfo)

 

However, i love the new version!

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

    • It's amazing that anyone still uses this bloated trash.
    • @Sayan...I have defended you at various points as I hope you know. This headline however is utter trash...shame on you sir!
    • An actual cosmic "Eye of Sauron" had been looking straight at us all along by Sayan Sen Image by Kovin P. Vasquez via Pexels | Not representative An international team of researchers has solved a long-standing mystery surrounding a distant blazar known as PKS 1424+240, helping explain why it produces some of the brightest high-energy gamma rays and cosmic neutrinos ever observed despite appearing to have a relatively slow-moving jet. The findings were published on June 6 in Astronomy & Astrophysics Letters. The study addresses a broader challenge in astrophysics: understanding how extreme cosmic objects accelerate particles to very high energies and produce very high-energy (VHE) photons and neutrinos. PKS 1424+240 is located billions of light-years from Earth. It has attracted attention for years because it is both a powerful source of VHE gamma rays and the brightest known neutrino-emitting blazar in the sky, according to observations by the IceCube Neutrino Observatory. It is also associated with one of the strongest peaks in IceCube's nine-year neutrino sky map A blazar is a type of active galactic nucleus powered by a supermassive black hole that pulls in surrounding matter and launches jets of plasma moving close to the speed of light. What makes blazars unique is their orientation. One of their jets points almost directly toward Earth, making them appear exceptionally bright across the electromagnetic spectrum and allowing scientists to study some of the most extreme physical processes in the Universe. The scientists exclaimed it's like the 'Eye of Sauron' in deep space. Usually, the brightest gamma-ray-emitting blazars are expected to have jets that appear to move very quickly. However, radio observations of PKS 1424+240 suggested that its jet was moving much more slowly, creating a contradiction that became part of a long-running problem known as the "Doppler factor crisis." To investigate, researchers analyzed 15 years of observations from the Very Long Baseline Array (VLBA), a network of 10 radio antennas spread across the continental United States, Hawaii and St. Croix. Using a technique called Very Long Baseline Interferometry (VLBI), astronomers combine signals from widely separated radio telescopes to create a virtual Earth-sized telescope capable of revealing extremely fine details. The team combined 42 polarization-sensitive radio images collected between 2009 and 2025, creating a much deeper and more detailed view of the jet than had previously been possible. The observations were carried out as part of MOJAVE (Monitoring Of Jets in Active galactic nuclei with VLBA Experiments), a long-running program that studies the brightness, polarization and magnetic field structures of jets produced by active galaxies. The project aims to better understand how activity near supermassive black holes is linked to high-energy radiation and neutrino emission. “When we reconstructed the image, it looked absolutely stunning,” said Yuri Kovalev, lead author of the study and Principal Investigator of the European Research Council-funded MuSES project at the Max Planck Institute for Radio Astronomy. “We have never seen anything quite like it — a near-perfect toroidal magnetic field with a jet, pointing straight at us.” The image revealed an unusual geometry. The researchers found that Earth lies almost directly in line with the jet, with a viewing angle of less than 0.6 degrees. In simple terms, astronomers are looking almost straight down the jet. This turned out to be the key to the mystery. Because the jet is aimed almost directly at Earth, a relativistic effect called Doppler boosting dramatically increases its apparent brightness. The study found that this effect boosts the emission by a factor of about 30 while also making the jet appear slower than it actually is. “This alignment causes a boost in brightness by a factor of 30 or more,” said Jack Livingston, a co-author at the Max Planck Institute for Radio Astronomy. “At the same time, the jet appears to move slowly due to projection effects — a classic optical illusion.” The nearly head-on view also gave scientists a rare look at the jet's magnetic field. Using polarized radio signals, they detected a clear toroidal, or doughnut-shaped, magnetic field component. The observations suggest the jet carries an electric current and that its magnetic field helps launch, shape and stabilize the flow of plasma. Researchers believe this magnetic structure may also play a key role in accelerating particles to energies high enough to produce both gamma rays and neutrinos. “Solving this puzzle confirms that active galactic nuclei with supermassive black holes are not only powerful accelerators of electrons, but also of protons — the origin of the observed high-energy neutrinos,” Kovalev said. The research was conducted under the MuSES (Multi-messenger Studies of Energetic Sources) project, which investigates how active galactic nuclei accelerate particles and generate different cosmic signals, including light and neutrinos. Scientists say understanding how protons are accelerated and linked to neutrino production remains one of the major unanswered questions in astrophysics. The findings help explain why some blazars can appear to have slow jets while still producing extremely bright high-energy emissions. More broadly, the study strengthens the link between relativistic jets, magnetic fields, gamma rays and high-energy neutrinos. Researchers say the results provide new clues about how some of the Universe's most powerful natural particle accelerators work and offer important insights for multimessenger astronomy, which combines different types of cosmic signals to study extreme events in space. Source: European Research Council, EDP Sciences This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Gotenks98 is right... Outlook (new) is absolute trash. Doesn't Mozilla have an Enterprise Version of Firebird?
  • Recent Achievements

    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
    • One Month Later
      pestcontrol46 earned a badge
      One Month Later
    • Week One Done
      pestcontrol46 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      273
    3. 3
      Skyfrog
      75
    4. 4
      +Edouard
      72
    5. 5
      FloatingFatMan
      68
  • Tell a friend

    Love Neowin? Tell a friend!