I have 2 PCs, both with a 64 channel madi card. Machine 'A' is
runing Win7, and the RME TotalMix is running showing what is on each
channel. I am also running Reaper, which has a plugin generating
tone on the 1st 8 channels which is visible on the TotalMix.
Machine 'B' is a dual boot Win7/Ubuntu 16.04, and when booted into
Win7, the tone coming in on the madi stream channels 1-8 is clearly
present and audable. When I boot into Ubuntu, I run QjackCtl and
start Jack. I then start a simple program I have written from a
tutorial I found that copies from the inputs to the outputs.
Unfortunately, nothing is received on the inputs. On the outputs
however if I fill the output Buffer with random numbers, the resulting
noise appears on machine 'A', so not everything is a total disaster.
I have checked alsamixer for muting on the inputs and am now at a loss
for possible causes. (I am summing the abs value of each frame in
input and periodically printf the total, which is always zero.
Could someone more knowledgeable that myself suggest causes for the
lack of input.
Zappa Fan. (mostly to make searching digests easier, but also true).
On Thu, Sep 15, 2016 at 12:27 AM, Paul Davis <paul(a)linuxaudiosystems.com>
> JACK has been a long, strange and wondrous journey, and even if at this
> point I lean towards thinking that the whole idea was a bit of a mistake (!
Definitely not. I guess you were thinking about some sub parts of jack when
you wrote this.
Firstly, jack provided a simple to use API to send and receive audio with
low latency to and from the soundcard.
Secondly, it made it possible for several programs to access the
so you didn't have to start and stop programs all the time.
There's a new release JACK1 now available.
(tagged in git as 0.125.0)
Changes since 0.124.1, in rough order of significance:
* in the alsa_midi slave driver, fix hotpug device enumeration. JACK1
will now respond
to MIDI devices being connected and disconnected while running.
* increase maximum size of a single JACK MIDI event to 64 bytes
* in the alsa_midi slave driver, fix thread start/stop handling when
* add support for jack_port_rename()
* fix incorrect ALSA backend latency values when used with other than 2
* drop support for CPU cycle counting clock, use kernel clocksource
* fix a double-fork that left zombie processes around
* improve the validity and usability of the return value of
* fix failing metadata look up by clearing UUID parsing buffer before use
* support unescaped double quotes in $HOME/.jackdrc
* fix memory leaks of metata key/value pairs
* fix crash caused by incorrect jack_error() format string
* remove option help from jackd and point user at documentation
* fix problems with garbage keys in metadata
* fix negative x-run values on Linux with ALSA backend and kernel 4.0 or
* build and run on openBSD with new sndio backend
* fix out-of-tree builds
* update configure.ac to work with current-ish autotools with less errors
* fix building on MacOS 10.12 (Sierra) where clock_nanosleep() is not
* enable use with Travis (continuous integration for OS X on github)
* correctly avoid Valgrind warning in one instance.
* use gcc atomics and CLOCK_REALTIME for generic CPU builds
* a handful of other minor bug fixes
Contributors: Hans-Peter Portner, Fons Adriaensen, Erik de Castro Lopo,
Filipe Coehlo, David Robillard, Adrian Knoth, Dominic Sacré, Peter Nelson,
Rui Nuno Capela, Robin Gareus, Peter Nelson, Paul Davis, Miroslav Urbanek,
Uladox, Josh de Kock, Jeremy Hu, Bernhard Wiedemann.
With this release of JACK1, I (Paul Davis) am stepping down from my
position as Benevolent Dictator for the project, and in all likelihood from
any active involvement with the continuing development of JACK1. Filipe
Coehlo (falktx to many of us) will be taking over my role as JACK1
maintainer, and I believe that this leaves the project in excellent hands.
JACK has been a long, strange and wondrous journey, and even if at this
point I lean towards thinking that the whole idea was a bit of a mistake (!
:), I want to thank all the amazing developers and users who contributed
their time, intelligence, insights and interest to the project, and hope
that it will continue forwards in the best possible way.