On Sat, February 10, 2018 12:08 pm, Benny Alexandar wrote:
> In the latest installation of jackd (1.9.12) the man page for zita-a2j/j2a
> says at the end ported to C code, where can I find this ported C source
code.
> Is it freely available or as lib ?
It would be freely available, but I have not seen that note. Check the
jack github pages, it could be referring to the equivalent function
included as part of the jackd v1 code.
--
Chris Caudle
Hello! OK, previously I had Akai MPC 2.0 Jacked to Harrison Mixbus and it
worked perfectly. I had to format my HDD & reinstall Windows , and I set
everything up exactly the same, yet Jack cannot see the MPC's midi out now.
I use W10 Pro x64, 8gb ram. Audio connections are working perfectly. Mixbus
can see the MPC's midi out, but Jack cannot. MPC midi out is handled by a
separate application called midimon.exe and is normally seen as
"AkaiProInternalMidi." In both the connections section and the patchbay,
it's as if it doesn't exist. I tried installing it as admin, and running it
as admin too, no change. Is there a way to force Jack to see it? MPC has a
crippled mixer, Jacking it to Mixbus is a crucial part of my workflow.
Please help! Thank you.
--
Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html
Hi,
I've built jack2 without dbus support for my headless RPi3 but now I'd like to easily install it on another Pi (Zero), so preferrably I'd like to create a .deb package.
How do I go about doing this ?
Regards
/Robert
Hi everyone,
capturing from ALSA capture devices via the Jack2 sound server (1.9.12),
results in too high pitched wav files (they are playing "too fast" and
sound like the "chipmunks"). If I run the same capture directly from the
ALSA devices (without Jack involved), everything sounds as expected
without any problems.
Audio examples:
Capture via jackrec: https://filebin.ca/3pyMxBw8cexQ/test-jackrec.wav
Capture via arecord: https://filebin.ca/3pyOPjcKGym5/test-arecord.wav
The device in question is a "virtual" Axia-ALSA (Livewire+) audio device
on CentOS 7 which operates at a sample rate of 48kHz and a bit depth of
either 16 or 32. As far as I can see, the sample rate and format
detection on the Jack side looks correct. I'm therefore looking for some
guidance on how to further debug this, I most certainly missed something
obvious.
I've also tried to play an mp3 file via mpg123 over jack (without the
involvement of the Alsa device) and record it again with jackrec. This
works and sounds correct.
Here is what I've tried and what the environment looks like:
# Capabilities of the Axia-ALSA device
arecord -D hw:0 --dump-hw-params
Recording WAVE 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono
HW Params of device "hw:0":
--------------------
ACCESS: MMAP_INTERLEAVED RW_INTERLEAVED
FORMAT: S16_LE S32_LE
SUBFORMAT: STD
SAMPLE_BITS: [16 32]
FRAME_BITS: [16 256]
CHANNELS: [1 8]
RATE: 48000
PERIOD_TIME: (41 1365334)
PERIOD_SIZE: [2 65536]
PERIOD_BYTES: [64 131072]
PERIODS: [1 1024]
BUFFER_TIME: (41 1365334)
BUFFER_SIZE: [2 65536]
BUFFER_BYTES: [64 131072]
TICK_TIME: ALL
--------------------
arecord: set_params:1299: Sample format non available
Available formats:
- S16_LE
- S32_LE
# Capture via arecord directly from the ALSA device (without jackd)
# This works as expected and the WAV file sounds fine
arecord -D hw:0 -c 2 -d 10 -r 48000 -f S32_LE -v /tmp/test-arecord.wav
Recording WAVE '/tmp/test-arecord.wav' : Signed 32 bit Little Endian,
Rate 48000 Hz, Stereo
Hardware PCM card 0 'Axia' device 0 subdevice 0
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S32_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 32
buffer_size : 16384
period_size : 4096
period_time : 85333
tstamp_mode : NONE
tstamp_type : MONOTONIC
period_step : 1
avail_min : 4096
period_event : 0
start_threshold : 1
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
appl_ptr : 0
hw_ptr : 0
# playing arecord wav (via my local notebook's HDA Intel PCH
# device), sounds correct
aplay test-arecord.wav
Playing WAVE 'test-arecord.wav' : Signed 32 bit Little Endian, Rate
48000 Hz, Stereo
# Starting jackd
# Verbose output at: https://pastebin.com/YzHEGSnR
jackd -d alsa -d hw:0
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 20
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
# Capture via jackrec
# This results in a too high pitched WAV file
# Verbose output at: https://pastebin.com/PCnymKLA
jackrec -f /tmp/test-jackrec.wav -d 10 -b 32 system:capture_1
system:capture_2
# playing jackrec wav (via my local notebook's HDA Intel PCH
# device), sounds incorrect
aplay test-jackrec.wav
Playing WAVE 'test-jackrec.wav' : Signed 32 bit Little Endian, Rate
48000 Hz, Stereo
System environment:
Distribution: CentOS 7.4.1708
Kernel: 3.10.0-693.17.1.el7.x86_64
ALSA Utils: 1.1.3
Jackd: 1.9.12
The jackd was rebuilt from Fedora source RPM to be able to test with the
latest version:
https://build.opensuse.org/package/show/home:radiorabe:audio/jack-audio-con…
Many thanks and best regards
Chris
Sorry, posted with wrong sender ...
Am Mittwoch, 31. Januar 2018 17:25 CET, "Ralf Mattes" <r.mattes(a)mh-freiburg.de> schrieb:
>
> Am Mittwoch, 31. Januar 2018 17:07 CET, Robert Bielik <Robert.Bielik(a)dirac.com> schrieb:
> > [...]
> > jackd 578 pi 3u REG 0,16 12 11510 /dev/shm/jack_sem.1000_default_system (deleted)
> > jackd 578 pi 4u CHR 116,0 0t0 11412 /dev/snd/controlC0
> > jackd 578 pi 5u unix 0xb78a4380 0t0 8031 /dev/shm/jack_default_1000_0 type=STREAM
> > jackd 578 pi 6u CHR 116,16 0t0 11413 /dev/snd/pcmC0D0p
> > jackd 578 pi 7u CHR 116,24 0t0 11414 /dev/snd/pcmC0D0c
> > jackd 578 pi 8u unix 0xb78a7b80 0t0 8033 type=STREAM> jackd 578 pi 9u REG 0,16 12 8034 /dev/shm/jack_sem.1000_default_freewheel (deleted)
> > jackd 578 pi 10u unix 0xb78a7800 0t0 11511 /dev/shm/jack_default_1000_0 type=STREAM
> > /home/pi/start_jack
> > Interesting to see the DEL for file descriptor.
>
> Well, that means that "someone" removed those files from the filesystem. Since the jackd process still
> hase the file descriptors open the files are still there, but since the have no name anymore they are
> inaccessible ...
> Now you only have to find out _who_ did it ;-.)
>
>
> Cheers, RalfD
>
>
Hi all,
I'm putting together an inprocess client (as it was the lowest hanging fruit), but I'd like to output log messages, I note that outputting to stdout/stderr doesn't seem to work.
Is there any API into which I can hook my logging framework output ?
Regards
/Robert
