1
General Discussion / Re: [CHANGES MADE] Not So Neo Output Mixer & 24-bit
« on: December 06, 2025, 10:54:33 AM »
Leave it, maybe you'll come back to it someday 
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
General Discussion / Re: [CHANGES MADE] Not So Neo Output Mixer & 24-bit
« on: December 06, 2025, 10:08:04 AM »
Just updated. For now, everything looks good, but the bit depth setting to "AS IS" only stays until we play a FLAC track, then it changes to 24bit, and even if we play an MP3 later, it changes to 16bit. I don't know if that's how it's supposed to be. I look at the behavior of the sampling frequency setting, set to "AS IS" it remains as such all the time.
3
General Discussion / Re: Not So Neo Output Mixer & 24-bit
« on: November 30, 2025, 11:23:04 AM »
However, from my observations, there seems to be some dark magic that wasn't there before.
First, all FLAC files are detected as 24-bit in the input format if Playback > Allow 24-bit is cheecked. For example, WAV files are detected as 16-bit if they're 16-bit, and PCM24 if they're 24-bit. The user setting from the drop-down list works the opposite way. Selecting 16-bit sets 32-bit, and selecting 32-bit sets 16-bit. 24-bit works fine.
Let's say we set the output format to 24-bit, but when we play something like an MP3, the setting changes to 16-bit and remains there even when the next track is FLAC, which is actually 24-bit. You have to manually set 24-bit each time.
First, all FLAC files are detected as 24-bit in the input format if Playback > Allow 24-bit is cheecked. For example, WAV files are detected as 16-bit if they're 16-bit, and PCM24 if they're 24-bit. The user setting from the drop-down list works the opposite way. Selecting 16-bit sets 32-bit, and selecting 32-bit sets 16-bit. 24-bit works fine.
Let's say we set the output format to 24-bit, but when we play something like an MP3, the setting changes to 16-bit and remains there even when the next track is FLAC, which is actually 24-bit. You have to manually set 24-bit each time.
4
General Discussion / Re: Not So Neo Output Mixer & 24-bit
« on: November 29, 2025, 11:54:10 PM »
I was just about to write that I'll wait until the next build in hopes that it will be fixed.
Thanks, it works.
Thanks, it works.
5
General Discussion / Re: Not So Neo Output Mixer & 24-bit
« on: November 28, 2025, 10:20:15 AM »
Sorry for the delay. I was trying to figure out what the problem was, and as it turns out, it's not just 24-bit. I'm getting crackling on various tracks at different bit resolutions and sample rates. It looks like overdrive, and I figured out that simply changing the master gain to -0.1 dB is enough to fix everything. I'll just add that all the settings are default: DRC, AGC, etc., are OFF, and all levels are at 0 dB.
I've tested it on various outputs—Direct, Wavey, YASAPI—and it's the same everywhere. No problem bypassing the mixer. No crackling.
That's one thing, but more importantly, what happened today immediately after updating to 23234: no signal on the SL/SR mixer output. It's impossible to set the output to 2/2 - quadro. After closing preferences and re-entering, the setting reverts to AS IS (no change)
x86, build 23234 from today.
I've tested it on various outputs—Direct, Wavey, YASAPI—and it's the same everywhere. No problem bypassing the mixer. No crackling.
That's one thing, but more importantly, what happened today immediately after updating to 23234: no signal on the SL/SR mixer output. It's impossible to set the output to 2/2 - quadro. After closing preferences and re-entering, the setting reverts to AS IS (no change)
x86, build 23234 from today.
6
General Discussion / [CHANGES MADE] Not So Neo Output Mixer & 24-bit
« on: August 28, 2025, 11:55:54 PM »
Does "Not So Neo Output Mixer" support 24-bit?
In my experience, it doesn't... I have crackling on 24-bit WAV/FLAC.
In my experience, it doesn't... I have crackling on 24-bit WAV/FLAC.
7
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: August 20, 2025, 09:27:50 PM »
Just for the record, latest build fixed my loading problem and the previous one fixed the streaming issue.
8
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: July 28, 2025, 09:49:40 PM »
Up until version 22222, I never had a problem with streaming. The way my radio playlists from bookmarks are displayed has changed. Now, they seem to display part of the URLs after the last slash.
The top is as it looks now, and the bottom is as it was before.
The top is as it looks now, and the bottom is as it was before.
9
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: July 28, 2025, 05:10:47 PM »
As before, about a week ago, the problem resolved itself. Unfortunately, it returned immediately after updating to 22222 the day before yesterday, if I remember correctly. It also started crashing while streaming the radio. I have some dumps from the crash report, which I'll send you.
10
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: July 17, 2025, 12:02:12 PM »
I mentioned dual monitor desktop because I run WACUP on a secondary monitor, and when this problem occurs during startup, I often see a black media library background (!?) on the primary monitor for a moment, and then nothing, because it stops responding. After half a minute, it reappears on the secondary monitor, but often in stages, because, for example, everything appears except the contents of the media library window.
I did a few OS restarts and it seems that when I run WACUP in safe mode, the problem doesn't occur. It takes a bit longer to start, taking ~3 seconds, but it doesn't go to not responding state.
I did a few OS restarts and it seems that when I run WACUP in safe mode, the problem doesn't occur. It takes a bit longer to start, taking ~3 seconds, but it doesn't go to not responding state.
11
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: July 14, 2025, 11:47:47 AM »
I was wondering if it had something to do with dual monitor desktop, but the problem occurs when running on both primary and secondary.
12
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: July 14, 2025, 09:14:56 AM »
Unfortunately, the problem returned right after updating to 22022. I have a ProcDump dump, I will send you the file via PM.
13
Resolved Issues / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: June 10, 2025, 11:17:35 AM »
A few days ago the problem disappeared, just like that. I didn't change anything in the config or anything at all. I run WACUP every morning and get to work, usually it starts on the Bookmarks screen, then I start one of my favorite radio streams. The system and the program start from a fast NVMe drive, I have the media library on another large HDD drive. Folders with files are added to "Folder Monitor", but monitoring is inactive. I prefer adding folders via Local library>Import folder... That's all I can say, at the moment I am unable to reproduce the problem, previously it was as above, the first start after logging into Windows took ~30 seconds, the program hung in the "Not responding" state at that time.
14
Resolved Issues / [FIXED] 1.99.32.21640 (x86) issue when launching: taking too long to load
« on: May 15, 2025, 06:40:18 PM »
I have another problem related to launching after updating to the latest version. The first start of the WACUP after logging into Windows takes me over 30 seconds from clicking the program icon. After closing it starts quickly every time.
15
General Discussion / Re: Winamp ML import
« on: January 06, 2025, 07:42:11 PM »
I'll answer here. Now everything is in the right place, thanks. I refreshed the metadata for all items and everything still looks fine. I remembered one thing, after I did the import legacy via WACUP the original db files in the Winamp folder was overwritten with an empty one. A backup of the files was created (I made my own anyway) but it was still a disturbing experience. 
Pages: [1] 2