That is such good news. What(low cost) hardware would this development be
used on to support the developers with testing/debugging and maybe even
development ?
* MOTU LP32 (Preferred)
* MiniDSP https://www.minidsp.com/products/network-audio/avb-dg (I think
MOTU's switch uses midDSP switch hardware)
I hope someday it will be possible to connect 4 or more 8 channel ADAT
modules (32 channels) to a PC under Ubuntu via AVB with low latency. The
only option to get this done under Windows is a Focursrite DANTE based
Rednet 3 right now because Thunderbolt is not really available there as
well. Plan to get Rednet3, but that does not solve the Linux environment
which I prefer. Would love to be able to use the Rednet 3 under Linux but
since DANTE is proprietary , so unlikely.
My two wishes:
[a] Multi (16+) channel low latency audio I/O using ADAT audio AD/DA
[b[ Bitwig supporting LV2 plugins.
With those two, the Linux Audio environment would be perfect and the world
a better place.
*(Apology for the re-sends and ignore the previous edits. Web based Gmail
is such a annoyance and un-logically structured)*
I read here about how JACK handles the client ordering using the sortfeeds
and truefeeds list
https://github.com/jackaudio/jackaudio.github.com/wiki/A_guide_to_the_Jack1…
So with a graph like this:
A -> B -> C
When I make a connection between C and A:
C -> A
Then C will be added to A's sortfeeds list and the processing order will be
retained: [A, B, C].
My question is: when does A actually get C's output data? If JACK allows
the connection, then A should get as input C's output data. Is there a
one-cycle delay? That's kind of what I interpreted this
<http://jack-audio.10948.n7.nabble.com/Some-more-explanations-on-jackdmp-td1…>
to mean.
I also read this
<http://jack-audio.10948.n7.nabble.com/JACK-design-flaw-and-Proposal-td882.h…>
but didn't walk away with a clear idea of what JACK actually does.
This paper
<http://www.grame.fr/ressources/publications/Jackdmp-ICMC2005.pdf> says
In the event of feedback loops, there is no ”correct” ordering of the
> graph, so Jack just picks one of the legal possibilities.
Is the "legal" choice that JACK is making here the same thing as what is
discussed on the Wiki page at the top of my post?
Also, do jack2 and jack1 behave the same in this regard?
Using the following instructions to install Jack:
https://obsproject.com/forum/resources/advanced-audio-capture-mac-os-x.142/
When I get to step 4, there is no JackRouter choice listed in System
preferences/Sound/Output and select JackRouter. Do the same for input.
What do you suggest I do in order to complete the installation and
operation of Jack on my Mac in order to have game sounds and live
commentary as I stream games.
Thank you,
stoicmom
I need your help, my mic won't work when Jack PortAudio is turned on.
I connected my mic to a Focusrite Saffire Pro 24 DSP and am working on
windows 10, my microphone is connected to the first XLR input, and is
working fine when Jack PortAudio is not activated.
When I turn on Jack PortAudio however, it suddently doesn't register any
sound anymore on the Widnows VU metres (playback devices), what also changes
is that I can't change the sample rate anymore of my mic, the Advanced tab
is gone after I started JackPort Audio.
I have enabled jackportaudio.dll, and also did the target command line.
I have provided you with a Imgur link to the pictures with the description
under the pictures.
https://imgur.com/a/sq9iI
I really, really hope you can help me!
Sincerely,
Robin
--
Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html
FFADO version 2.4.0 is now available, a package of userspace drivers for
firewire audio interfaces. As for version 2.3.0, this version contains
mostly incremental improvements and bug fixes. There are no significant new
features in this version compared to the last, but users are encouraged to
upgrade to pick up the improvements.
This is a source-only release which can be downloaded from the ffado.org
website at
http://ffado.org
or via the direct link:
http://ffado.org/files/libffado-2.4.0.tgz
Notable changes include:
* Numerous build system and code improvements to support architectures such
as MIPS, x32 and various PowerPC flavours.
* A large number of fixes for newer versions of gcc (particularly versions
6 and 7).
* Initial support for the optional TCO module of the RME Fireface-800.
* Expanded ffado-mixer support for the Phase88 device.
* Initial work to make ffado-mixer compatible with python3/pyqt5.
* Start work towards compatibility with scons3.
Thanks go out to the developers and users who contributed code and
information which went into this release: Plamen Aleksandrov, Daniel
Cavalli, Xavier Forestier, Thorsten Glaser, Adrian Knoth, Dominik Meister,
Andras Muranyi, Orcan Ogetbil, "Olivier", Nils Philippsen, Takashi Sakamoto,
Shalok Shalom, Stefan Richter, Roland Stigge, "Vince" and Jonathan Woithe.
Apologies if there or errors or omissions - please contact us via the FFADO
mailing list and we'll be happy to make corrections.
[Apologies for cross-postings] [Please distribute]
*Save the date: Linux Audio Conference 2018*
The 2018 Linux Audio Conference will take place at
*c-base, Berlin*
*7th -11th June 2018*
The LAC 2018 will feature a full program of talks, workshops and music.
Theofficial call for papers and works will be sent shortly after the
winter break -
so use the quiet of the holidays to think about possible submissions.
All relevant information will be made availableon:
http://lac.linuxaudio.org/2018/
All the best,
the LAC 2018 Organizing Team
--
Henrik von Coler
Elektronisches Studio, Fachgebiet Audiokommunikation
Electronic Music Studio, Audio Communication Group
Technische Universität Berlin
Fakultät I Geistes- und Bildungswissenschaften
Institut für Sprache und Kommunikation
Faculty I Humanities
Institute of Speech and Communication
Einsteinufer 17c, Sekr. EN 8, 10587 Berlin
Germany
Tel: +49 (0)30 314 22327
Fax: +49 (0)30 314 21143
voncoler(a)tu-berlin.de
www.ak.tu-berlin.de
Hello there, I was using Jack until last month. Tried to start it today
and nothing. Any ad vice would be appreciated. Tx. JoeF.
15:45:55.995 Statistics reset.
15:45:56.038 ALSA connection change.
15:45:56.260 D-BUS: Service is available (org.jackaudio.service aka
jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
15:45:56.346 ALSA connection graph change.
15:45:59.493 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
Thu Dec 21 15:45:59 2017: Starting jack server...
Thu Dec 21 15:45:59 2017: JACK server starting in realtime mode with
priority 10
Thu Dec 21 15:45:59 2017: self-connect-mode is "Don't restrict self
connect requests"
Thu Dec 21 15:45:59 2017: ERROR: Cannot lock down 82274202 byte memory
area (Cannot allocate memory)
Thu Dec 21 15:45:59 2017: Acquired audio card Audio0
Thu Dec 21 15:45:59 2017: creating alsa driver ...
hw:0|hw:0|1024|3|44100|0|0|nomon|swmeter|-|32bit
Thu Dec 21 15:45:59 2017: ERROR:
ATTENTION: The playback device "hw:0" is already in use. Please stop the
application using it and run JACK again
Thu Dec 21 15:45:59 2017: ERROR: Cannot initialize driver
Thu Dec 21 15:45:59 2017: ERROR: JackServer::Open failed with -1
Thu Dec 21 15:45:59 2017: ERROR: Failed to open server
Thu Dec 21 15:46:00 2017: Saving settings to
"/home/lulujoe13/.config/jack/conf.xml" ...
15:46:08.819 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
4294967295, skipping unlock
A few days ago a new version of JACK2 was released.
You can grab the latest release source code at
https://github.com/jackaudio/jack2/releases.
The official changelog is:
- Fix Windows build issues
- Fix build with gcc 7
- Show hint when DBus device reservation fails
- Add support for internal session files
If you did not know already, I am now maintaining JACK2 (and also JACK1).
So this latest release was brought to you by yours truly. ;)
The release was actually already tagged on the git repo quite some time
ago, but I was waiting to see if Windows builds were possible.
I got side-tracked with other things and 1.9.12 ended up not being
released for some time, until someone reminded me of it again... :)
There are still no updated macOS or Windows builds, but I did not want
to delay the release further because of it.
The 1.9.11 release (without RC label) was skipped to avoid confusion
with the versions.
So 1.9.12 is the latest release as of today. macOS and Windows binaries
still use an older 1.9.11 version.
Being the maintainer of both JACK1 and JACK2 means I can (more or less)
decide the future of JACK.
I believe a lot of people are interested to know the current plan.
First, JACK1 is in bug-fix mode only.
I want to keep it as the go-to reference implementation of JACK, but not
add any new features to it.
The reason for this is to try to get JACK1 and JACK2 to share as much
code as possible.
Currently JACK2 includes its own copy of JACK headers, examples and
utilities, while JACK1 uses sub-repositories.
During the course of next year (that is, 2018) I want to get JACK2 to
slowly use the same stuff JACK1 does, then switch to use the same
repositories as submodules like JACK1 does.
This will reduce the differences between the 2 implementations, and make
it a lot easier to contribute to the examples and utilities provided by
JACK.
(Not to mention the confusion caused by having utilities that work in
simlar yet different ways)
We will keep JACK1 "frozen" until this is all done.
Second, but not least important, is to get the JACK1 specific features
into JACK2.
A few things were added into JACK1 after JACk2 was created, that never
made it into JACK2.
This includes meta-data (JACK2 does have the API, but a non-functional
one) and the new internal clients.
The purpose is to reduce reasons users might have to switch/decide
between JACK1 and JACK2.
JACK2 should have all features that JACK1 has, so that most users choose
JACK2.
Now, you are probably getting the impression that the focus will be on
JACK2, which is correct.
Though I realize some developers might prefer JACK1's design, the long
"battle" of JACK1 and JACK2 needs to stop.
Development of new features will happen in the JACK2 codebase, and JACK1
will slowly become legacy.
Well, this is my personal plan at least.
Not sure if this all can be done in 2018, but better to take things
slowly and get things done than do nothing at all.
I will keep you updated on the progress through-out the year.
Happy holidays everyone!
Hi!
I came across several locations in the Jack source code which look like
copy&paste style bugs (see attached diff). Maybe someone familiar with the
code can review these?
Thanks & kind regards,
Markus
