Recommended Posts

Hi all, I've been playing with the playlists of the Mini players. This is what I have up till now. This is not a mockup, but still a draft. I'm thinking how to further organize things. For the Cover player, the playlsit appears left or right of the player, depending on where there is space. For the Micro and Nano player it appears at the bottom or top, again depending on space and position. The space between main window and playlist is necessary to avoid shadow overlap. This setup works. It is now a matter of deciding the look of the contents of the playlist.

 

cover player playlist.png

micro player playlist.png

Edit: suggestions and ideas are welcome.

Tested it, i love that, especially the changes on the cover player :). I have a suggestion, could you add an option to show the playlist under the player on the cover player?

I knew you could do it! Testing the new changes now, so far so good =) It's awesome!

 

I glad you like it :)

Yeah but .png is fine.

I'll add png and ico for the blue and white icon. That way people can choose.

  • Like 1


Thanks for a new nightly build!!
Testing it now on Windows 10 build 10558 :rofl:

I wait for the next PC and mobile builds, i hope it will be released tonight :)


I'm using the new nightly build of Dopamine (build 414), and i still have problems with borders and windows.
- Borders: The left and the top borders are still doubled, right and bottom are fine :)
- Windows: On the cover player, the playlist window is horizontally smaller than the cover window when the 1px border option is on, i use playlist vertically align on the bottom of cover player.

 

I wait for the next PC and mobile builds, i hope it will be released tonight :)


I'm using the new nightly build of Dopamine (build 414), and i still have problems with borders and windows.
- Borders: The left and the top borders are still doubled, right and bottom are fine :)
- Windows: On the cover player, the playlist window is horizontally smaller than the cover window when the 1px border option is on, i use playlist vertically align on the bottom of cover player.

 

yeah the doubling of borders is caused because I enable a UI parameter to avoid blur at any desktop scaling level (100 %, 125 % and 150 %). If I disable that parameter, the borders are fine, but other parts of the UI become blurred. Conclusion: it will cost lots of time to fix, so for now it's delayed for later.

Edit: ok I see what you mean for the window size with border enabled.

Edited by Raphaël G.
  • Like 1

yeah the doubling of borders is caused because I enable a UI parameter to avoid blur at any desktop scaling level (100 %, 125 % and 150 %). If I disable that parameter, the borders are fine, but other parts of the UI become blurred. Conclusion: it will cost lots of time to fix, so for now it's delayed for later.

Edit: ok I see what you mean for the window size with border enabled.

Ok, not a problem, i have disabled borders for the moment, until you have a fix to provide :)

In the cover player configuration with playlist on the bottom, i have a black rectangle at the top of the playlist window behind the search bar, the number of tracks and a part of the track which is at the top of the playlist. It seems to appear and disappear creating a kind of flickering of the playlist window.

I have another question about tags:

- I use the ";" separator in my tags (Ex: when i have more than 1 artist on a track, i put "artist1; artist2" in the "artist" tag), seems like Dopamine can't read "artist2".
- I often rip vinyls and use "A1; A2; B1; ..." tags in "track number" tag, and sometimes the "0" track number when a track is hiding before 1st track on some CDs, seems like Dopamine can't handle it.
 

Ok, not a problem, i have disabled borders for the moment, until you have a fix to provide :)

In the cover player configuration with playlist on the bottom, i have a black rectangle at the top of the playlist window behind the search bar, the number of tracks and a part of the track which is at the top of the playlist. It seems to appear and disappear creating a kind of flickering of the playlist window.

I have another question about tags:

- I use the ";" separator in my tags (Ex: when i have more than 1 artist on a track, i put "artist1; artist2" in the "artist" tag), seems like Dopamine can't read "artist2".
- I often rip vinyls and use "A1; A2; B1; ..." tags in "track number" tag, and sometimes the "0" track number when a track is hiding before 1st track on some CDs, seems like Dopamine can't handle it.
 

Can you explain the black bar a little more? The first nightly had a non-transparent background behind the counter and searchbox, the latest nightly doesn't have this anymore?

How do other players handle multiple artists and track numbers? I only handle the first. I thought the tracknumer tag should just contain a number.

Can you explain the black bar a little more? The first nightly had a non-transparent background behind the counter and searchbox, the latest nightly doesn't have this anymore?

How do other players handle multiple artists and track numbers? I only handle the first. I thought the tracknumer tag should just contain a number.

I can reproduce it with white theme sometimes a plain background or some rectangles appear, there are problems with transparent background, when scrolling the songs in the playlist.

In Foobar2000, ";" are remplaced by ",", it is showed on the same column.
For the track numbers, i don't know if it should just contain a number.

I can reproduce it with white theme sometimes a plain background or some rectangles appear, there are problems with transparent background, when scrolling the songs in the playlist.

In Foobar2000, ";" are remplaced by ",", it is showed on the same column.
For the track numbers, i don't know if it should just contain a number.

What does A1; A2; B1; mean in you tracknumber tag?

I wait for the next PC and mobile builds, i hope it will be released tonight :)


I'm using the new nightly build of Dopamine (build 414), and i still have problems with borders and windows.
- Borders: The left and the top borders are still doubled, right and bottom are fine :)
- Windows: On the cover player, the playlist window is horizontally smaller than the cover window when the 1px border option is on, i use playlist vertically align on the bottom of cover player.

 

Could you test the latest nightly (build 416)? I fixed both these issues (at least it looks right on my computer). I'd like to know if it's fixed for you too.

What does A1; A2; B1; mean in you tracknumber tag?

for vinyl rips this would refer to side a and side b. I don't think it's any kind of real tagging standard, but I've often seen vinyl rips tagged that way (A or B preceding track number in track number tag)

for vinyl rips this would refer to side a and side b. I don't think it's any kind of real tagging standard, but I've often seen vinyl rips tagged that way (A or B preceding track number in track number tag)

Exactly!

Could you test the latest nightly (build 416)? I fixed both these issues (at least it looks right on my computer). I'd like to know if it's fixed for you too.

Everything seems to be fixed, i'll report you if i find anything else! Great work! :)

I just had a crash of Dopamine, freshly opened on cover player, clicking on the "next" button to switch track. Dopamine window disappeared.
Here is the log on this period:

2015-10-07 12:42:01.3444|Info|Dopamine.Application.ExecuteStartup|### STARTING dopamine, version 1.0.0 (Build 416). IsPortable = False ###
2015-10-07 12:42:02.9917|Info|Dopamine.Common.Services.Playback.PlaybackService+VB$StateMachine_100_DeleteRuntimeFilesAsync.MoveNext|Deleting runtime files.
2015-10-07 12:42:03.7603|Info|Synapse.Synapse.Main|<<< Synapse indexer started >>>
2015-10-07 12:42:03.7708|Info|Synapse.Synapse.Main|Validating process
2015-10-07 12:42:03.7808|Info|Synapse.Synapse.ValidateProcess|Commandline argument 1: IgnoreRemovedFiles = True
2015-10-07 12:42:03.7808|Info|Synapse.Synapse.Main|Initializing WCF proxies
2015-10-07 12:42:03.8388|Info|Synapse.Synapse.Main|Notifying the main application that the indexer is started
2015-10-07 12:42:03.9812|Info|Synapse.Synapse.Main|Waiting for the database
2015-10-07 12:42:03.9892|Info|Synapse.Synapse.WaitForDatabase|C:\Users\antho\AppData\Roaming\Dopamine\Dopamine.db was found. Proceeding.
2015-10-07 12:42:03.9892|Info|Synapse.Synapse.Main|Initializing the Indexing Worker
2015-10-07 12:42:06.3786|Info|Synapse.Synapse.Main|Initializing the LifeBeat Timer
2015-10-07 12:42:06.3786|Info|Synapse.Synapse.Main|Starting the LifeBeat Timer
2015-10-07 12:42:06.3786|Info|Synapse.Synapse.Main|Updating collection
2015-10-07 12:42:06.3940|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_27_IndexCollectionAsync.MoveNext|+++ STARTED INDEXING COLLECTION +++
2015-10-07 12:42:30.9325|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_27_IndexCollectionAsync.MoveNext|Tracks removed: 0. Time required: 24532 ms +++
2015-10-07 12:43:13.0846|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_27_IndexCollectionAsync.MoveNext|Tracks updated: 0. Time required: 32815 ms +++
2015-10-07 12:43:14.1395|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_27_IndexCollectionAsync.MoveNext|Tracks added: 11. Time required: 1051 ms +++
2015-10-07 12:43:15.1180|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_27_IndexCollectionAsync.MoveNext|+++ FINISHED INDEXING COLLECTION: Tracks removed: 0. Tracks updated: 0. Tracks added: 11. Time required: 68718 ms +++
2015-10-07 12:43:15.1250|Info|Dopamine.Common.Services.Indexing.IndexingService.OnRefreshLists|Sending event to refresh the lists
2015-10-07 12:43:15.1355|Info|Synapse.Synapse.Main|Updating artwork
2015-10-07 12:43:15.1421|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_29_IndexArtworkAsync.MoveNext|+++ STARTED INDEXING ARTWORK +++
2015-10-07 12:43:15.4937|Info|Dopamine.Core.Indexing.Indexer+VB$StateMachine_29_IndexArtworkAsync.MoveNext|+++ FINISHED INDEXING ARTWORK: Covers deleted from database: 0. Covers deleted from disk: 0. Covers updated: 1. Time required: 348 ms +++
2015-10-07 12:43:15.4982|Info|Dopamine.Common.Services.Indexing.IndexingService.OnRefreshArtwork|Sending event to refresh the artwork
2015-10-07 12:43:15.5017|Info|Synapse.Synapse.Main|Notifying the main application that the indexer is stopped
2015-10-07 12:43:15.5017|Info|Synapse.Synapse.Main|Stopping the LifeBeat Timer
2015-10-07 12:43:15.5017|Info|Synapse.Synapse.Main|Closing WCF proxies
2015-10-07 12:43:15.5152|Info|Synapse.Synapse.Main|<<< Synapse indexer NORMAL stop >>>

One thing I've noticed from the 416 nightly build is that it doesn't save the position, nor the size of the window once you restart or close Dopamine. I'm hoping this is a bug and won't become a default thing.

If that ever happens, it's a bug. I couldn't live with it not remembering its position myself :). I did some changes after build 416 concerning positioning. It seems to behave here. But I'll keep an eye on it.

  • Like 1

Hi all,

A new Dopamine build is available. This is the changelog:

7-10-2015: Dopamine 1.0.0.424 (Preview)

- Improved handling of tags
- Put the Mini Player playlists in separate window again
- Added extra white and blue icons in .ico and .png format for shortcuts and docks
- When hovering the scrollbars, the mouse cursor changes to a hand.
- Fixed issues when using desktop scaling higher than 100%

Download here

For the next build I'll be focusing on this:

- Display album artists in the list of artists
- Add an option to show notifications only when the main window is visible, or any time
- Bugs, of course
 

Let's keep it simple for the next build. After these changes the code is ready to add rating and tagging.

  • 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

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      FloatingFatMan
      67
  • Tell a friend

    Love Neowin? Tell a friend!