SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
yes, I compiled apulse from source, no surprises there.
no, nothing is displayed on the terminal after "apulse skype".
I have noticed, though, that if I try to directly start skype.4.3 it complains about a missing PulseAudio library from version 5.0 (libpulse.5.0 or something like that, I'm not in front of the terminal right now).
For completeness I'm stating that I'm working on a 32bit 14.0 Slackware, *not* a 64bit one.
@moesasji,
I have noticed, though, that if I try to directly start skype.4.3 it complains about a missing PulseAudio library from version 5.0 (libpulse.5.0 or something like that, I'm not in front of the terminal right now).
Unfortunately I can't help. The only thing I can say is that the above thing you mention is expected behavior. When you run "apulse skype" the apulse command provides the compatibility layer that provides the equivalent of the pulseaudio libraries. So if you run skype directly that layer is obviously missing.
1. It was written for the sole purpose of having sound in Skype-4.3 without having to install PulseAudio.
2. Once the first item was achieved, the development stopped. There won't be any new features, only occasional small bugfixes.
3. The above means that running apulse with anything other than Skype-4.3 is unsupported and most likely won't work. For example, it is reported to not work with Steam and even Skype-4.2.
If interested, I found the above information here (WARNING: Russian website, lots of flame and hate).
I think there was no point in creating an "official" SlackBuild for it. Instead it should be bundled with Skype's SlackBuild as an option (like APULSE=yes). Also there's no point in building 64bit libraries since Skype is 32bit only.
Not sure why you would want PulseAudio, if Steam is the only thing that bother you
It does not. I just don't know any other applications that might want to use PA. Also I remember a comment from G+ about wondering if XCOM could use apulse, so I thought that some Steam games might only use PA for their sound output.
It does not. I just don't know any other applications that might want to use PA. Also I remember a comment from G+ about wondering if XCOM could use apulse, so I thought that some Steam games might only use PA for their sound output.
Cool thanks for that slackbuild. too bad it probably won't get in SBo.
I ditched skype altogether now.
Though i know quite a few people who use it with apulse and its working like a charm.
As for steam doesn't that bundle its own copy of pulseaudio anyway?
To isolate Skype 4.3 from the other files in $HOME, README.SLACKWARE proposes to create specific user and group and use sudo.
Another way is to just create another "real" user with a specific $HOME belonging to the group users, and use "su - $user" to change identity. That works here™. FWIW YMMV and all.
Last edited by Didier Spaier; 10-31-2014 at 07:22 PM.
Hi,
I've compiled apulse on my Slackware64-current without any particular option and then installed the Skype distribution repackaged using the Sbo script.
Skype starts well but I have no sound played no recorded.
In options, for sound, everything is set up to "Virtual device", so my guess is that I need to pass some information to apulse to make it use the proper card.
Indeed, I have a terrible HDA sound card that provide a "digital card" as first and the proper "Analog" card as second device :
Code:
bash-4.3$ aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: Generic [HD-Audio Generic], périphérique 3: ID aa01 Digital [ID aa01 Digital]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
carte 1: Generic_1 [HD-Audio Generic], périphérique 0: ALC887-VD Analog [ALC887-VD Analog]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
bash-4.3$
I managed to make most of my programs work by forcing the default to card 1, but could not find yet the way to do so with apulse.
I tried this :
But no luck yet. If anyone has a solution, I would be grateful.
Is it necessary to use a pulseaudio-like conf file?
EDIT : Well actually, it worked, I just needed to set APULSE_CAPTURE_DEVICE to "hw:2,0" and not stupidly to "1,0".
It actually works pretty well apparently and is really quite easy to set up. Just make sure apulse is compiled in 32bits on a multilib system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.