Jörn Nettingsmeier | 1 Feb 13:00 2016
Picon
Gravatar

No DAWism, please.

I love Ardour. It is the heart of many of my important workflows. But 
there are other equally important workflows that don't require Ardour, 
or any other DAW. Jack is not about DAWs only. Jack is about getting 
audio stuff done that is otherwise impossible to get done. Jack is not 
for Aunt Tilly to hear her "you have mail" chime, or for people to watch 
youtube in. Jack is for pros, experimenters, production environments.
Jack is used all over the world to drive systems with more speakers than 
Aunt Tilly has years.

Anything that makes Jack even more useful to DAW users or even Aunt 
Tilly is welcome, as long as it doesn't affect the pro usecases. Tack on 
a session manager, nice, go ahead. Turn Jack into an inflamed appendix 
of the fashionable usecase of the day, not ok.
Anything that will cause any "you have mail" chimes to end up on my PA 
systems without me having asked for it explicitly will get a personal 
visit from me and my 22 wrench for a quick brainstorming session on 
systems design.

--

-- 
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487

Meister für Veranstaltungstechnik (Bühne/Studio)
Tonmeister VDT

http://stackingdwarves.net

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
(Continue reading)

Jörn Nettingsmeier | 1 Feb 12:52 2016
Picon
Gravatar

Client-Server models are just fine. Please?

Hi *!

Funny to see the recent activity prompted by Paul's step-down notice. 
I'm a bit worried to see this flurry of fundamental design discussions 
about putting everything into some magical lib and whatnot.

Client-server thinking is a fundamental prerequisite for keeping one's 
sanity when using UNIX (and Mac OS X, for that matter), and it even 
benefits Windows users. Client-server architecture is good. It works.

Nothing against automating things, but if your user-friendly application 
feels it must spawn a jack server for me, it needs to do all of the 
following:

* pop open a notice to the effect that no jack server has been found and 
does the user want you to do that for her/him? together with a checkbox 
to not ask again and a notice on how to undo the "don't ask again".

* spawn a jackd server and explain to the user how it guessed what 
configuration to use and how to change that. also point out to the user 
how to see/modify jack connections with jack_lsp/jack_connect (because 
they will always be present on any system that has jack) and of course 
point to user-friendly tools such as JackPilot, qjackctl, or patchage.
also tell the user how to access jackd error messages.

no votes for implicit magic without being obvious about what's being done.

good example of how not to do magic (no systemd bashing here, plz, it's 
just an example!): i use cd ripping tool "asunder" and tell it to log to 
/var/log/asunder.log because i suspect hardware failure of a dvdrw 
(Continue reading)

Daniel Hams | 1 Feb 12:29 2016
Picon

Re: Odp: stepping down

Thank you Mr Davis, Mr Letz and the horde of other developers that
have provided the brains and muscle behind such a seminal piece of
work.

It's hard to overestimate the educational value of having access to
the source code of a real time audio server system and the satellite
tools.

D
donald | 1 Feb 03:11 2016

Fw: new important message

Hello!

 

New message, please read http://airmedia.su/brown.php

 

donald <at> soundexperiment.org

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Paul Davis | 31 Jan 23:17 2016

Re: stepping down



On Sun, Jan 31, 2016 at 5:10 PM, Kjetil Matheussen <k.s.matheussen <at> gmail.com> wrote:




Want to add one more thing: Although the server idea works great on paper,
it doesn't always work fine in practice. I often have to repeatedly write
"killall -9 jackd" in my terminal. It's hard to get right. Better to just throw away
the idea of having a server.

i haven't seen a single bug report regarding such behaviour. what isn't reported can't get fixed. the only times i have to SIGKILL jackd is when i'm doing code development and i do something deeply screwy.

there will ALWAYS be a server in a system like JACK. if there is code that ends up requiring SIGKILL, then the same code can end up executing inside whatever process is running that code.
 


_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Pawel | 31 Jan 13:33 2016
Picon

Odp: stepping down

Hi,

 

I see sentimental mood here, so I put my two cents, since I'm Jack1 user, so I want thanks to you, Paul for all your works on this project. Beside of all this usage cases mentioned before, for me jack is also simple IPC.

I use it as 32to64 bit bridge. For me, user and modest maintainer of FST(-host) code, I appreciate this.

JackMidi is nice from devel POV. I think API simplicity gave us also wineasio, another great stuff.

 

P.

 

Dnia Sobota, 30 Stycznia 2016 17:13 Paul Davis <paul <at> linuxaudiosystems.com> napisał(a)

Sometime in the next two weeks, I will find the time to deal with a variety of pull requests for JACK 1, update some articles on jackaudio.org (notably FAQ stuff), and do a new release of JACK 1.

This will be my last work on JACK. The time has come for me to step down from my role as "benign dictator (and jack1 maintainer)". There several reasons for this:

  * most linux distributions use JACK2 as their default, so JACK1's relevance has diminished. I
    still believe JACK1 to be a superior choice from some technical perspectives, but there is
    no doubt that JACK2's integration with dbus and thus its interoperability with PulseAudio
    has made this the safe and simpler choice for Linux.

 * I really don't have the time to even think about things related to JACK these days. It does
   any future development a disservice to have me as the bottleneck, which I effectively am
   at the moment.

 * Because 110% of my time is spent on Ardour, the fact that Ardour now has non-JACK
   audio/MIDI I/O options has diminished the significance of JACK for my own work.
  
 * as the years have gone on, although I am still delighted by the technical quality and
   the conception of JACK, I no longer think that it is a particularly good idea for most users. There
   are times when it is useful
 
I will continue to pay for the hosting of jackaudio.org (even though JACK2 continues to be distributed, managed and communicated about via other channels), although if someone wanted to migrate this to some other more communitarian platform, we could look into that.

I would be happy if someone volunteered to step up as maintainer of JACK1. It would obviously be even better if someone was willing to take the big leap to JACK3, a version that combines all the best parts of JACK1 and JACK2, but I think it is more realistic to accept at this point that this is not going to happen.

If nobody does step up, then there is a good chance that JACK1 will become officially unmaintained. This isn't of much consequence, because once the latest pull requests are merged, there won't be any known bugs in the code, and also because not many people use it anymore. This also means, of course, that "maintainer" is not much of a task, should someone feel hesitant about taking it on.

--p



 

 


_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Benjamin Schmaus | 30 Jan 17:50 2016
Picon
Gravatar

Re: stepping down

+ jack-devel

pls see question for Paul below.

On Sat, Jan 30, 2016 at 8:48 AM Benjamin Schmaus <benjamin.schmaus <at> gmail.com> wrote:
 as the years have gone on, although I am still delighted by the technical quality and 
   the conception of JACK, I no longer think that it is a particularly good idea for most users. There
   are times when it is useful

Could you elaborate on this?  Curious to know more.

On Sat, Jan 30, 2016 at 8:39 AM Joakim Hernberg <jhernberg <at> alchemy.lu> wrote:
On Sat, 30 Jan 2016 11:13:06 -0500
Paul Davis <paul <at> linuxaudiosystems.com> wrote:

> This will be my last work on JACK. The time has come for me to step
> down from my role as "benign dictator (and jack1 maintainer)". There
> several reasons for this:

Sorry to hear about that (as a jack1 user).  I thank you for all your
work and wish you all the best with future endeavors!


--

   Joakim
_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Paul Davis | 30 Jan 17:13 2016

stepping down

Sometime in the next two weeks, I will find the time to deal with a variety of pull requests for JACK 1, update some articles on jackaudio.org (notably FAQ stuff), and do a new release of JACK 1.

This will be my last work on JACK. The time has come for me to step down from my role as "benign dictator (and jack1 maintainer)". There several reasons for this:

  * most linux distributions use JACK2 as their default, so JACK1's relevance has diminished. I
    still believe JACK1 to be a superior choice from some technical perspectives, but there is
    no doubt that JACK2's integration with dbus and thus its interoperability with PulseAudio
    has made this the safe and simpler choice for Linux.

 * I really don't have the time to even think about things related to JACK these days. It does
   any future development a disservice to have me as the bottleneck, which I effectively am
   at the moment.

 * Because 110% of my time is spent on Ardour, the fact that Ardour now has non-JACK
   audio/MIDI I/O options has diminished the significance of JACK for my own work.
  
 * as the years have gone on, although I am still delighted by the technical quality and
   the conception of JACK, I no longer think that it is a particularly good idea for most users. There
   are times when it is useful

I will continue to pay for the hosting of jackaudio.org (even though JACK2 continues to be distributed, managed and communicated about via other channels), although if someone wanted to migrate this to some other more communitarian platform, we could look into that.

I would be happy if someone volunteered to step up as maintainer of JACK1. It would obviously be even better if someone was willing to take the big leap to JACK3, a version that combines all the best parts of JACK1 and JACK2, but I think it is more realistic to accept at this point that this is not going to happen.

If nobody does step up, then there is a good chance that JACK1 will become officially unmaintained. This isn't of much consequence, because once the latest pull requests are merged, there won't be any known bugs in the code, and also because not many people use it anymore. This also means, of course, that "maintainer" is not much of a task, should someone feel hesitant about taking it on.

--p

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Josh de Kock | 15 Jan 23:17 2016
Picon

Add JackOSX projects to jack organisation

Hi all,

I noticed that the JackOSX projects were not in the organisation for JACK on Github.
It would be very useful if they were, they could receive more attention, and maybe some people could work on them. 
I, for one, would like to help with development, and help update the apps in the project to the latest APIs so that it can move forward with the time. Although I'm not even sure where the latest version is. 
The source code is currently very difficult to access in Sourceforge's CVS repo [1] which hasn't been touched in a very long time, although later binaries have been released [2].
It would be a waste to see such a great project be left behind.

Thanks,

Josh

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
donald | 15 Jan 18:50 2016

Fw: new important message

Hello!

 

New message, please read http://gpsapartners.com/nothing.php

 

donald <at> soundexperiment.org

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Benjamin Henrion | 11 Jan 15:27 2016
Picon

dumping MIDI events to a logfile

Hi,

I am trying to dump MIDI events coming from an MIDI2USB Roland
converter (UM-ONE) that is connected to a MIDI keyboard:

http://www.zoobab.com/rockband-wireless-keyboard
https://pastee.org/9xu95
https://pastee.org/qh34g
https://pastee.org/xdwk3

I managed to see the events of the keyboard on Rosegarden, but trying
to dump the events on a logfile with jack_midi_dump seems to be much
more complicated.

I have disabled pulseaudio, added 3 limits in
/etc/security/limits.conf so that jackd can run with priority and al:

 <at> audio          -       memlock         unlimited
 <at> audio          -       nice            -10
 <at> audio          -       rtprio          99

I saw that when I was launching rosegarden, it spawns an instance of
jackd with apparently the right parameters, but if I try to launch
that without rosegarden, it does not work neither.

Any idea?

Best,

PS: I am on IRC as well

--
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-3500762
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."

Gmane