[Snowsky Melody] Device disconnects within WolfEQ every time a EQ preset is set/saved.

[mafclean]

First

I would like to say THANK YOU VERY MUCH, @audioslayer, for making this application available. I know that this project is mainly for the FiiO K13, but as soon as I bought a Melody unit, I was in search for an offline application that could help us, Windows 10 users, to use all the available features that the Melody DAC/AMP has to offer us; and, until now, I only found yours. You see, I am not a smartphone user (nor owner), so I really appreciate the opportunity to have the Melody EQ available on Windows. So, I commend you for the initiative and altruist favor to help us out with your software, since even FiiO did not do this (yet?!).

Second

WolfEQ IS working with Snowsky Melody; at least for the EQ feature section that I used. I have used the PEQ with no problems whatsoever, so far, for what I needed. I was also able to create and/or export/import FiiO's XML files into it with no problem (but I might add that FiiO's website cannot recognize the XML of the exported WolfEQ, since the header is different — although this is not the point of this issue, and I will create another issue later only for this topic of the XML files).

Third (the issue)

The main point of this topic is to register the issue that I am having while using the Melody on Windows 10: the DAC/device becomes "not detected" within the WolfEQ application every time a EQ preset is set/saved; making me always in the need to go to Settings again, then click Detect (the device), before being able to set/save another EQ preset.

These are the screenshots explaining my exact actions:

• Action 01: WolfEQ is opened. Device begins as 'disconnected' while the last set preset is showing (Metal - ENERGETIC Bass).

• Action 02: I need to go to Settings to Detect device again. Device profile does NOT change every time I open WolfEQ. It saves the last device used as expected.

• Action 03: Device gets connected/detected again by WolfEQ, after I press Detect.

• Action 04: Getting back to the Tune page, the first preset is already set (Metal - ENERGETIC Bass) while the device/DAC is detected by WolfEQ.

• Action 05: Changed the preset Metal - ENERGETIC Bass to Metal - LOW Bass.

• Action 06: As soon as the new preset is saved, the device/DAC gets disconnected/undetected.

And here again I need to repeat the whole process every time I make a change to any preset and/or I make any changes to the PEQ — that does not register any of the changes until I detect the device again and save the preset. Is this the expected behavior?!

PS: I am not a professional developer, but I am, in a way or another, a technical guy. So when you need me to do something to help investigate this issue deeper, I am m your guy in any way that I can — just fire it up!

Again, thank you, @audioslayer !

My Specs & Setup

• Computer: ASUS TUF F-15 (2022 edition).
• OS: Windows 10 IoT Enterprise LTSC, version 21H2 (Build: 19044.5247 / Dec, 2024).
• Headphones: FiiO FT1 (updated version, 2025+).
• USB Mode: FT1 connected to Melody via 3.5mm audio jack; Melody connected to laptop via USB-C.
• Melody Configuration: 2 channels, 24bit/96000Hz, with no spatial sound enhancements.
• Melody Firmware Version: 1.1.0 — latest as of today (July, 02 - 2026).
• Other details: I have a 15.6" display with a resolution of 1920x1080 with a 150% scale and layout.

[audioslayer]

Nice Screenshots, I will get this fixed. Hop in the discord, if possible, so i can send you a test build. I am free all weekend! My name is audio in the discord.

[mafclean]

Hi, @audioslayer ! Nice. Thank you very much for your expertise!

As for Discord, unfortunately, I am not a user anymore, since 2024, because they keep asking for a smartphone number to authenticate — something I cannot do because I do not even own a smartphone. I am sorry!

If it is not too much of a hassle, could/would you annex the testing builds here?! I know it can be done, but if you do not want to, or think this would be unwanted for you and the project, we can find another way.

[audioslayer]

Hi @mafclean — no problem at all, here is a direct download instead of Discord.

Test build with the fix (WolfEQ 0.3.0 beta):

• Download: https://plexwolf.duckdns.org/assets/wolfeq-test-builds/WolfEQ-0.3.0-Test.zip
• Test build page (notes + checksums): https://plexwolf.duckdns.org/assets/wolfeq-test-builds/
• SHA256: 0440edd2519db814a32a9d07ec52921061087bced96aa0af99d08dfa17cd81fc

It is a self-contained Windows x64 zip — unzip anywhere and run WolfEQ.exe, no install needed.

What changed for this issue:

• The Melody is now treated as a save-only profile, so WolfEQ no longer forces a device EQ readback right after a preset save — that readback is what left the device stuck as "not detected".
• After a save, WolfEQ now waits up to ~30 seconds for the Melody to settle and reconnects automatically, so you should not need to go to Settings → Detect between saves anymore.

What I would love you to try:

1. Save an EQ preset to a USER slot from the Tune page and confirm the device stays connected afterward.
2. Change the PEQ and save again a few times in a row without touching Settings, and confirm each change is audible on the device.

If it still drops, please attach %LOCALAPPDATA%\WolfEQ\logs\wolfeq.log and a screenshot of the status log. I'll leave this issue open until you can confirm the fix on your hardware. Thanks again for the detailed report!

[mafclean]

Hey, @audioslayer ! Sorry for the delay (residence moving month).

Here are the results and the sequence of the testing I did following your orders:

Written Sum-up

1. I open WolfEQ. Device starts Disconnected.

2. I try to Detect the device. Device is detected for a few (less than 5) seconds, then it disconnects itself.

3. [While device is still disconnected] I choose a preset from the library or change the PEQ by modulating the graphic; in both instances I am not able to Write to USER 1 (that stays grayed out).

4. [While device is still disconnected, but the library preset is set or PEQ is changed] I click Detect, device gets connected, and now Write to USER 1 lights up green for me to click it, but then again the device disconnects itself a few seconds later (as step 2).

5. [While device is still disconnected, but the library preset is set or PEQ is changed] I click Detect, device gets connected, Write to USER 1 lights up green for me to click it, I now immediately proceed to click Write to USER 1 while I am still able to (and I click it). Changes proceed to take place and are audible within maybe 2 seconds after and device never again disconnects from now on until I close WolfEQ again.

Screenshot Actions

• Action 01: I open WolfEQ. Device starts Disconnected.

• Action 02: I try to Detect the device. Device is detected for a few (less than 5) seconds, then it disconnects itself.

• Action 03: [While device is still disconnected] I choose a preset from the library or change the PEQ by modulating the graphic; in both instances I am not able to Write to USER 1 (that stays grayed out).

• Action 04: [While device is still disconnected, but the library preset is set or PEQ is changed] I click Detect, device gets connected, and now Write to USER 1 lights up green for me to click it, but then again the device disconnects itself a few seconds later (as step 2).

• Action 05: [While device is still disconnected, but the library preset is set or PEQ is changed] I click Detect, device gets connected, Write to USER 1 lights up green for me to click it, I now immediately proceed to click Write to USER 1 while I am still able to (and I click it). Changes proceed to take place and are audible within maybe 2 seconds after and device never again disconnects from now on until I close WolfEQ again.

And from there on, the device never gets undetected/disconnected again (until I quit WolfEQ and start all over again). While I have "sync to the user profile" activated (WolfEQ is connected with Melody), I can change the PEQ or choose another library preset and just click Write to USER 1 every time and it proceeds to change and work every time with no problems.

Logs

I am annexing the wolfeq.log of these exact actions until I close WolfEQ.

---

I think this is it?! If I did something wrong, or didn't do something, please, just ask me to and I will do/redo anything you need me to. Okay?!

Again, thank you very much @audioslayer !

I really appreciate it, and I am here at your service.