Re: [Slackbuilds-users] Wrong MD5SUM for libreoffice-6.2.8.2-srcs.tar.xz at SourceForge?
On 26/11/19 5:41 am, Andrzej Telszewski wrote: > Hi, > > When downloading: > http://sourceforge.net/projects/slackbuildsdirectlinks/files/LibreOffice/libreoffice-6.2.8.2-srcs.tar.xz > > > I get the following md5sum: > b5d5e57832056d8a5625b1d5dc3aa024 > > whereas .info states the following one: > 1fcf52003e0d3c514caf8bfd40b6b88e > > > Where lies the problem? > Maintainer error. It should be: b5d5e57832056d8a5625b1d5dc3aa024 and will be fixed soon. Thanks, chris ___ 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/
Re: [Slackbuilds-users] Trouble downloading from sourceforge.net
On Mon, Nov 25, 2019 at 08:36:06PM +0100, Peter Dambier wrote: > Hi, > > e.g. from pcmanfm Slackbuild I wanted to download > > "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz; > > After lots of lots of redirect wget gave up. > [snip] Not sure - but incidentally I was having similar problems with github yesterday. 500 errors abound. Coincidence? ___ 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/
Re: [Slackbuilds-users] Trouble downloading from sourceforge.net
On Mon, 25 Nov 2019, Matteo Bernardini wrote: > Date: Mon, 25 Nov 2019 14:49:43 > From: Matteo Bernardini > Reply-To: SlackBuilds.org Users List > To: SlackBuilds.org Users List > Subject: Re: [Slackbuilds-users] Trouble downloading from sourceforge.net > > Il giorno lun 25 nov 2019 alle ore 20:35 Peter Dambier > ha scritto: > > > > Hi, > > > > e.g. from pcmanfm Slackbuild I wanted to download > > > > "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz; > > > > After lots of lots of redirect wget gave up. > > > > Trying the homepage got me into an ants nest where stupid me signed up > > for a newsletter in the 50th floor below ground but I still could not > > get the source. > > > > Google finally found it at: > > > > "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz; > > > > Again lots of lots of redirect and finally I get it from > > > > "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz; > > > > The redirects for both URLs looked the same. That is why I dont think > > there is a need to change the download in the SlackBuild. > > > > Horses tend to drop their manure everywhere but I remember there > > were quite a lot of downloads that did not succeed. pcmanfm actually was > > the first one I finally made to download after all obstacles. > > > > md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. > > > > and it runs on Slackware Current 32 Bit. > > > > Sorry for the rant but I had to vent because if I had blown my top like > > SpaceX did with Starship MK 1, I would look really silly :) > > maybe is a temporary problem at SourceForge, it happens sometimes. > > remember that there's a backup hosting for the tarballs linked here at > SBo, sbosrcarch (courtesy of Urchlay and hosted by Tadgy) > > http://slackware.uk/sbosrcarch/ > ___ > 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/ > The line I have in my sf.sh takes care of that: wget -bc $1 --max-redirect=1 --trust-server-names Once that's started you check on it these ways. First wc -l wget-log if it's larger than 6 lines the download is probably working. Then every so often: grep -i saved wget-log Nothing back from grep the download is still in progress. When saved appears you get the file information including the correct name of the file on your system. That's what that --trust-server-names switch does for you. I hope this helps. > -- ___ 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/
Re: [Slackbuilds-users] Trouble downloading from sourceforge.net
On 11/25/2019 08:49 PM, Matteo Bernardini wrote: Il giorno lun 25 nov 2019 alle ore 20:35 Peter Dambier ha scritto: Hi, e.g. from pcmanfm Slackbuild I wanted to download "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz; After lots of lots of redirect wget gave up. Trying the homepage got me into an ants nest where stupid me signed up for a newsletter in the 50th floor below ground but I still could not get the source. Google finally found it at: "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz; Again lots of lots of redirect and finally I get it from "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz; The redirects for both URLs looked the same. That is why I dont think there is a need to change the download in the SlackBuild. Horses tend to drop their manure everywhere but I remember there were quite a lot of downloads that did not succeed. pcmanfm actually was the first one I finally made to download after all obstacles. md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. and it runs on Slackware Current 32 Bit. Sorry for the rant but I had to vent because if I had blown my top like SpaceX did with Starship MK 1, I would look really silly :) maybe is a temporary problem at SourceForge, it happens sometimes. remember that there's a backup hosting for the tarballs linked here at SBo, sbosrcarch (courtesy of Urchlay and hosted by Tadgy) http://slackware.uk/sbosrcarch/ ___ 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/ Thankyou Matteo, That is good news. Cheers Peter -- 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/
Re: [Slackbuilds-users] Trouble downloading from sourceforge.net
Il giorno lun 25 nov 2019 alle ore 20:35 Peter Dambier ha scritto: > > Hi, > > e.g. from pcmanfm Slackbuild I wanted to download > > "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz; > > After lots of lots of redirect wget gave up. > > Trying the homepage got me into an ants nest where stupid me signed up > for a newsletter in the 50th floor below ground but I still could not > get the source. > > Google finally found it at: > > "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz; > > Again lots of lots of redirect and finally I get it from > > "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz; > > The redirects for both URLs looked the same. That is why I dont think > there is a need to change the download in the SlackBuild. > > Horses tend to drop their manure everywhere but I remember there > were quite a lot of downloads that did not succeed. pcmanfm actually was > the first one I finally made to download after all obstacles. > > md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. > > and it runs on Slackware Current 32 Bit. > > Sorry for the rant but I had to vent because if I had blown my top like > SpaceX did with Starship MK 1, I would look really silly :) maybe is a temporary problem at SourceForge, it happens sometimes. remember that there's a backup hosting for the tarballs linked here at SBo, sbosrcarch (courtesy of Urchlay and hosted by Tadgy) http://slackware.uk/sbosrcarch/ ___ 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/
[Slackbuilds-users] Wrong MD5SUM for libreoffice-6.2.8.2-srcs.tar.xz at SourceForge?
Hi, When downloading: http://sourceforge.net/projects/slackbuildsdirectlinks/files/LibreOffice/libreoffice-6.2.8.2-srcs.tar.xz I get the following md5sum: b5d5e57832056d8a5625b1d5dc3aa024 whereas .info states the following one: 1fcf52003e0d3c514caf8bfd40b6b88e Where lies the problem? Thanks in advance! P.S. Bcc'd maintainer. -- Best regards, Andrzej Telszewski ___ 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/
[Slackbuilds-users] Trouble downloading from sourceforge.net
Hi, e.g. from pcmanfm Slackbuild I wanted to download "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz; After lots of lots of redirect wget gave up. Trying the homepage got me into an ants nest where stupid me signed up for a newsletter in the 50th floor below ground but I still could not get the source. Google finally found it at: "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz; Again lots of lots of redirect and finally I get it from "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz; The redirects for both URLs looked the same. That is why I dont think there is a need to change the download in the SlackBuild. Horses tend to drop their manure everywhere but I remember there were quite a lot of downloads that did not succeed. pcmanfm actually was the first one I finally made to download after all obstacles. md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. and it runs on Slackware Current 32 Bit. Sorry for the rant but I had to vent because if I had blown my top like SpaceX did with Starship MK 1, I would look really silly :) Cheers Peter -- 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/
Re: [Slackbuilds-users] Jack policy
On Sunday, November 24, 2019 02:38:01 PM Franzen wrote:
> Hi,
>
> as there is no 'or/||' possible in the REQUIRES tag, installing package
> "a" with REQUIRES=jack-audio-connection-kit
> and then installing package "b" with REQUIRES=jack2 will end with a
> broken jack, as jack-audio-connection-kit and jack2
> are conflicting packages. Details at
> https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_ja
> ck2
>
> Grepping throus SBo git shows
>
> slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' +
>
> | grep jack-audio-connection-kit | wc -l
>
> 73
> slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' +
>
> | grep jack2 | wc -l
>
> 6
>
> If i change my builds to jack-audio-connection-kit, then there will only
> be two builds left with dep on jack2, namely
> MuseScore and lives.
> If their maintainers have no problem with jack-audio-connection-kit,
> maybe jack-audio-connection-kit could
> be handled as default jack on SBo?
>
> Johannes
> ___
> 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/
I've been struggling with this on SBo for years. Last time I asked this list,
the consensus was to just make a note in the README that *either* jack-audio-
blah or jack2 were required.
My thought was to just specify that "jack" is required, and let the user
decide whether to install 'jack-audio-connection-kit' or 'jack2', but I guess
that's a little too much like a "meta package".
I wouldn't mind using jack2 as the default for SBo, if we're voting on the
subject. I've used Jack2 since 2014 at least, and I've not run into problems
with ALSA, JACK, or MIDI. However, I only use software MIDI (input through USB
controllers) so I can't speak for physical [actual] MIDI interfaces. Even so,
it's nearly 2020, and I feel like "most" users could safely default to jack2.
The people connection daisy chains of MIDI synths directly to the back of
their computer can fallback on jack-audio-connection-kit.
___
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/
Re: [Slackbuilds-users] Jack policy
Am 25.11.19 um 12:29 schrieb Dave Woodfall: On 2019-11-25 12:15, Franzen put forth the proposition: So i think there's no need for a poll what jack is better Sorry, my fault really. In any case much value, i learned a lot about jack since yesterday. -daw Cool shortcut, you need to make music with computers ;-) ___ 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/
Re: [Slackbuilds-users] Jack policy
On 2019-11-25 12:15, Franzen put forth the proposition: > So i think there's no need for a poll what jack is better Sorry, my fault really. -daw signature.asc Description: PGP signature ___ 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/
Re: [Slackbuilds-users] Jack policy
On 2019-11-25 11:53, Peter Dambier put forth the proposition: > pulseaudio alarm. > > Jack 1 is alsa and Linux Midi. > Jach 2 is pulseaudio and Apple OSX Midi. Jack 2 works fine with Alsa and without pulse. That's how I've been using it for years. The jack2 man page says "Alsa MIDI", as I posted earlier. To stop pulseaudio, kill the daemon if it's running and comment out the lines in /etc/asound.conf: #pcm.default pulse #ctl.default pulse Then chmod -x /etc/rc.d/rc.pulseaudio to make sure it doesn't start at boot. This is the non-purist way of not using pulseaudio, and has worked for me since the release of 14.2. Also, the man page mentions about dbus: Defining $JACK_NO_AUDIO_RESERVATION will bypass audio device reservation via session bus (DBus). This can be useful if JACK was compiled with DBus support but should run on a headless system. I can confirm that it stops all the errors about X11 not running. -daw signature.asc Description: PGP signature ___ 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/
Re: [Slackbuilds-users] Jack policy
Hi, Jack 1 is alsa and Linux Midi. Jach 2 is pulseaudio and Apple OSX Midi. My intention was not to push users in either jack direction, but workaround the missing logical "or" in REQUIRES for applications that depend on a jack implementation. This could prevent pointless issues if someone e.g. install MuseScore and qtractor per sboutils, which aren't conflicting in reality. So i think there's no need for a poll what jack is better, but use the same jack for all apps in REQUIRES, and everybody is free to change that to the other jack, if one likes. The path to jack-audio-connecion-kit looked shorter to me, as only two builds need to be adjusted, but i don't have a preference. Johannes ___ 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/
Re: [Slackbuilds-users] Jack policy
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 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 ___
Re: [Slackbuilds-users] Jack policy
On 2019-11-25 18:27, Christoph Willing put forth the proposition: > Also jack2 doesn't support Linux MIDI, according to that table. What do they actually mean by "Linux MIDI" though? Alsa? I can't imagine they would drop MIDI support altogether. It's what most musicians use right? I'm only a guitarist though (or was), not a keyboard player, so I don't have any use for it other than testing that sequencer and synth software etc. works. -daw signature.asc Description: PGP signature ___ 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/
Re: [Slackbuilds-users] Jack policy
On 2019-11-25 08:50, Felix Pfeifer 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 signature.asc Description: PGP signature ___ 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/
Re: [Slackbuilds-users] Jack policy
On 25/11/19 5:50 pm, Felix Pfeifer wrote: >> 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. > For a detailed list of differences & pros/cons, see: https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 SMP capability in jack2 seems attractive but see info in that linked page about why that is not necessarily such a big deal. The detailed feature differences table mentions that jack1 has builtin support for multiple sound cards (not in jack2). Also jack2 doesn't support Linux MIDI, according to that table. In other comments on that page, it says: "... current plan is to implement all Jack1 features into Jack 2 ..." which suggests (to me) that jack2 is still missing some features from jack1. However, jack2 supports DBUS & PulseAudio - not necessarily a plus for some people - for which jack1 requires patching to enable. Maybe those differences have been resolved since then - version 0.121.3 for jack1 and 1.9.10 for jack2. We're now at 0.125.0 for jack1 and 1.9.12 for jack2. chris ___ 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/
