Bug 1953429 - 192 KHz sample rate gone after Fedora 34 'upgrade'
Summary: 192 KHz sample rate gone after Fedora 34 'upgrade'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-26 06:05 UTC by udo
Modified: 2022-06-08 01:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 01:09:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description udo 2021-04-26 06:05:00 UTC
Description of problem:
We 'upgraded' to fedora 34.
After seeing the old-style menu at the bottom of the screen (*) we noticed the audio playback was not flawless.
We found out about pipewire running the show.
We looked at teh config but that is also no step forward.
How to set stuff for 192 Khz audio?
The settings from pulseaudio were not migrated.

How to optimize buffers to the playback is with no stutters?


Version-Release number of selected component (if applicable):
pipewire-0.3.26-1.fc34.x86_64

How reproducible:
Upgrade to fedora 34 from previous fedora 33 w/ 192 Khz audio playback


Actual results:
- lower samplerate
- hiccups in audio playback

Expected results:
- flawless audio


Additional info:

Comment 1 udo 2021-04-26 06:05:58 UTC
(*) yes, if the menu is so important that it had to go to the left and now to the bottom of the screen, when why is this not configurable?

Comment 2 udo 2021-04-26 06:18:04 UTC
We set:
default.clock.rate        = 1920000
link.max-buffers          = 64

Result:

Stuff sounds like a badly tracking DAT-tape.


Before I ask:
Why couldn't we wate until 'the product' is a bit more mature?
Has some self-tuning?
Has less issues?

I ask:
How to fix?

Comment 3 udo 2021-04-26 16:15:26 UTC
in pipewire.conf we set:
default.clock.rate        = 48000 (default)
link.max-buffers                      = 64

in alsa-monitor.conf we set:
audio.rate             = 192000

Then stuff starts to sound like it was.

Comment 4 udo 2021-04-27 15:10:43 UTC
default.clock.rate in pipewire.conf needs to be 192000.
All audio.rate needs to be 192000 too.
All node.latency nees to be 1024/192000.

Then 192000 starts to work, also for lower samplerates.

Comment 5 Ben Cotton 2022-05-12 16:44:32 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-06-08 01:09:01 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.