guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#43628] Further Info


From: Prafulla Giri
Subject: [bug#43628] Further Info
Date: Sun, 27 Sep 2020 02:31:50 +0545

Oh, I come from a culture that does not call seniors by their first names. (:
Yes! guix-android looks super awesome! I'm glad that you are working on that. You're awesome.
(Also, I just realized that you've also got guix-home-manager and so many more cool repositories! I need to check those out, and soon!)

I did manage to resolve this issue. Kinda'. Here: https://github.com/peanutbutterandcrackers/guix-packages/blob/master/aegisub.scm

All I had to do was re-define 'alsa-lib' to point to the /gnu/store path of alsa-plugins. The /gnu/store path had to be figured out during runtime.

Could you please check how this fares in a GuixSD system? If it goes well, perhaps I should send a patch in for aegisub. But then again, I wonder if I should make the changes in alsa-lib itself, but I am not very sure about that.

On Sat, Sep 26, 2020 at 8:20 PM Julien Lepiller <julien@lepiller.eu> wrote:
Hehe, thanks for your interest in guix-android. It's not really done yet, but I'm very motivated :). It always feels weird when someone on the internet calls you Mr ^^. No need to be so stiff, you can call me "Julien" (and I suppose it's the norm to call people by their first name in this kind of internet community).

Maybe try to run aegisub with strace -f, you might find out something. You may have to take a look at alsa's sources to find out how it looks for its plugins exactly (maybe try to grep for PLUGIN or PLUGINDIR)?

Le 26 septembre 2020 08:07:34 GMT-04:00, Prafulla Giri <pratheblackdiamond@gmail.com> a écrit :
Okay, I think I'm stuck now. lol



On Sat, Sep 26, 2020 at 3:42 PM Prafulla Giri <pratheblackdiamond@gmail.com> wrote:
Hello Mr. Lepiller,

Thank you for the tip. For the moment, I want to poke around this issue. Perhaps I get absolutely tired of it (or find a good hack - and an ugly patch). I did manage to learn a bit more about union-builds in general. So, that's a silver lining.

Also, your work on guix-android seems so very cool! Please keep up the great work!

On Sat, Sep 26, 2020 at 3:28 PM Julien Lepiller <julien@lepiller.eu> wrote:


Hi Prafulla,

Le 26 septembre 2020 03:31:38 GMT-04:00, Prafulla Giri <pratheblackdiamond@gmail.com> a écrit :
>Another information:
>
>I have other programs on my foreign system (installed via guix) that
>produce sound well, without any issues. They include:
>espeak and kdenlive.
>
>Also, I did try making the union-build use copies instead of symlinks
>using
>(union-build ... #:symlink copy-recursively) but that didn't work out
>either.
>
>Now, I'm going to take a look at fixing the pkg-config rules, and will
>be
>updating this thread should that resolve this issue.
>
>On Sat, Sep 26, 2020 at 12:21 PM Prafulla Giri
><pratheblackdiamond@gmail.com>
>wrote:
>
>> I forgot to mention, but the union-build works. If one `guix build`s
>the
>> union package, and cd into the /gnu/store/...-union-build, one will
>see
>> that things are there as it should be (lib/normal-alsa-*.so and
>> lib/alsa-lib/*pulse*.so).
>>
>> It's just that aegisub seems to be looking from the
>> /gnu/store/normal-alsa-lib-dir instead of
>/gnu/store/union-alsa-package.
>>

I think the issue with the union-build is that it is completely ignored: alsa doesn't look in it's current directory for plugins, but in the directory where it's been configured (at build time) to look for.

On the Guix System, there is a service that creates a /etc/asound.conf, which references alsa-plugins:pulseaudio. Maybe you actually want to configure that? Maybe try to copy this to a new file .asoundrc:

pcm_type.pule {
  lib "/home/foo/.guix-profile/lib/alsa-lib/libasound_module_pcm_pulse.so"
}

ctl_type.pulse {
  lib"/home/foo/.guix-profile/lib/alsa-lib/libasound_module_ctl_pulse.so"
}

pcm.!default {
  type pulse
}

ctl.!default {
  type pulse
}

reply via email to

[Prev in Thread] Current Thread [Next in Thread]