No, the goal is to run Jackd on RTOSor patch Jackd to make it run on
RTOS (not yet started !) .
Cheers
Jean-Louis
Le 17/02/2020 à 22:07, Ralf Mattes a écrit :
>
> Am Montag, 17. Februar 2020 21:03 CET, Jean-Louis Mounier <jean-louis.mounier(a)laposte.net> schrieb:
>
>> Hello friends,
>>
>> do you think it is possible to compile and run JackAudio on ESP32.
> You got linux running on an ESP32? Wow!
>
> Cheers, RalfD
>
>
>
Hello friends,
do you think it is possible to compile and run JackAudio on ESP32. It
could become a nice platform to connect "in ear" headphones or
microphones for example. ESP32 is a powerfull, cheap and low-power
platform having WiFi (2.4Ghz) and bluetooth capabilities.
This idea can be a platform to build a wireless (Wifi) for live
performance, avoiding cable use.
I'll try to work on this subject but, as a newbie, it may take a long
time. Hope some of you will bring some help.
Forgive my poor English as I am French speaking
Thank you in advance
Regards
Jean-Louis Mounier
Hello JACKies,
i tinkered this thing https://github.com/oskude/jackplot that plots jack audio data with opengl in real-time (and am a really happy puppy :D). but as i'm a c, jack and opengl noob, i was hoping to get some help here. (at least for the jack part)
so i set the jack data (pointer) to a global variable
https://github.com/oskude/jackplot/blob/bcac59813b01b3bf7c2ebebd4988b22f5bf…
and read that data in opengl draw function (when ever its ready to draw)
https://github.com/oskude/jackplot/blob/bcac59813b01b3bf7c2ebebd4988b22f5bf…
(ignoring the function i read it in, am i even reading the jack data correctly?)
i'm suprised that it works, and hasn't crashed!
but i have the feeling that this is a bad/unsafe way to do it...
any thoughts? tips? links?
Cheers,
Andre Osku Schmidt
ps. i know about error checking, but i would like to keep this code as small as possible, until i understand the core jack-audio-data-to-opengl-points part.
Hi,
Thank you for your great support in Jack.
I am trying to build a real-time application on basis of Jack Server and
Client architecture. But Jack capture and playback latency is failing me to
make the application sample accurate.
*My Jack server configuration (jackd -dalsa):*
*JACK server starting in realtime mode with priority 10 self-connect-mode
is "Don't restrict self connect requests" audio_reservation_init Acquire
audio card Audio0 creating alsa driver ...
hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz,
period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected
sample format for capture: 32bit integer little-endian ALSA: use 2 periods
for capture ALSA: final selected sample format for playback: 32bit integer
little-endian ALSA: use 2 periods for playback*
*My Understanding :*
0. Realtime mode = Yes, 10 priority
1. Sampling Rate = 48000Hz
2. 1 Periods = 1024 frames
3. Buffer Size = 2 Periods = 2048 frames
4. Capture Latency = 2 periods = 1 Buffer = 21.3 x2 ms
5. Playback Latency = 2 periods = 1 Buffer = 21.3 x2 ms
*Apllication:*
passthru/simple_client.c of Jack2 repositry with one client for both sterio
capture and mono playback
*My application pipeline:*
input -----------> capture left channel (stage 1) ------------> playback
left channel (stage 2) --------------> capture right channel (stage 3)
*Latency calculation:*
After stage 1 --------------- 2 periods = 42.6 ms
After stage 2 --------------- 2 + 2 periods = 85.2 ms
After stage 3 --------------- 2 + 2 + 2 periods = 127.8 ms
*Difference between stage 3 and stage 1*
6 periods - 2 periods = 4 periods
Latency difference should be 4 periods but I am getting larger than 4
periods like 4 periods which also differs with different trials.
*So, how can I make my application sample accurate or what is the correct
procedure?*
It will be a great help and advance thanks.
Best Regards
Ruhul Amin
Hi,
Thank you for your great support in Jack.
I am trying to build a real-time application on basis of Jack Server and
Client architecture. But Jack capture and playback latency is failing me to
make the application sample accurate.
*JACK server starting in realtime mode with priority 10self-connect-mode is
"Don't restrict self connect requests"audio_reservation_initAcquire audio
card Audio0creating alsa driver ...
hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bitconfiguring for 48000Hz,
period = 1024 frames (21.3 ms), buffer = 2 periodsALSA: final selected
sample format for capture: 32bit integer little-endianALSA: use 2 periods
for captureALSA: final selected sample format for playback: 32bit integer
little-endianALSA: use 2 periods for playback*
I noticed that the source distribution has and android directory, less
fortunate that without instructions. Does anyone happened to know how to
compile this for android device, or more in general how to cross compile
jack to for arm7?
best: steve
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.
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.
(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
