Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build 15: Bit Depth Switching causing unnecessary stuttering #97

Open
MasterRahool opened this issue Jun 11, 2023 · 2 comments
Open

Build 15: Bit Depth Switching causing unnecessary stuttering #97

MasterRahool opened this issue Jun 11, 2023 · 2 comments

Comments

@MasterRahool
Copy link
Contributor

beta 10/build 15, connected to DAC via USB

Okay so here's my experience with the latest:

With Bit Depth Switching on:

  • It "works", it does switch the bit depth
  • when selecting a track with a different depth, my audio had to pause 3 times before the track started playing
  • when selection the 2nd track on the same album (no switching involved!) it stuttered twice before playing, selecting the third track it stuttered like 3-4 times.

In its current state, I can't consider this functioning as intended
(I dont use this feature, just, assuming I really needed to have the right depth)

With Depth off:

  • With depth off, things play fine on the same album
  • no lag when switching between albums with the same bit rate & different depths
  • only lag is when bitrate switching, the track starts and a split second later my dac has to adjust to the new bit rate, this isn't a consistent issue, sometimes it plays with no audio sneaking out the beginning
  • i did find that going between, ie, from 88 to 96, sometimes it would go 88-48-96, but this wasn't consistent
@MasterRahool
Copy link
Contributor Author

MasterRahool commented Jun 11, 2023

Found another issue while listening today.

  • Listening to a 44.1k track, opened up a playlist on shuffle, the track is 44.1 but LSS changed it to 48k (which was the next song queued up)
  • I went forward, then back again to get it to change to 44.1k
  • A significant number of seconds later (10? as in, it wasnt in the initial couple when it usually changes), it forced itself back to 48k

@bonifaido
Copy link
Contributor

Submitted a fix for this in #106

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants