Re: [LAD] jackdbus log controls?

While your correct that changing my approach to make use of pre-
allocated players that are re-load-able would work
for fixing the verbose log problem, it is a rather large design
philosophy change to make this late in the design. The
OS X version I am porting from had the media handling "builtin" using a
similar, pre-allocated object approach. My
new design is a departure form the original approach since I wanted to
make the most use of jack's inter-application
flexibility. Since I am at the testing stage at this point, a lot
of re-coding would be needed to go back to the old,
pre-allocated player approach. And I am kind of attached to leaving my
core mixer inputs open/disconnected when
not used my the automation algorithm, so they can be connected
to sources by the user if they want. For now, I'll
rotate log files.

Thanks,
Ethan...

On Sat, 2019-11-30 at 13:19 +0100, Fons Adriaensen wrote:
> On Sun, Nov 24, 2019 at 03:51:04PM -0700, Ethan Funk wrote:
> i
> > My application is endlessly forking new audio player processes that
> > connect back to a core mixer via jack, play when needed, then
> > disconnect when finished. So the above log file is crammed full of
> > jack port connect and disconnect notices. How do I make it stop?
>
> Not really answering you questions, but avoiding the problem
> that triggers it: just use a fixed set of players and control
> them (load, stop, start, locate,...) instead of creating a new
> player for each file...
>
> Ciao,
>

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev