On Sun, January 28, 2018 9:34 am, Benny Alexandar wrote:
> After starting jack server using qjackctl
What jack settings were used in qjackctl? Which driver was chosen, and
which interface?
> Then in qjackctl connected the graph as shown in the attached picture.
That graph works if j2a is controlling the sound card, if jack was started
with the ALSA driver and the USB device as the interface then jackd would
already be controlling the sound card.
When providing information it will save a lot of time if you actually copy
and past the command line you used as well as the resulting messages. For
example you stated that you started zita-a2j, did you start zita-j2a with
the same command line parameters as zita-a2j? What status messages were
printed at that time? What was in the messages window of qjackctl (that
is where the output from the jackd server is displayed)?
You have given about a fourth of the information needed to help you
determine what is happening on your system.
--
Chris Caudle
Hello,
Hello,
I tried to configure Jack control (Jack_v1.9.11_64_setup.exe) to bind Traktor to Ableton but the solution did not suit me, I uninstalled Jack Audio control and since then I can not launch the TRAKTOR 64-bit application .
I can still launch TRAKTOR in 32 but the uninstall has removed something that blocks the software.
Thank you for your help.
Vincent
Bonjour,
J'ai essayé de configurer Jack control (Jack_v1.9.11_64_setup.exe) pour lier Traktor vers Ableton mais la solution ne me convenant pas, j'ai désinstallé Jack Audio control et depuis je ne peux plus lancer l'appli TRAKTOR en 64 bits.
Je peux encore lancer TRAKTOR en 32 mais la désinstallation à enlevé qelque chose qui bloque le logiciel.
Merci de votre aide.
Vincent
Hello,
Hello,
I tried to configure Jack control (Jack_v1.9.11_64_setup.exe) to bind Traktor to Ableton but the solution did not suit me, I uninstalled Jack Audio control and since then I can not launch the TRAKTOR 64-bit application .
I can still launch TRAKTOR in 32 but the uninstall has removed something that blocks the software.
Thank you for your help.
Vincent
Bonjour,
J'ai essayé de configurer Jack control (Jack_v1.9.11_64_setup.exe) pour lier Traktor vers Ableton mais la solution ne me convenant pas, j'ai désinstallé Jack Audio control et depuis je ne peux plus lancer l'appli TRAKTOR en 64 bits.
Je peux encore lancer TRAKTOR en 32 mais la désinstallation à enlevé qelque chose qui bloque le logiciel.
Merci de votre aide.
Vincent
On Tue, January 23, 2018 10:12 am, Benny Alexandar wrote:
> Any documentation on how to use the jack_delay for measuring ?
$ man jack_iodelay
NAME
jack_iodelay - JACK toolkit client to measure roundtrip latency
SYNOPSIS
jack_iodelay
DESCRIPTION
jack_iodelay will create one input and one output port, and
then measures the latency
(signal delay) between them. For this to work, the output port must
be connected to its
input port. The measurement is accurate to a resolution of greater
than 1 sample.
The expected use is to connect jack_iodelay's output port to a
hardware playback port,
then use a physical loopback cable from the corresponding hardware
output connector to an
input connector, and to connect that corresponding hardware
capture port to jack_iode‐
lay's input port. This creates a roundtrip that goes through any
analog-to-digital and
digital-to-analog converters that are present in the audio hardware.
Although the hardware loopback latency is the expected use, it
is also possible to use
jack_iodelay to measure the latency along any fully connected
signal path, such as those
involving other JACK clients.
Once jack_iodelay completes its measurement it will print
the total latency it has
detected. This will include the JACK buffer length in addition to
any other latency in
the signal path. It will continue to print the value every 0.5
seconds so that if you
wish you can vary aspects of the signal path to see their effect on
the measured latency.
If no incoming signal is detected from the input port, jack_iodelay
will print
Signal below threshold... .
every second until this changes (e.g. until you establish the
correct connections).
To use the value measured by jack_iodelay with the -I and -O
arguments of a JACK backend
(also called Input Latency and Output Latency in the setup dialog
of qjackctl), you must
subtract the JACK buffer size from the result. The buffer size is
determined by multiply‐
ing the number of frames per period (given to the jackd backend
by the -p or --period
option) by the number of periods per buffer (given to the jackd
backend by the -n or
--nperiods option). Note that JACK2 will add an implicit
additional period when using
the default asynchronous mode, so for JACK1 or JACK2 in synchronous
mode, the buffer size
is n*p, but for JACK2 in asynchronous mode the buffer size is
(n+1)*p. Once the JACK
buffer size is subtracted from the measured latency, the result is
the "extra" latency
due to the interface hardware. Then, if you believe that the
latency is equally distrib‐
uted between the input and output parts of your audio hardware
(extremely likely), divide
the result by two and use that for input and output latency
values. Doing this measure‐
ment will enable JACK clients that use the JACK latency API to
accurately position/delay
audio to keep signals synchronized even when there are inherent
delays in the end-to-end
signal pathways.
AUTHOR
Originally written in C++ by Fons Adriaensen, ported to C by Torben
Hohn.
1.9.10 August 2017
JACK_IODELAY(1)
--
Chris Caudle
Could someone please have a look at this
<https://stackoverflow.com/questions/48336952/fail-to-compile-source-with-ja…>
? I have been trying to solve this for far too long hoping I could figure it
out by myself. I really want to start using JACK in my project though and I
am getting kind of frustrated. Maybe someone could tell me what they have
running on their machine? Distro/Compiler/Compiling Arguments/Any other
Programs/...
Every help is appreciated :) If you feel like something doesn't add up, I am
happy to retry everything.
Kind regards,
Ariel
--
Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html
On Tue, January 16, 2018 10:36 am, Benny Alexandar wrote:
> I want to test how zita-ajbridge behaves when there is a drift in clock.
> Any idea how to artificially create clock drift for testing purpose.
The clocks are going to naturally drift if they are not synchronized
externally.
In a lab environment I would use a frequency generator on a device that
could provide a S/PDIF stream for one of the devices to lock to, and
slowly vary the frequency.
Without lab equipment the best you could do would be to change the
temperature of the crystal that controls the sampling rate for one of the
devices.
Typically the equipment would be running around 30 degrees C, but the
components should be able to handle up to 50 degrees or 60 degrees C, and
down to about 0 degrees. The quartz oscillators will vary in frequency
several PPM as the temperature swings. Just be careful not to swing the
temperature too quickly, you could crack a solder joint, or potentially
cause the clock generator to lose sync if the frequency changes faster
than any PLL can track.
Assuming you don't have any lab rework equipment that can generate
controlled temperature air over a small area, your best bet might be a
hair dryer on low, and control the temperature by distance from the
blower.
--
Chris Caudle
Hi,
I'm using latest jack audio server version jackd 1.9.12. I have built simple client.c app
and able to capture audio from microphone input and play it out.
I have another USB soundcard which is connected to pc through USB.
How to get input from USB soud card ?
After connecting USB sound card and when printed the ports[] array
after executing the jack API jack_get_ports()
I could see only PC microphone capture ports, not showing USB ports.
-ben
[Apologies for cross-postings] [Please distribute]
Conference date: 7th - 10th June 2018
The Linux Audio Conference 2018 will be hosted at c-base, Berlin -
in partnership with the Electronic Music Studio (TU Berlin) and Spektrum.
https://lac.linuxaudio.org/2018
Deadline for all submissions: Friday, February 28th, 2018 (23:59 UTC)
- - -
1: Call for Papers / Posters / Workshops
LAC 2018 invites submissions of papers, posters and workshops addressing
all areas of audio processing based on Linux and open source software.
All submissions and presentations are in English. All submissions are
peer reviewed by a committee of experts from different disciplines.
Submissions can focus on technical, artistic or scientific issues and
can target developers or users.
For more details see the website:
https://lac.linuxaudio.org/2018/pages/cfp/
*Papers*
Papers must be written and presented in English.
The length of papers is 4 to 8 pages, with up to 5 keywords, and an
abstract of up to 200 words.
The poster presentations are based on paper submissions of 2-4 pages,
with up to 5 keywords and an abstract of up to 150 words.
*Workshops*
The workshop presentation (max duration of 2h) should be 1-4 pages, with
up to 5 keywords, and an abstract of up to 150 words to be published on
the conference website. Submit a brief description of the workshop
including URL (if available).
How to submit?
* Use the OpenConf online submission tool at
https://lac.linuxaudio.org/2018/openconf
* Select the relevant submission type ('_ PAPER _' / '_ POSTER _' / '_
WORKSHOP _')
* The required file format is PDF, formatted for A4 paper. Authors are
required to use the templates for paper formatting available as download
on the conference website.
* Please notify us if you need a special technical setup for your
presentation.
- - -
2: Call for Music Performances / Multimedia Installations
LAC 2018 also invites submissions of Electroacoustic Works and
Multimedia Installations. A jury will select the compositions and
installations to be included in the conference program according to
artistic merit and technical feasibility.
Please be prepared to perform your work yourself and make sure that you
have all resources needed to perform your piece at your disposal (e.g.
instruments, other performers, etc.).
Unfortunately, LAC 2018 cannot pay a fee neither for you nor for any
additional performers, and LAC 2018 cannot organize or pay for travel or
accommodation neither for you nor for any additional performers.
All submissions are peer reviewed by a committee of experts in music and
arts.
Electroacoustic Works and Multimedia Installation can address all areas
of digital audio and audiovisual art.
Available Technical Setups
For concerts, the LAC will provide the following equipment:
* 8-channel - speaker setup
* Stereo setup + video projection
* Digital mixing desk
Additional requests can not be guaranteed.
How to submit?
* Use the OpenConf online submission tool at
https://lac.linuxaudio.org/2018/openconf
* Select the submission type '_ PERFORMANCE _'
* The required file format is PDF, formatted for A4 paper. It includes:
* Description of the project program notes
* Link to video or audio demonstration of the project
* Technical rider of the work
Important Dates
* Deadline for all submissions: Friday, February 28th, 2018 (23:59 UTC)
* Acceptance notification: March 31st, 2018
* Final deadline for 'camera ready' paper: April 15th, 2018
* Author registration deadline: April 15th, 2018
* Final program: May 1st, 2018
Up-to-date information regarding the conference can be found on its website:
https://lac.linuxaudio.org/2018
Looking forward to seeing you in Berlin!
The Linux Audio Conference 2018 team