starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 16:56:02 +03:00

[GH-ISSUE #1168] Activating visualizer and restarting the song results in significant volume increase #673

New issue

Closed

opened 2026-02-26 02:33:55 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 02:33:55 +03:00

Owner

Originally created by @fschlaef on GitHub (Jan 7, 2020).
Original GitHub issue: https://github.com/koel/koel/issues/1168

Describe the bug
When visualizer is enabled, changing, restarting or simply moving forward or backward in the song results in a significant volume increase, which cannot be traced to an actual change in volume anywhere in Koel (the volume slider and equalizer doesn't change) or the system.

This only happens when visualizer is enabled and only works once (i.e the volume doesn't keep increasing)

To reproduce

Start a song
Enable visualizer
Move forward or backward in the song using Koel's progress bar
Volume increases noticeably

Expected behavior
No change in volume.

Environment

Koel version 4.2.2
OS: Debian Sid
Browser: Chrome 79
PHP version 7.3.12
Node version 12.14.0

Originally created by @fschlaef on GitHub (Jan 7, 2020). Original GitHub issue: https://github.com/koel/koel/issues/1168 **Describe the bug** When visualizer is enabled, changing, restarting or simply moving forward or backward in the song results in a significant volume increase, which cannot be traced to an actual change in volume anywhere in Koel (the volume slider and equalizer doesn't change) or the system. This only happens when visualizer is enabled and only works once (i.e the volume doesn't keep increasing) **To reproduce** 1. Start a song 2. Enable visualizer 3. Move forward or backward in the song using Koel's progress bar 4. Volume increases noticeably **Expected behavior** No change in volume. **Environment** - Koel version 4.2.2 - OS: Debian Sid - Browser: Chrome 79 - PHP version 7.3.12 - Node version 12.14.0

kerem

2026-02-26 02:33:55 +03:00

closed this issue
added the
[Type] Bug
label

kerem commented

2026-02-26 02:33:55 +03:00

Author

Owner

@phanan commented on GitHub (Jan 8, 2020):

Huh? That's interesting :D I'll take a look later.

@phanan commented on GitHub (Jan 8, 2020): Huh? That's interesting :D I'll take a look later.

kerem commented

2026-02-26 02:33:55 +03:00

Author

Owner

@BrookeDot commented on GitHub (Apr 22, 2020):

I was able to reproduce this in 4.3.0 but only in Safari on macOS not in Firefox or Chromium. Of note, once the volume was changed by the Visualizer the volume slider had no additional effect until the page was refreshed.

Unfortunately I'm not seeing any warnings in the console. @fschlaef do you have any warnings or errors that can help to track this down?

@BrookeDot commented on GitHub (Apr 22, 2020): I was able to reproduce this in 4.3.0 but only in Safari on macOS not in Firefox or Chromium. Of note, once the volume was changed by the Visualizer the volume slider had no additional effect until the page was refreshed. Unfortunately I'm not seeing any warnings in the console. @fschlaef do you have any warnings or errors that can help to track this down?

kerem commented

2026-02-26 02:33:56 +03:00

Author

Owner

@acjohnson commented on GitHub (Oct 28, 2020):

I am having the same behavior as described and am running Koel version 4.4.0 using Firefox and Chrome on Ubuntu 20.04. Also both Chrome and Firefox do the same thing on my Android 10 device.

I'm using the docker image located here if you would like to try and reproduce: https://github.com/jgesc/docker_koel

@acjohnson commented on GitHub (Oct 28, 2020): I am having the same behavior as described and am running Koel version 4.4.0 using Firefox and Chrome on Ubuntu 20.04. Also both Chrome and Firefox do the same thing on my Android 10 device. I'm using the docker image located here if you would like to try and reproduce: https://github.com/jgesc/docker_koel

kerem commented

2026-02-26 02:33:56 +03:00

Author

Owner

@CirnoT commented on GitHub (Nov 10, 2020):

Can confirm this is happening with following configuration:

Koel version [e.g. v4.1.0]: master (e9b850fc33)
OS: [e.g. macOS Mojave] Debian 10
Browser [e.g. Chrome 79] Chromium 86
PHP version [e.g. v7.2.0]: v7.3 from Debian repository
Node version [e.g. v10.15.3]: v14.15.0 (current LTS)

@CirnoT commented on GitHub (Nov 10, 2020): Can confirm this is happening with following configuration: - Koel version [e.g. v4.1.0]: master (e9b850fc3346b204b9b95e1e99d9a8752f3c6530) - OS: [e.g. macOS Mojave] Debian 10 - Browser [e.g. Chrome 79] Chromium 86 - PHP version [e.g. v7.2.0]: v7.3 from Debian repository - Node version [e.g. v10.15.3]: v14.15.0 (current LTS)

kerem commented

2026-02-26 02:33:56 +03:00

Author

Owner

@pattmax00 commented on GitHub (Oct 18, 2022):

I also have this issue

@pattmax00 commented on GitHub (Oct 18, 2022): I also have this issue

kerem commented

2026-02-26 02:33:56 +03:00

Author

Owner

@acjohnson commented on GitHub (Oct 28, 2022):

I can confirm this is now fixed 🎉 amazing @phanan

@acjohnson commented on GitHub (Oct 28, 2022): I can confirm this is now fixed :tada: amazing @phanan

kerem commented

2026-02-26 02:33:56 +03:00

Author

Owner

@fschlaef commented on GitHub (Oct 31, 2022):

Updated today, confirm fixed 👍 Awesome job as always @phanan !

@fschlaef commented on GitHub (Oct 31, 2022): Updated today, confirm fixed 👍 Awesome job as always @phanan !

kerem referenced this issue

2026-02-26 02:34:11 +03:00

[GH-ISSUE #1305] Support Subdirectory Installation #754

kerem referenced this issue

2026-02-26 03:30:34 +03:00

[PR #673] [MERGED] add support for non root installations #1315

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#673

No description provided.

Rows
Columns