pulseaudio alarm.

Jack 1 is alsa and Linux Midi.
Jach 2 is pulseaudio and Apple OSX Midi.

They did not finish to port everything from Jack 1 to Jack 2 yet but
they continued to develop Jack 1.

I am seeing this through my Slackware without pulseaudio eyes and I do
experience both on AMD and Intel Atom a better audio and faster system.

The other problem might be Jack 1 C, Jack 2 C++

So sorry to mention Gentoo:
There might be a virtual Package Jack, that is emty and needs either
Jack 1 or Jack 2 ...

nut that only moves the trouble onto somebody elses desk and is a pain
for the user.

Kind regards
Peter

On 11/25/2019 10:52 AM, Dave Woodfall wrote:
On 2019-11-25 08:50,
Felix Pfeifer <pfeifer.fe...@gmail.com> put forth the proposition:
Personally, I find changing things to jack-audio-connection-kit from jack2 is
a regression, and I'd recommend going the other way.  I don't know the reasons
that people stick to the now very old version.

I've been running jack2 for several years and had no problems with it, or had
to downgrade to the older jack.  It's also what all the apps on Studioware
use, and there haven't been any problems reported about it.

This is just my 2 pennies though, speaking as an everyday jack user.



Is jack2 supporting ALSA-MIDI?
For my builds it would be OK to switch to jack2
as long as it supports ALSA-MIDI which I use
to connect to my hardware. Also pd comes with
support for ALSA-MIDI.

cheers,
Felix

I don't use midi myself and I have a slightly older version installed
than on SBo at the moment, but the jackd man page has under alsa backend
options -X, --midi [seq|raw]

"Specify which ALSA MIDI system to provide access to. Using raw will
provide a set of JACK MIDI ports that correspond to each raw ALSA device
on the machine. Using seq will provide a set of JACK MIDI ports that
correspond to each ALSA "sequencer" client (which includes each hardware
MIDI port on the machine). raw provides slightly better performance but
does not permit JACK MIDI communication with software written to use the
ALSA "sequencer" API."

  ZSH<31>% jackd -dalsa -Xseq -r48000 -i2 -o2
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
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
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|2|2|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit float little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit float little-endian
ALSA: use 2 periods for playback
port created: Midi-Through:midi/playback_1
port created: Midi-Through:midi/capture_1
port created: PCR:midi/playback_1
port created: PCR:midi/capture_1
port created: PCR:midi/playback_2
port created: PCR:midi/capture_2
port created: PCR:midi/playback_3

  ZSH<30>% jack_lsp
system:capture_1
system:capture_2
system:playback_1
system:playback_2
system:midi_capture_1
system:midi_playback_1
system:midi_capture_2
system:midi_playback_2
system:midi_capture_3
system:midi_playback_3
system:midi_capture_4

ZSH<32>% jackd -dalsa -Xraw -r48000 -i2 -o2
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
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
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|2|2|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit float little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit float little-endian
ALSA: use 2 periods for playback
scan: added port hw:3,0,0 in-hw-3-0-0-PCR-MIDI
scan: added port hw:3,0,1 in-hw-3-0-1-PCR-1
scan: added port hw:3,0,2 in-hw-3-0-2-PCR-2
scan: added port hw:3,0,0 out-hw-3-0-0-PCR-MIDI
scan: added port hw:3,0,1 out-hw-3-0-1-PCR-1
scan: opened port hw:3,0,0 in-hw-3-0-0-PCR-MIDI
scan: opened port hw:3,0,1 in-hw-3-0-1-PCR-1
scan: opened port hw:3,0,2 in-hw-3-0-2-PCR-2
scan: opened port hw:3,0,0 out-hw-3-0-0-PCR-MIDI
scan: opened port hw:3,0,1 out-hw-3-0-1-PCR-1

ZSH<30>% jack_lsp
system:capture_1
system:capture_2
system:playback_1
system:playback_2
system:midi_capture_1
system:midi_capture_2
system:midi_capture_3
system:midi_playback_1
system:midi_playback_2

I can't imagine why they would ever remove midi support, but I hope that
helps.

-daw



_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


--
Peter and Karin Dambier
Adalbert-Stifter-Strasse 17
D-69509 Moerlenbach
+49(6209)280-3030 (VoIP: GGEW)
+49(6252)750-308 (VoIP: sipgate.de)
mail: pe...@peter-dambier.de
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to