Fast playback and garbled audio persists (Ubuntu 13.10)

Hi,

Which distribution are you using? I assume you're using Ubuntu, if this is not the case, the paths of some tools could be a bit different.

For most people just running "pulseaudio -k" solves the problem, in some other cases winetricks in combination with winecfg was successful (see this FAQ: https://answers.launchpad.net/pipelight/+faq/2444).

* Concerning winetricks: How did you run it exactly? Its really necessary to run it for example with (all in one line):

WINEPREFIX=~/.wine-pipelight WINE=/opt/wine-compholio/bin/wine WINEARCH=win32 ~/.wine-pipelight/winetricks

otherwise it will just modify the settings of your default wine prefix ~/.wine

* To run winecfg we recommend the following command (all in one line):

WINEPREFIX=~/.wine-pipelight WINEARCH=win32 /opt/wine-compholio/bin/winecfg

If you haven't used exactly these command lines, can you please repeat the step to select "sound=alsa" via winetricks and also test if the "Play Sound" button in winecfg works as expected? You also should have a list of multiple output devices in winecfg, try to select a different one. When everything works as expected in winecfg, it should also work with the Silverlight application in most cases.

If this doesn't help please try to create a pipelight log with the following method:
* close all browser windows first
* start your browser from a terminal with:
firefox &> ~/pipelight.log
(or any other browser, like google-chrome, chromium-browser, ...)
* upload the file pipelight.log from your home directory, either here on launchpad or on some other page like http://pastebin.com and write the link here

Sebastian

I am using Ubuntu 13.10

I ran winetricks using:

WINEPREFIX=~/.wine-pipelight WINE=/opt/wine-compholio/bin/wine WINEARCH=win32 ~/.wine-pipelight/winetricks

That opens a window with "Select the default wineprefix" already selected. I clicked 'OK'.
From there, I selected "Change settings" and clicked 'OK'.
This brings up a long list of settings. I selected 'sound = alsa' and clicked 'OK'.
This causes my terminal to display:

Executing w_do_call sound=alsa
Executing load_sound alsa
Setting sound driver to alsa
Executing winetricks_early_wine regedit C:\windows\Temp\_sound=alsa\set-sound.reg

However, if I repeat this process, I find that the setting "sound=alsa" is unchecked, even though I just went through the process of turning it on.

After that, I ran:

WINEPREFIX=~/.wine-pipelight WINEARCH=win32 /opt/wine-compholio/bin/winecfg

My terminal gave the message:

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory

but a Wine configuration window appeared nonetheless. In the Audio tab, the selected driver is winealsa.drv.
The first time I click the "Test Sound" button, the terminal displays:

err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded

but this message only shows once; a new one does not appear every time I click "Test Sound".
When Output Device is set to either "(System default)" or "Out: default", clicking the "Test Sound" button will make a sound, but both have the same problem when using Netflix. The other options produce no sound.

Thank you very much for your assistance. I'm trying to learn how to use Linux because I like open source software, but it does seem much more complicated than Windows, at least to a new user.

Hi,

from what you wrote above it sounds like you did everything correctly.

>However, if I repeat this process, I find that the setting "sound=alsa" is unchecked, even though I just went through the process of turning it on.

Thats okay, this option is just saved, but you cannot see the current state (at least not in winetricks).
Also the other terminal messages are nothing unusual and don't mean that there is really an error.

Can you try to run your browser with (close all other browser windows first):

PULSE_LATENCY_MSEC=30 firefox

and check if the problem occurs then, too?

Sebastian

Sebastian, I know the submitter didn't respond but the PULSE_LATENCY_MSEC argument fixed the exact same problem that I was having with it. Thanks a bunch, never would have figured that out otherwise.