Sounds not coming trough on a Linux Pipewire system

[Parakovsky]

Think it might be related that pulseaudio got proxied by Pipewire or something. Can't see the audio output both in pavucontrol and the browser window.

[nnirror]

@Parakovsky A few questions / things to check:

1. Have you "enabled browser sound" by clicking the speaker icon in the lower-left of the browser window? It should be toggle on so it has the three lines coming off it.
2. If you do that and it still doesn't work, what browser are you using and what Linux OS?

[Parakovsky]

Yes, sorry.... latest Archlinux. Tried Chromium as well as Firefox... sound just don't come trough altough ama hobbyist so probably me evaluating it wrongly or somethnig. There is no indication of coming sound from anywhere in the system..... tried muting/unmuting and deity knows what else... Michael Cella ***@***.***> writes:

…

@Parakovsky A few questions / things to check: 1 Have you "enabled browser sound" by clicking the speaker icon in the lower-left of the browser window? It should be toggle on so it has the three lines coming off it. 2 If you do that and it still doesn't work, what browser are you using and what Linux OS? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

-- Aleksas Tunikas http://www.schopenhauer.fm

[Parakovsky]

Installed pipewire-jack or whatever it called, and trying SC to test out audio. It doesn't work from scratch but after that pipewire-jack thing it seems to be. Dunno if that helps, just trying to report on advances. Maybe my thing is still misconfigured somehow.

[nnirror]

Okay. Have you followed the steps in the "Installation and getting started" section?

It is necessary to complete each of those, in the order they are listed, so that Facet will run properly. So, you need to install nodejs, npm, and sox.

https://github.com/nnirror/facet?tab=readme-ov-file#installation-and-getting-started

First, I would walk through each step again and confirm that you have completed it.

Then, when you run "npm run facet", and you navigate to localhost:1124, does the text editor open correctly? Is there a green circle in the bottom-left to indicate that the servers in the background are running? At the very bottom fo the screen, there should be a indicator of the transport's position in the loop which continually moves from left to right. Is that working?

If the text editors and servers seem to be running properly, then after you run a command such as $('example').sine(100).times(_.sine(100)).play();, you should see a .wav file appear in the facet/tmp directory. Does that happen? If so, can you play that wav file somehow?

Just a few thoughts to help you debug. I hope this is helpful.. please feel free to ask more questions if you're still not able to get it running.

[Parakovsky]

Hello, yes and sorry to be the pain in the ass guy, but maybe problem related somehow to a system wide situation, so it might be useful for people in the future so basically Sox and NPM is installed system wide, cloned the repo and installed it and run trough npm, and the error displayed in a terminal, I dunno wether I forgot to check last time or it was not there is sound like this

***@***.*** facet node js/process_manager.js

error starting transport server: AggregateError error posting to transport server: AggregateError This only happens when I run it for a playback not in the load itself. Here is a short screencast for you: https://disk.yandex.com/i/E1RfALvP59VGIg, sorry i was switching windows to try to make it fullscreen and accidentally jumped to some random shit there, nevermind that! Anyway hope you have a wonderful day and we will eventually solve it somehow!

[nnirror]

Thanks for sending that video.

Could you go to the root of the facet repository and run node js/transport.js from a terminal?

If there aren't any errors when you run that command, this issue might be due to firewall settings on your computer. Facet uses several HTTP servers on your local machine, each running on a different port, and they need to be able to communicate with each other.

Also, what version of NodeJS are you using? you can check by running node -v.

[Parakovsky]

Hi Michael, not aware of any firewall on my system but I got few other things running that might ruin the Facet occupying same ports or somethnig..... Here's the output you asked, segmentation fault is kinda worrying. Have a blessed day! ~/facet $ node js/transport.js segmentation fault ~/facet $ node -v v21.6.2