Stuttering sound in the first 35 second after play

Ask Fedora
, , , , , , , ,
1

after installation of Fedora41,I try rhythmbox, the sound is not good( the sound is on and off,intermittently) in the first about 35s, and after this 35s,the sound is good. I try VLC to play mp3 file, it is the same. would you please tell me how to solve this problem?thanks!

1 Like
2

Added audio, f41, pipewire, pulseaudio, rhythmbox, vlc, workstation

3

Hey there and welcome to Fedora!

Excuse me editing your title, I made it a bit clearer.

Please tell us more about your setup.

  • what hardware?
  • what variant of Fedora do you use? The main one?
  • can you give us the output of lspci | grep Audio ?
  • can you try “g4music” and “Celluloid” from Flatpak/Flathub? If you need help installing those, feel free.

There are multiple ways to use Audio on Linux. Fedora and all other modern Distros use Pipewire, and there simply might be issues with something here.

Using an app that uses pipewire natively, like Celluloid and G4Music, could solve those or give us insights.

Afaik, rhythmbox and and for sure VLC are pretty outdated projects not following current Linux Desktop standards.

4

thank you for your reply.I answer you four questions as follow:

  1. hardware: I use Thinkpak X1 Extreme, install F41 in VMware-workstation, (I also install Ubuntu24.4 in this VMware,but the sound is good.)

  2. I use Fedora41 workstation Main one, [Fedora-Workstation-Live-x86_64-41-1.4.iso],default installation.

  3. lspci | grep Audio:02:01.0 Multimedia audio controller: Ensoniq ES1371/ES1373 / Creative Labs CT2518 (rev 02)

4. I installed G4music and celluloid just now. but the problem is still there, also the same problem as that of VLC and rhythmbox.

1 Like
5

Okay so you dont run Fedora on that machine, but in a virtual machine?

This is a highly important factor. But it didnt happen on Ubuntu.

I would just assume this is something with VMWare.

6

Added virtualization, vmware

7

I have had the exact same experience with Fedora, beginning with F40, in VMs ran under VMWare Fusion. So I would isolate this issue as being specific to VMWare.

I have solved my issue by switching to another hypervisor.