Bug Report: Levels doesn't work when changing Audio Output Device

[Repertix]

Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue.

If you are playing the game in a browser, what site are you playing it from?

• Newgrounds
• Itch.io? Specify below
• • Windows
• • Mac
• • Linux

If you are playing the game in a browser, what browser are you using?

• Google Chrome (or chomium based like Brave, vivaldi, MS Edge)
• Firefox
• Safari

What version of the game are you using? Look in the bottom left corner of the main menu. (ex: 0.2.7, 0.2.1, shit like that)

0.3.2

Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.

• In-game, disconnect Headphones, Earbuds, etc., in other words, change the audio output device you were playing the game with, the game is muted from now on.

• Pause and restart the level.

• Now when the level starts, the first note "chunk" will appear but in certain a height it would stop moving.

• Reset the level as many times you want, it won't change nothing.

• You can check on any other levels and the notes would freeze too.

Please describe your issue. Provide extensive detail and images if possible.

So, I was playing Week 6 when my earbuds ran out of battery so I quickly paused the game, and changed the earbuds for another pair I have, when I connected back, I noticed the game was muted so I restarted the level, after restarting, the first notes appeared but stopped moving upwards, if you try to restart the level this won't work as the notes will behave just like in the first time.

After checking a bit further, when entering other levels, the level starts fine but in the moment the Enemy or Boyfriend hits the first note, the notes stop moving again and level freezes.

My Epic Evidence:

OBS.Video.05-05-2024.mp4

If you're game is FROZEN and you're playing a web version, press F12 to open up browser dev window, and go to console, and copy-paste whatever red error you're getting

[EliteMasterEric]

I believe this is an issue with the Lime library, where it does not include functionality to detect a change in audio device and reinitialize the playback module. As a result, all audio stops.

As a side effect, the Conductor does not change its position since it relies on the current timestamp of the audio (which isn't currently playing!) and therefore the notes (which rely on the Conductor position) don't move!

We will look into fixing it but it's not easy.

[AbnormalPoof]

Does this still occur in v0.5.1?

[NotHyper-474]

Does this still occur in v0.5.1?

Yes

[ACrazyTown]

This could be resolved with a pull request I have made on Lime's repository (#selfpromo 😅) which adds the ability to change the audio output device manually, automatically change the audio output device if it's disconnected or something and also does not pause audio sources when the audio output device disconnects

openfl/lime#1841

It's not fully complete but I think it's in a mostly useable state