shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

281
active users

#pipewire

0 posts0 participants0 posts today

Hey #LinuxAudio geeks, anyone succeeded using multiple #proAudio cards with #pipewire? I have a RME HDSPe MADI (with a massive 32 in rack) and a RME HDSPe RayDAT (with a modest 8x8 in/out rack). In pipewire, I only see the MADI card. I have 0 DA converter on MADI so it's basically useless: I have *zero* working outputs with Pipewire.

I can run jackd over pipewire and it works, but gets unreliable: the bridge from jack to pw regularly drops under load, requiring a restart of jackd.

Ideas?

Continued thread

I'm now set. I have the Toughpad sitting in its dock, USB television dongle plugged in… ABC News 24 running.

For sound, I ran:
`pactl load-module module-native-protocol-tcp port=<port> listen=<desktop_ip>`
on my desktop connected to the stereo, and:
`pactl load-module module-tunnel-sink server=tcp:<desktop_ip>:<port>` on the Toughpad.

I was then able to direct the sound from Kaffeine to the new audio sink that appeared. Latency and lip-sync is pretty good.

I'll have to keep this trick in mind for when I'm wanting to watch movies with decent sound.

I've got a network speaker (a Denon Home 150) that speaks "AirPlay Remote", "AirTunes Remote", "Tidal Connect", "Spotify Connect", "HEOS Audio", and "Qobuz Connect" according to Avahi.

How can I play music on this from Linux?

My music player (Strawberry) doesn't list it or any of those protocols, and I can't set it as an audio device (which is probably a good thing).

#linux#arch#airplay

#Linux audio is bizarrely confusing to a regular user lol - if I were to configure a #PulseAudio setting (i.e. clock.force-quantum) but obviously most systems now have moved to using #PipeWire, but from what I can tell or think to understand is that systems use PipeWire via something called #WirePlumber, should this (user-specific) configuration be done in a WirePlumber config, or PipeWire? I normally could learn these things easily through the #ArchWiki, but so far, this topic is completely lost on me lol.

I'm not sure how many people on here run archlinux, but recently, a contribution I made to speech dispatcher, namely the pipewire module I talked about a while ago on here, got in the arch package.

Before wooping with joy and other similar feelings because something I made, with the help of the maintainer of course, got into a mainline distribution people actually use, not just in my computer, it'd be really nice if I could know whether it made any tangible difference.

So then, here are afew of the things I hoped to come true with the introduction of a pipewire native audio module:

* less battery usage by speech dispatcher
* the ability to be able to speak normally, even in high stress environments, such as low-memory and so on
* lower cpu consumption
* lower latency when speaking and being interrupted often, the case of screenreaders fits perfectly here

Now, I'm absolutely no statistician, and I don't know how to even begin to measure any of this. So, here is me asking help from the wider fediverse.

For the people who know how any of this part works, can you take afew measurements of the performance of speechd, both with and without the pipewire support enabled? I'm primarily interested in the situations I mentioned before, especially the latency, does well under load and consumes less resources aspect.

For anyone who sees this, can I please have a boost? :p it would be incredibly helpful for me to know if this improved anything, even if one bit, and if it was worth going on and on about latency improvements regarding pipewire. I tried to do local tests with sound first, the results were positive, and so was my experience with using speech dispatcher with this module enabled. It could be because of my older computer, but I definitely feel a difference, although not a huge one. If there are other bottlenecks, I'm not sure they're in audio anymore, unless my code is flawed, which could definitely be and a deeper review on that by someone who knows audio stuff better than me should probably be done at some point, but I'm trying to get an inkling into the benefits this had, if any.
#linux #pipewire #archlinux #statistics

PipeWire 1.4 Is Out with RISC-V Support, MIDI2 Support, JACK Control API, and More

Highlights of PipeWire 1.4 include support for the RISC-V CPU architecture, a PipeWire JACK control API, DSD playback for the ALSA plugin, a system service for pipewire-pulse, Bluetooth support for BAP broadcast links, support for hearing aids using ASHA, a new G722 codec, and UMP (aka MIDI2) support.

9to5linux.com/pipewire-1-4-is-…
#Musicproduction #Pipewire #Midi2 #RiscV

Easy Effects очень неплох, это который эквалайзер, но скорее больше: «Audio Effects for PipeWire Applications».
Можно рекомендовать тем, кто задумался о приобретении внешней звуковухи ради более яркого звучания музыки. Позволит поиграться и со встроенной, понять, надо ли что-то другое или пары крутилок хватит в этом.

Полезно и для тех, у кого микрофон шумами изобилует или хочется подправить звук идущий с него в какую-нибудь VoIP или же ВКС.
От звонких согласных полностью не спасёт ни это средство, ни другие. От речи нетренированного обывателя даже «экраны» плохо помогают (работать над произношением всё равно придётся).

#audio #music #linux #easyeffects #pipewire @Russia
hub.hubzilla.deHubzilla.de

So here's the thing: I'd really love to use #Ardour for my next album, cause I don't want to continue working with something from a company sucking up to America's regime

Only problem is: I can't

I'm using 3 different audio interfaces via #pipewire 1.2.4, and Ardour keeps on forgetting USB audio and MIDI connections over restarts (or suspends), forcing me to make each connection again, which sucks.

First person to solve this for me gets a present and a special credit in the liner notes.
(1/2)