Hi everyone,
I'm Wim Taymans and I'm working on a new project called PipeWire you might
have heard about [1]. I have given some general presentations about it during
its various stages of development, some of which are online [2].
PipeWire started as a way to share arbirary multimedia, wich
On Mon, 20 Aug 2018 at 01:41, Robin Gareus wrote:
>
> On 02/19/2018 09:39 AM, Wim Taymans wrote:
> [...]
> > I would very much like to hear your ideas, comments, flames, thoughts on
> > this
> > idea. I think I'm at a stage where I can present this to a bigger audien
On Wed, 7 Jul 2021 at 14:05, Filipe Coelho wrote:
>
> On 07/07/21 12:37, Robin Gareus wrote:
> > On 7/7/21 1:00 PM, Wim Taymans wrote:
> >> This utterly fails with jackd on this system, it doesn't even want
> >> to start all the clients, I'm sure it's something w
On Tue, 6 Jul 2021 at 21:41, Fons Adriaensen wrote:
>
>
> I'll give PW its chance when the developers tell me it's ready for
> real life. Which will mean a session with around 15 jack clients
> with a total of 800 or so ports. Should run without hickups while
> watching a youtube movie and
On Wed, 7 Jul 2021, 22:55 Fons Adriaensen, wrote:
> On Wed, Jul 07, 2021 at 10:44:23PM +0200, Fons Adriaensen wrote:
>
> > With jack2 this takes 0.5s to create the clients, and on average 0.1s to
> > connect all of them in a chain (15 * 32 connect calls).
>
> Correction: after removing some
You need to make sure the cron script can find the local socket to
talk to pipewire.
It searches for the socket named pipewire-0 in:
$PIPEWIRE_RUNTIME_DIR
$XDG_RUNTIME_DIR
$HOME
~/
I'm guessing that the cron script is running with a different user
and/or does not have
the same environment
Hi Fons,
As a bare minimum you would need pipewire (the daemon) and
pipewire-jack (the libjack.so client implementation). With a custom
config file you can make this work exactly like jack (see below).
The way PipeWire normally works is that when starting the daemon,
nothing is in the graph.
On Mon, 17 Jan 2022 at 16:03, Lorenzo Sutton wrote:
>
> My problem with that set-up is that it seemed that something like Ardour
> would need to be explicitly run via pw-jack so e.g.
>
> pw-jack ardour
>
You distro probably also has a package that puts the pipewire
libjack.so in LD_LIBRARY
On Tue, 18 Jan 2022 at 17:15, Will Godfrey wrote:
> >and of course systemd. I do not think it will run without.
It does run fine without systemd.
>
> If it *requires* systemd then that is a non-starter for me :(
>
It doesn't require systemd.
You can compile with systemd support and then you
On Thu, 20 Jan 2022 at 12:16, Fons Adriaensen wrote:
>
> Hello, Wim,
>
> > Sorry, git for now. I just started to implement the last bits to make a
> > session manager optional.
>
> OK, I'll wait until this is available via Arch (don't want to mix up
> two potential problems, build/install and
On Wed, 19 Jan 2022 at 14:04, Fons Adriaensen wrote:
>
> On Tue, Jan 18, 2022 at 07:16:39PM +0100, Wim Taymans wrote:
>
> > As a bare minimum you would need pipewire (the daemon) and
> > pipewire-jack (the libjack.so client implementation). With a custom
> > config
On Fri, 10 Feb 2023 at 23:46, Fons Adriaensen wrote:
>
> On Thu, Feb 09, 2023 at 01:34:52PM +0100, Wim Taymans wrote:
>
> > real JACK is more mature and does things differently (mostly device
> > wakeup with IRQ instead of timers)
>
> The real difference between the t
On Tue, 14 Feb 2023 at 16:32, Fons Adriaensen wrote:
>
> On Tue, Feb 14, 2023 at 03:57:05PM +0100, Wim Taymans wrote:
>
> > > The real difference between the two methods is 'sample count'
> > > versus 'time' as the source of the event that starts a period.
> >
On Wed, 8 Feb 2023 at 12:09, Fons Adriaensen wrote:
>
> Hello all,
>
[snip]
> So the ideal solution
> for me would be the have Pipewire as a Jack client.
> So first question:
>
> Q1. Is that still possible ? If not, why not ?
It is possible although I have not tried this in a while. The way it
14 matches
Mail list logo
