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

Make buffer underrun counter visible in the main Window #10706

Closed
mixxxbot opened this issue Aug 23, 2022 · 6 comments
Closed

Make buffer underrun counter visible in the main Window #10706

mixxxbot opened this issue Aug 23, 2022 · 6 comments
Labels
feature incomplete stale Stale issues that haven't been updated for a long time.

Comments

@mixxxbot
Copy link
Collaborator

Reported by: 0x520
Date: 2022-04-10T16:03:31Z
Status: New
Importance: Undecided
Launchpad Issue: lp1968486


I would love if there was an option to see the Buffer underrun counter in the main window, if you play for example on an internet Radio, the buffer underrun might not be audible on the speakers attached to your laptop, however skipping might occur on the stream. That way you at least would have achance of noticing.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2022-04-10T21:21:24Z


There is already the CPU meter. The read area means underrun.

What would be the use case to have the counter always visible? You cannot do anything to lint old under-runs.

Do you know why you have under runs in the first place?

@mixxxbot
Copy link
Collaborator Author

Commented by: 0x520
Date: 2022-04-12T17:21:19Z


To be honest, i wasnt even aware of that tiny CPU Meter, i had an occassion where i played on an online radio station and only when i relistened to the recording realised that i had a ton of underruns, because on my speakers i had zero skipping, however it skipped on the stream, i assume because of the extra overhead for the compression. I would have been able to simply reconnect with greater Latency for example in order to at least partly play without skipping.
Thanks for the hint though, maybe it would be sufficent to make the "CPU Meter" more Promiment when it turns red.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2022-04-12T20:51:26Z


It sounds as if you suffer another type of underruns than displayed in the CPU meter.
The CPU meter underruns will be in place in all destinations. So that is probably not your issue.

There is another type of underrun, that happens when due to the different Clocks for soundcard and streaming. By default the Stream is send with the master soundcard clock, it requires compensation samples to match the listener soundcard clock. You may try to switch to the Network clock. Maybe it helps.

Or you had network issues? In case of a network buffer overflow Mixxx will try to reconnect. which is visible by a yellow on air connection widget.
You will see it also in the mixxx.log

@mixxxbot
Copy link
Collaborator Author

Commented by: 0x520
Date: 2022-04-12T21:59:28Z


I doubt that i had network issues since i got 10g fiber to the router and 1g copper from there. I usually have roughly 930mbits upload. I reckon though, that the underrun counter had some underruns noted, maybe i am too aggressive on the buffer, i had it to 5ms. Ill definetly check for the soundcard clocks though, thanks for the advice.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@daschuer
Copy link
Member

Is this still an issue?

@github-actions github-actions bot added the stale Stale issues that haven't been updated for a long time. label Feb 20, 2023
@github-actions
Copy link

Expired for Mixxx because there has been no activity for 60 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature incomplete stale Stale issues that haven't been updated for a long time.
Projects
None yet
Development

No branches or pull requests

2 participants