Steps for Reproduction
This can depend on your machine's specific drivers and player settings.
Some additional details are needed here:
-Do you use WASAPI or DirectSound?
-Which buffer settings do you have in Helium?
-Which soundcard do you use and which OS are are you using?
Settings of the player should not be changed after installation:
Soundcard: Realtek High Definition Audio.
Driver Provider: Realtek Semiconductor Corp.
Driver Version: 184.108.40.20686
All Effects for the device are disabled.
Output Quality: 24 Bit, 192000 Hz
Installed: Sound Blaster X-Fi MB5 Version 1.00.11
Using build in speakers of the notebook.
OS: Windows 10 Pro 1703
My Screnshots are not visible in the last post. I will try it again. In the previous post they were somehow inserted twice (Ctrl+V), so I had removed the second inserted one but it looks like it remove all them. Strange behaviour of the posting text editor.
#1 Options at the reporting time
#2 Options, that solved my problem
>> Should I expect any problems by disabling of WASAPI?
No. WASAPI (Windows Audio Session API) is Microsofts hardware interface which works directly against sound devices using the providers unique drivers.
Simplified, when active in Helium, Helium will work as a bridge when playing music - just forwarding data to WASAPI which is responsible to pick and use the proper replaying routines.
When DirectSound is used, playback will be handled within Helium using a software mixer. (Using DirectSound's replaying engine)
For more specific WASAPI details, please google it.
Thanks for the information Mikael.
For me the solution was DirectSound.
I have the exact same problem as OP.
Steps to reproduce: Play song 1, then pause it, then start playback on song2: song1 will play for X seconds before song 2 starts playing. The "X seconds" I'm talking about here depends on how much seconds you've set the buffer to. If it's 1.5 seconds, the song will play for 1.5 seconds before the next song starts playing. If you've set it to 8 seconds, it will literally take 8 seconds before the next song starts playing.
The problem here is with the buffer. I don't know if this feature is just bugged or something. It also doesn't help that there's no way to completely disable this (no buffer at all) as the minimum is 0.5 seconds.
Using DirectSound is NOT the solution. I guess it might depend on your setup, but using DirectSound on my DAC results in worse audio quality.