JackAudio October 2019

jackaudio@lists.linuxaudio.org

3 participants
5 discussions

[Jack-Devel] Jack-devel mailing list is shutting down

by Filipe Coelho

Hello everyone, I bring some sad news. While moving jackaudio.org to be under my control (I have been speaking with Paul Davis lately about it), everything was apparently going smooth until we realized we completely forgot about the mailing list. If someone really wants to keep it going, and is willing to take over that side of things, please contact me directly. At this point it will have to be a new setup though. Me and a few others in #lad IRC channel have been talking about creating an online space for communication. I have been experimenting with RocketChat myself, and it is working well. In any case, it is very likely that at some point later this year we will have some new way of bringing community together. Anything that happens will be posted under https://jackaudio.org/news/ Thank you, and I am sorry, at the same time.

5 years, 2 months

[Jack-Devel] JACK2 v1.9.13 release

by Filipe Coelho

A new version of JACK2 has just been released. You can grab the latest release source code at https://github.com/jackaudio/jack2/releases. The official changelog is: - Meta-data API implementation. (and a few tools updated with support for it) - Correct GPL licence to LGPL for files needed to build libjack. - Remove FreeBoB backend (superseded by FFADO). - define JACK_LIB_EXPORT, useful for internal clients. - Mark jack_midi_reset_buffer as deprecated. - Add example systemd unit file - Signal to systemd when jackd is ready. - Set "seq" alsa midi driver to maximum resolution possible. - Fix loading internal clients from another internal client. - Code cleanup and various fixes. (too many to mention here, see git log for details) This release is focused on meta-data support, and this is why it took so long. There might be odd cases here and there and a few bugs, as it is often the case for all software... So please make sure to report back any issues! Special thanks goes to Rui Nuno Capela for the initial pull-request regarding meta-data. There was some work needed afterwards, but that was the biggest hurdle and motivation needed for a new release. :) There are still no updated macOS or Windows builds, those will be handled at a later date. Current plan is to have JACK1 feature-parity first (only a2jmidid and zita internal clients missing now), and afterwards merging examples/tools and header files to be shared between JACK1 and JACK2. The situation regarding development of JACK and JACK1 considered legacy has not changed since last release 2 years ago. See https://jackaudio.org/news/#jack2-v1912-release-and-future-plans for more information. PS: I am in the progress of moving jackaudio.org domain, there might be some disruption.

5 years, 2 months

Re: [Jack-Devel] synchronization with Jack transport

by Christopher Arndt

(Re-directing the discussion to the mailing list again.) Am 03.10.19 um 15:03 schrieb Philippe GARCIA-ORTUNO: > Yesterday I made a test to connect seq24 (in seq24 send the clock to > midi Throught and then connect midi Trought to Ardour MMC, > Ardour+seq24+Tempest played well at 120). So is Ardour normally involved in your setup? Can you describe exactly, which (audio) software you are running and what is connected where and to what (audio and midi, ALSA, JACK and hardware MIDI connections)? Try to create a minimal setup, which still exhibits the problem. Chris

5 years, 2 months

[Jack-Devel] Fwd: Re: synchronization with Jack transport : jack-audio-tools-master problem

by Philippe GARCIA-ORTUNO

I still continue to have some error with python3: /chapolin@chapolin-MS-7B89:~/jack-audio-tools-master$ python3 transport/timebase_master.py Traceback (most recent call last): File "transport/timebase_master.py", line 11, in <module> import jack ModuleNotFoundError: No module named 'jack' /and/ chapolin@chapolin-MS-7B89:~/jack-audio-tools-master$ python3 setup.py cmd --help /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type' warnings.warn(msg) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'cmd' /Philippe/ / Le 03/10/2019 à 17:06, Christopher Arndt a écrit : > Am 03.10.19 um 17:03 schrieb Philippe GARCIA-ORTUNO: >> I tried to do /python setup.py/ and /python timebase_master.py/ in a >> command line but I had some error message: for /python >> timebase_master.py :/ >> >> python timebase_master.py >> File "timebase_master.py", line 15 >> def __init__(self, name, *, bpm=120.0, beats_per_bar=4, >> beat_type=4, >> ^ >> SyntaxError: invalid syntax > > You need to use Python 3. You can install the scripts with "python3 > setup.py install", but you can also just run timebase_master.p > directly from the root of project: > > $ python3 transport/timebase_master.py --help > > Chris > > > P.S. Please answer to the mailing list, not to me personally. >

5 years, 2 months

[Jack-Devel] synchronization with Jack transport

by Philippe GARCIA-ORTUNO

Hello, I have a problem of synchronization with Jack: for a song at a tempo of 120bpm I drive several synths including a hardware Tempest in slave mode with seq24 disconnected from jack transport and everything is fine. But if I connect seq24 to Jack my Tempest suddenly turns much more slowly, I would say almost half the tempo. Would you have any idea where the problem might come from? thank you in advance for your help, best regards, Philippe

5 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

JackAudio October 2019