Hi,
Simple question about JACK that I haven't been able to find anywhere else.
Hoping someone here's kind enough to set me straight. :)
Coming from PulseAudio, I noticed that JACK's documentation and discussions
seem to barely mention things regarding channels....but do refer to ports
quiet
often. So I was wondering what kind of mapping there is between say L and R
channels and JACK ports? Or does a mapping even exists?
Thanks,
Hai
Hi,
is the build for Mac OS X currently maintained? Where are the
most up-to-date build instructions to be found? I see there's a
waf wscript set up in the macosx folder, but there's also the
XCode project. Which one is the 'official' way to build, which
one would you prefer to have fixed if I dig into this (neither
works out of the box)?
Thanks!
Patric
Hi,
I'm building a test application for doing bit-perfect loopback
testing on my sound card drivers. However, since jack uses floating
point types, it seems that I can't get a bit-perfect data in and out
from (16-bit) 0x0000 to 0xFFFF. the LSB seems to get rounded on and
off, and also it seems that jack enforces a range of -32767 to +32767
instead of -32768 to +32767 (for 16-bit audio).
Is it possible that it's as simple as changing jack_default_audio_sample_t?
:-)
Thanks,
-Caleb
Hello,
I have a question:
Is it expected that calling "get_all_connections(port)" from a port
registration callback in libjack can cause client being timed-out by
jackd1?
See more detailed test-case description and error output below.
I was creating an app where JACK (used only jackd1) manager code would
connect/disconnect JACK ports as they appear or disappear, with the
assumption that it'd be the only app managing jack connections
on-the-fly.
Fairly obvious (expected) way to do it seem to be:
* Init client.
* Run "set_port_registration_callback(my_callback)".
* Enumerate all current ports, create all connections between these.
* On every port registration callback:
* Run "get_all_connections(port)".
* connect() to ports which should-be - but not yet - connected.
* disconnect() from ports that should not be connected, but got
returned from that call.
But when I tried doing that, it seems that running
"get_all_connections(port)" causes (unexpected) error when port with
same name appears for the second time during app lifecycle.
I.e. starting jackd1 as "jackd -d dummy", then starting the client,
then running "alsa_out -d hw:CARD=SB", stopping alsa_out and running it
again, causes the client to time-out.
Error message in client (from libjack, I think):
cannot read result for request type 10 from server (Connection reset by peer)
cannot send event response to engine (Broken pipe)
cannot continue execution of the processing graph (Bad file descriptor)
jack_client_thread: graph error - exiting from JACK
jackd output when this happens:
timeout waiting for client test-client to handle a port registered event
cannot send port registration notification to test-client (Resource temporarily unavailable)
One complication here is that I'm using not a C client, but a python
CFFI wrapper around it (see links below), which seem to translate API
pretty much verbatim from what I see in doxygen docs.
But I can't be sure it's not an issue with the wrapper, of course.
I've attached the python code that 100% reliably reproduces this
behavior on this machine, and on clean a Debian Jessie VM.
Running "get_all_connections(port)" anywhere outside of that callback
seem to resolve (or work around) the issue.
I wasn't able to find any reference to the issue (i.e. something like
"you should not do that!") in the docs or the google, and python module
author can't confirm (see links below) whether it's an API bug/feature
or a problem with python module itself.
So the question is basically whether it's expected behavior of jack API
(and maybe is or should-be documented somewhere), or totally
unexpected, and likely an issue with python module?
Python API wrapper module:
https://github.com/spatialaudio/jackclient-python/
Related issue I've opened with the python API wrapper module:
https://github.com/spatialaudio/jackclient-python/issues/30
Python (python2) code to reproduce the issue (also attached to this mail):
http://hastebin.com/dehubayeyo.py
Code link above also contains instructions on how to run it to
reproduce the issue.
This code depends on python jack client module linked above, which can
be built/installed with e.g. "pip2 install --user jack-client"
(to ~/.local/, "pip" script is usually packaged in distros as
"python2-pip" [arch] or "python-pip" [debian]).
Would appreciate any suggestions. Thanks!
--
Mike Kazantsev // fraggod.net
Hi,
I just wanted to report that the website is available under both
http://www.jackaudio.org and http://jackaudio.org. This is not good
practice, it can be identified as duplicate content, it should be
considered having the www. version redirect to the naked one, or vice versa.
Xavi
[repost from LAD, forgot jack-devel in the list of recipients]
Hi!
Alexander Carot contacted me to spread the news:
Starting in April 2016, three research assistant positions (PhD
candidates welcome) will be available within the Soundjack project. If
interested, please contact Prof. Carôt (a.carot(a)inf.hs-anhalt.de).
(copy-pasted from <http://www.soundjack.eu/jobs.html>)
I've been told one is TV-L13, the other is 75% and the third is 50%
(money equivalent can be found here [0])
The project will be about making music in a distributed environment,
contract will last three years (no idea if extendible).
Working from home is negotiable and even considered part of the project.
Candidates are expected to speak English, German is explicitly NOT
required.
Feel free to forward to interested parties.
Cheers
[0]
https://de.wikipedia.org/wiki/Tarifvertrag_f%C3%BCr_den_%C3%B6ffentlichen_D…
On Tue, Aug 25, 2015 at 3:38 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
> On Tue, Aug 25, 2015 at 12:31:13PM -0400, Paul Davis wrote:
>
>> Indeed. I'm out for 2 weeks on vacation with only intermittent network
>> access. Back next week. A pull request or a straightforward patch
>> would make the next step much easier, but i'll deal with it one way or
>> another.
>
> OK, enjoy the off-line time :-) I'll be doing the same from next friday
> until 17 september (Greece, diving).
>
> I'll send you the output of git diff and the modified files, along with
> some notes on how things are supposed to work. There are some open
> questions that only someone very familiar with the code can resolve.
Please send that diff.
Hi all.
After upgrading to fc22 during summer, I'm having issues with 32bit jack
clients running in my 64bit jackd.
I'd be thankful for any clues to what's going on, and ways to debug
this. And if others would care to check, and confirm/disprove the same
behavior, please tell me what you get.
Here's what happens:
The 32bit clients connect well, but the callbacks never seem to return,
making jackd send out a steady stream of xruns and errors:
JackEngine::XRun: client = simple_client was not finished, state = Triggered
I'm checking with jack2 installed (jack-1.9.10), with .i686 and .x86_64
versions installed using the standard fedora packages.
The same 32bit clients work well in fc21, fc20, and ubuntu 14.04 (in a
vm on the same hardware). Afaik, nothing has changed vs. the -mixed
flag in jackd, and would expect 32bit clients to run well inside a 64bit
jackd.
Checking with example-clients/simple-client.c from the jack sources:
$ gcc -m32 -g -O -lm -ljack simple_client.c -o simple_client
$ ./simple_client
- results in the noted behavior. Without -m32 everything's fine.
Thanks,
-anders