Hi :)
I added what I did below chronologically arranged. The first try failed
because of Packman libs. The second try failed because of less Packman
libs too.
I don't know what to install and then how to use ldconfig. When I last
tried to remove the whole studio in the box, by removing or first
install and then removing jack by zypper it failed.
I installed jack by YaST2 from repo-oss.
I don't know what to do. I can't install or remove jack, all because I
upgraded from the repo-oss version 0.109 to the Packman's version 0.116.
Cheers,
Ralf
------------------------------------------------------------------------
------------------------------------------------------------------------
FIRST TRY
PACKMAN PROBLEM
spinymouse@suse11:/usr/src/packages/RPMS/x86_64> wget
http://www.sonarnerd.net/suse11/jack-0.116.1-16.jl.suse.x86_64.rpm
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # rpm -iv
jack-0.116.1-16.jl.suse.x86_64.rpm
error: Failed dependencies:
libcap is needed by jack-0.116.1-16.jl.suse.x86_64
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # zypper install libcap
Downloading repository 'Packman Repository' metadata [done]
Building repository 'Packman Repository' cache [done]
Reading installed packages...
The following NEW package is going to be installed:
libcap1
Overall download size: 8.0 K. After the operation, additional 16.0 K
will be used.
Continue? [YES/no]: y
Downloading package libcap1-1.10-10.1.x86_64 (1/1), 8.0 K (16.0 K unpacked)
Downloading: libcap1-1.10-10.1.x86_64.rpm [done]
Installing: libcap1-1.10-10.1 [done]
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # rpm -iv
jack-0.116.1-16.jl.suse.x86_64.rpm
Preparing packages for installation...
file /usr/lib64/libjackserver.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjackserver2-0-1.9.0-0.pm.4
file /usr/lib64/libjack.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjack2-0-1.9.0-0.pm.4
file /usr/bin/jack_freewheel from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_load from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_transport from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_unload from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jackd from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/inprocess.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_alsa.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_dummy.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_net.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/alsa_in from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/alsa_out from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_freewheel from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_load from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_netsource from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_transport from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_unload from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jackd from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/inprocess.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/intime.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_alsa.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_dummy.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_net.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_oss.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jack
Reading installed packages...
The following packages are going to be downgraded:
lash jaaa hydrogen gstreamer-0_10-plugins-bad-lang
gstreamer-0_10-plugins-bad
The following packages are going to be REMOVED:
tuneit tap-reverbed soundtank snd-ls san-dysth rtsynth rezound
qtractor qsampler
qjacklam python-lash phasex perl-Audio-Ardour-Control mx44 lash-devel klick
kde4-kdenlive jconv jamin jacktube jackmixdesk-gui jackmixdesk jackmix
jackmeter
jackmaster jackbeat jack_snapshot jack_mixer jack_capture jackEQ jack2
jack-rack jack
guitarix gmidimonitor gigedit-linuxsampler-plugin fmit mhwaveedit
linuxsampler
ecasound ecamegapedal dssi-calf didgeridoo calf bristol-debugsource
bristol-debuginfo
bristol audicle ardour2 alsa-patch-bay LiVES
The following packages are going to change vendor:
lash jaaa hydrogen gstreamer-0_10-plugins-bad-lang
gstreamer-0_10-plugins-bad
Overall download size: 3.5 M. After the operation, 91.1 M will be freed.
Continue? [YES/no]: n
------------------------------------------------------------------------
------------------------------------------------------------------------
SECOND TRY
PACKMAN DISABLED & jack & libcap1 REMOVED BY YAST2
suse11:/usr/src/packages/RPMS/x86_64 # zypper install libcap1
Reading installed packages...
The following NEW package is going to be installed:
libcap1
Overall download size: 8.0 K. After the operation, additional 16.0 K
will be used.
Continue? [YES/no]: y
Downloading package libcap1-1.10-10.1.x86_64 (1/1), 8.0 K (16.0 K unpacked)
Downloading: libcap1-1.10-10.1.x86_64.rpm [done]
Installing: libcap1-1.10-10.1 [done]
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # rpm -iv
jack-0.116.1-16.jl.suse.x86_64.rpm
Preparing packages for installation...
file /usr/lib64/libjackserver.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjackserver2-0-1.9.0-0.pm.4
file /usr/lib64/libjack.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjack2-0-1.9.0-0.pm.4
file /usr/bin/jack_freewheel from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_load from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_transport from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_unload from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jackd from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/inprocess.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_alsa.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_dummy.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_net.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
------------------------------------------------------------------------
------------------------------------------------------------------------
HOW DO I HAVE TO USE ldconfig?
suse11:/usr/src/packages/RPMS/x86_64 # ldconfig
suse11:/usr/src/packages/RPMS/x86_64 # ldconfig --help
Usage: ldconfig [OPTION...]
Configure Dynamic Linker Run Time Bindings.
-c, --format=FORMAT Format to use: new, old or compat (default)
-C CACHE Use CACHE as cache file
-f CONF Use CONF as configuration file
-i, --ignore-aux-cache Ignore auxiliary cache file
-l Manually link individual libraries.
-n Only process directories specified on the
command
line. Don't build cache.
-N Don't build cache
-p, --print-cache Print cache
-r ROOT Change to and use ROOT as root directory
-v, --verbose Generate verbose messages
-X Don't generate links
-?, --help Give this help list
--usage Give a short usage message
-V, --version Print program version
Mandatory or optional arguments to long options are also mandatory or
optional
for any corresponding short options.
------------------------------------------------------------------------
------------------------------------------------------------------------
REMOVING THE STUDIO IN THE BOX, EXCEPTED qjackctl THAT IS A NON-RPM
INSTALL, BY REMOVING jack BY zypper
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jack
Reading installed packages...
'jack' is not installed.
Nothing to do.
suse11:/usr/src/packages/RPMS/x86_64 # zypper install jack
Reading installed packages...
Nothing to do.
------------------------------------------------------------------------
AFTER I INSTALLED jack BY YAST2 FROM THE REPO-OSS
suse11:/usr/src/packages/RPMS/x86_64 # jackd --help
jackd: error while loading shared libraries: libjack.so.0: cannot open
shared object file: No such file or directory
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jackd
Reading installed packages...
'jackd' not found.
Nothing to do.
suse11:/usr/src/packages/RPMS/x86_64 # ldconfig
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jackd
Reading installed packages...
'jackd' not found.
Nothing to do.
Toni wrote:
> you need rpm -e --nodeps <packagename> perhaps additionally the
> option --allmatches if packages are installed twice.
>
> than a package is removed and you have a temporary inconsitent system, but if
> you install immediately the other packages all will be fine :)
>
Thank you :)
as I have written, I made a quick test, when I was tired. I bet this is
written in the man page too?!
Cheers,
Ralf
Hi :)
I'm searching the following headers by http://www.rpmseek.com/index.html:
#include <iostream>
#include <fstream>
#include <cerrno>
Does anybody know where I can find them for Suse 11.1 RC? RPM Seek now
is searching for more than 200 seconds ;).
I wish to have a howto on German, to make a audio workstation for Suse
11.1, that's why I started a thread for the release candidate on
English, but I failed with doing this.
I can't build a kernel for Suse, I once patched without trouble for 64
Studio 2.1.
Any help at
http://forums.opensuse.org/pre-release-beta/401422-enable-realtime-audio-mi…
is welcome.
Cheers,
Ralf
Sorry to the lists, please ignore this mail, it's a test if my mails
come through the list.
@ Oc2pus:
That's strange. I'm member at jack-dev list. I haven't written to
Packman, because of the troubles we had at Linux-Club.
Maybe mirroring failed for the server I have jackd from. I can't change
to Suse right now. If you can write me were the script is, with the
information for the YaST2 and zypper servers, I can take a look from my
Lenny and than we should first diff if the package is equal to that of
another server.
The only other thing I can imagine is, that VideoLAN might cause a
conflict, even if YaST2 says that the dependencies aren't inconsistent.
-------- Original Message --------
Subject: Re: [LAD] [Jack-Devel] JACK for openSUSE 11.0 x86_64
Date: Mon, 15 Dec 2008 18:52:14 +0100
From: oc2pus(a)arcor.de
To: Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
References: <494681DB.6030804(a)alice-dsl.net>
<200812151757.17264.oc2pus(a)arcor.de> <49469359.9070308(a)alice-dsl.net>
Am Montag, 15. Dezember 2008 schrieb:
> oc2pus(a)arcor.de wrote:
> > you can't do it this way ...
> >
> > If you still have problems to install the packman packages, post your
> > problems to our mailing list and or cc me (I've packaged those packages
> > for packman) http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>
> Why, you always ignored what I was writing. You can read all messages
> here in the LAD mailing list archive.
Simple reason: because I won't subscribe to all available mailing-lists for
every package I maintain ...
and the jack-devel list answers me for every post:
Your mail to 'Jack-Devel' with the subject
Re: [LAD] [Jack-Devel] JACK for openSUSE 11.0 x86_64
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a members-only list
And I can't remember to ignore postings on the packman mailing-list. We try to
do our best and need the feedback and the reporting of problems and a error
is fixed as quick as possible.
> Cheers,
> Ralf
have fun
oc2pus
Hi :)
I have this problem too: http://ardour.org/node/2271
If I go back to the Suse 11.0 version before 0.116, it's 0.109, the
message changes from "jackd: symbol lookup error: jackd: undefined
symbol: clock_source" to "jackd: symbol lookup error: jackd: undefined
symbol: _jack_get_microseconds".
I tried to write with the German community (at Linux-Club Suse and
Packman community) about such issues, but they aren't interested in
their bugs and because they laugh about me, I'm not interested anymore
to report anything to them. Everything I tried to inform about, should
be wrong they say and laugh and there were a lot of bugs similar to that
one, for audio and MIDI realtime applications from the standard
repositories Oss, Non-Oss, Updates, Packman and VideoLAN. Also there are
often versions that aren't good for professional work.
I removed the jack package by YaST2 and then ...
suse11:/usr/lib # rm libjack*
suse11:/usr/lib64 # rm libjack*
After I installed jack again, I got "jackd: error while loading shared
libraries: libjackserver.so.0: cannot open shared object file: No such
file or directory".
Does anybody know a Suse community that is interested to solve those things?
I'm fine with the Debian 64 Studio audio community. Isn't there such a
friendly community for Suse (not JAD)?
For some reasons I like to use Debian 64 Studio and Suse, but Suse often
is a pain in the arse, because of a narrow views having community.
Do I need to compile jack myself for Suse 11.0? Before I upgraded jack,
I don't get any error messages.
Cheers,
Ralf
Hi all,
After quite some time spent doing nothing, a lot of polishing from Nedko, a
lot of suggestions from Kfoltman, and absolutely no effort from me to make
things go faster... I am very proud to announce the first release candidate
of LADITools 1.0 code name "flabbergasting-mademoiselle-sitting-on-my-hat"
(yeah... I bought a new hat for those who wonder)
LADITools is a set of tools aiming to achieve the goals of the LADI project
(http://nedko.arnaudov.name/wiki/moin.cgi/LADI) to improve desktop
integration and user work-flow of Linux audio system based on JACK and
LASH. Those tools take advantage of the DBus interfaces recently added to
JACK and LASH to ease the configuration and use of those two great
softwares.
Ok, sounds good... but what does it really do ?
LADITools is a software suite containing various utilities to make your
life a little easier when working with JACK and LASH clients.
You will find in this suite :
* The laditools python module (no interest for the end users)
* laditray : a system tray icon that allows you to start, stop and
monitor JACK, as well as start some JACK related apps (log viewer,
connections...)
* wmladi : a controller as a Window Maker dockapp. Uses the same menu
as laditray
* ladilog : a JACK, LASH and a2jmidid log viewer
* ladiconf : a GUI to setup JACK's configuration
* g15ladi : a JACK monitor for g15 keyboards
You can download it from the LADITools homepage here :
http://www.marcochapeau.org/software/laditools. Some updated screenshots
will be made available soon. As far as docs and bug reporting are
concerned, you'll have to come and ask on #LAD or #jack about it :)
My thanks go to Nedko Arnaudov who is the brain hidden behind this plan to
take over the world using DBus interfaces, Krzysztof Foltman who tests,
suggests and code a lot more than I do, a lot of people from IRC who also
made suggestions and contributions for the past year, and of course, the
whole set of JACK/LASH developers who accepted to have a DBus control
interface get into their repo :)
Cheers,
-- Marc-Olivier Barre --
--- MarcO'Chapeau ----
- www.marcochapeau.org -
Hi,
The FFADO team is proud to announce the first release candidate for
FFADO 2.0.
This release candidate is intended to collect feedback about the library
under wide-spread usage. The code should be free of major bugs.
We are looking for packagers that are interested in creating packages
for their favorite distribution. Please contact us if you can help us
out with this.
Release and download information:
http://www.ffado.org/?q=release/rc1
Currently, the installation options are:
* manual build from source
[http://www.ffado.org/?q=release/rc1]
* semi-automatic build from source into a 'sandbox'
[http://subversion.ffado.org/wiki/SandboxInstalls]
* APT repository for Ubuntu Gutsy and Hardy (possibly others)
[http://www.ffado.org/?q=release/apt]
Please test and report issues at our TRAC at http://subversion.ffado.org/
or at the mailing list (ffado-devel(a)lists.sourceforge.net). Please take
note of http://subversion.ffado.org/wiki/WritingGoodTickets when
reporting bugs.
We ask all users of FreeBoB that are not yet testing FFADO to try this
release candidate. Note that FFADO can co-exist with FreeBoB without any
problems, so you can revert back to your original setup very easily.
Enjoy,
Pieter Palmers
ffado.org
Hey there,
I have a Java app that can output Midi and I want to be able to access softsynths on a Linux system. Is there already a project out there that does such a thing? Would it be best to interface with Ladspa or Jack?
Any info would be greaty appreciated!
Richard
>
> Wasn't that a very long time ago, like pre jre 1.5?
>
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4356787
>
>
Not sure about it, I never tried to interface a softsynth from Java in
Linux, but I compiled one of the examples at jsresources and got this:
http://www.jsresources.org/examples/MidiPlayer.html
$ java -version
java version "1.5.0_10"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode)
$ java MidiPlayer -l
Available MIDI OUT Devices:
0 Real Time Sequencer
1 Java Sound Synthesizer
but...
$ pmidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
128:0 AlsaModularSynth ams
So at first glance I got the impression that interfacing alsaseq from
a vanilla JVM is not exactly trivial. Again, didn't look too deep into
it, so I may easily have missed something.
L
hi,
A semester has gone by, since last release, with no big news on this
front. Alas, on the verge of the coming one-dot-oh release of the mighty
JACK Audio Connection Kit, here goes one fine update of its old and aged
Qt GUI front-end:
QjackCtl 0.3.4 is out!
Nothing much new to see but you might welcome the patchbay snapshot
revamp, which might finally do the right thing, and the rand new
translations that are getting in place: German (de), Spanish(es), French
(fr) and Russian (ru). Many thanks to all involved.
With no further ado, the good stuff is ready from the usual places.
Website:
http://qjackctl.sourceforge.net
Project page:
http://sourceforge.net/projects/qjackctl
Download:
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.4.tar.gz
Weblog:
http://www.rncbc.org
License:
QjackCtl is free, open-source software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.
Change-log:
0.3.4 2008-12-05 Patchbay snapshot revamp.
- Introducing the very first and complete translations in-package:
German (de), Spanish (es), French (fr) and Russian (ru); credits in
TRANSLATORS.
- At last, after years of retarded procrastination, the old infamous
patchbay snapshot feature has been the subject of a almost complete
rewrite and it does try to give a way better mapping of all actual and
current running client/port connections, both JACK (audio, MIDI) and
ALSA MIDI, of course ;)
- On Setup/Settings/Parameters dialog, all device selection options are
now reset to default when disabled interactively.
- Grayed/disabled palette color group fix for dark color themes.
- Qt Software logo update.
- Fait-divers: desktop menu file touched to openSUSE conventions.
- ALSA PCM devices now only listed/enumerated iif strictly compliant
with the audio mode criteria (Duplex, Capture-only or Playback-only) as
kindly suggested by Nedko Ardaunov.
- JACK client/port aliases may now be displayed as a global user option
(see Setup/Display/Connections/JACK client/port aliases).
- Lighten up the connections line and highlight colors, as seen to fit
best on some darker background themes.
- Patchbay snapshot fixed to differentiate socket clients according to
its type (Audio, MIDI or ALSA-Seq), avoiding the mess and gross mistake
of hanging disparate type ports under the same client item.
- JACK_DEFAULT_SERVER environment variable is now appended to the X11
unique application identifier, allowing for having multiple instances
each controlling its own JACK server, besides the default one.
- Due to some trouble with newer Qt >= 4.4 applications regarding font
size configuration, a new global user option is now available to the
rescue: Setup/Misc/Defaults/Base font size (default is no-op).
Cheers && Enjoy.
--
rncbc aka Rui Nuno Capela
rncbc at rncbc dot org
