Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7520 discussions

Sorry, just an information about the status quo of jack for Suse 11 from Packman

by Ralf Mardorf

Hi :) I'm double-sorry if a mail some minutes before came through the list, but while I take a look at my account on the homepage of my provider, there seems to be something wrong. I take a breather and will read any mails within the next days, but not today, I also can't reply to the old thread from were I'm writing now. I just want to inform, that I repaired Suse 11.0 for JACK, but that there still is a problem for other people. If someone will do a YaST2 update for all packages, if a newer version is available, than only libjack will be upgraded, but not jack and then their JACKs will be broken, so if people do an update and they have 1. JACK installed and 2. the Packman repository enabled, at the moment they need to take care about libjack, they need to manually keep libjack, or they should disable the Packman repository. Status quo of this was at around 19:50, then there was no 0.116 jack or jack2 available, but a libjack 0.116. Cheers, Ralf

17 years

Just a suggestion about how to handle bug reports

by Ralf Mardorf

I'm not banned for some mailing list and some of the recipients are very kind, but their lists are joined by people who maybe should pay attention to this. If you want people to report bugs, than - don't laugh about them and say that they are the only one with that problem and they should search the web before they do stupid bug reports. Be careful, sometimes the user might have more knowledge and you only think you're right. - you say they are right, but the bug isn't caused by your software, package-build, wiki, they should search the web and find out them self where they have to report bugs. Users might be stupid, but they won't report a bug for their office suit to ALSA and reporting a bug that has to do with an audio application, might be reported to ALSA, JACK, the kernel community, because they all have to do with such a bug - allow people to report without getting subscribed I'm suggesting this because I misbehaved, when I asked because of a bug. Now I'm banned for a forum and a mailing list, but they grant me, that I have pointed out something that was unknown. But I wasn't the one who pointed out this bug, the web was full of posts from other people, before I even noticed this bug. When they try to report something and been laughed at etc., they don't go on like I did, they won't be idiots like I'm. They won't be banned. A lot of people change over to windows, a lot of people report bugs and nobody cares about, a lot of people won't spend hours in reporting something, by reading rules how to do this, e.g. I was exhorted to write the German word "das" correctly, because there are rules, that this word sometimes must be written "dass" instead of "das". I often reported bugs to people who than said, they are making music too and that bug didn't exist, a year later it's noticed in a developer list and they have long threads about it and they wonder why nobody reported this before. People don't try to asked, because they have fear to asked in a wrong kind, the wrong questions. If you report a bug you often hear use this distro instead of this distro, if you don't like it, or use Windows instead of Linux, if you don't like it. But you do like a special distro, application etc. ... Things went terrible wrong in the community and it's not a borderline and dyslexic personality like me ... "normal" people have fear to use Linux, to ask the community. If anybody is interested in what I noticed about Linux audio and MIDI, which bugs I have myself etc., I will go on, because I will stay at Linux for nearly everything, but I guess I have to find something else for multimedia. Hints for alternatives to Linux are welcome. Don't worry, I won't write anything again if I'm unwanted. Good luck for multimedia Linux!

17 years

Re: [LAD] [64studio-users] Just a suggestion about how to handle bug reports

by Ralf Mardorf

Hi Gustin :) it's easy to get named a troll. What should a user do, that has troubles with JACK? I like the 64 Studio community, unfortunately the version for the 64 Studio 2.1 stable version is 0.103. It's silly if a user reports a bug about that version, while the JACK developers needs statements about 0.116. There are distros like Suse, that supports 0.116 by community packages, e.g. for Suse it's the Packman repository. I had contact to the packager by the Linux Club. People reported that bug e.g. to the Ardour forums, a long time before I had this bug. There they say, it's a JACK bug, but this isn't true, it was a packman bug. http://ardour.org/node/2271 I don't want to talk again about this, because I'm personal involved in this, maybe someone of those who replied off-list can give other examples, I won't quote private mails. Testing of RCs often is unwanted. I tried to make a howto and needed help and that was unwanted. And people don't report bugs to the right places, 1. because they don't know the right places and 2. because they know, that they will get bashed. When I reported the JACK package bug for Packman I get sarcasms. I was a troll, who made everything wrong, because I have no knowledge. Nobody but me should have this bug too, written by the packer, who asserted that he makes music with the packages from Packman. This must be a lie, because this package is broken for everyone. 1. If you like to help and write a howto, but you need some help because you e.g. don't know that compilers differ for several Linux, you need to add headers for some applications, than you do something that is unwanted. 2. If you report that something don't work, you need help, than you are a troll, because it's not true. I'm not the only one. Why can you find bugs in the web, that are not reported to the right people? I got mails off-list, with statements similar to "I recently got raked over the coals by ...". Which distribution can I use, that is wanted by the developers? How do I have to report bugs? When I say "Hello, there's a bug" I don't want the answer, that I'm a noob, nobody has this bug, while the whole community has got the same bug. I'm not the "Girl, interrupted" when I reported a bug and I'm not a individual case. I get crazed, when people are unconvincable, they don't need to excuse, while people like me get banned. The only thing users can do, is to report bugs anonymous, in forums somewhere in the web, instead of talking to the right people. Misspelling for a user who reports something should be allowed. Posting a bug that was posted before, should be allowed. Posting a bug of a front or back end to the back or front end people should be allowed. To be stupid should be allowed. But it isn't. Cheers, Ralf PS: I have a bad conscience because I wrote this troll like stuff. I also get off-list mails that this will break the work. But I guess it's a topic, if Linux is also for Users. I never developed anything for Linux, but I was a developer too. I don't understand the problem with bug reports. At the moment it looks like I'm not banned in much mailing lists, as it was written.

17 years

Re: [LAD] [Jack-Devel] JACK for openSUSE 11.0 x86_64

by Ralf Mardorf

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.

17 years

Re: [LAD] JACK for openSUSE 11.0 x86_64

by Ralf Mardorf

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

17 years

Problems with compiling

by Ralf Mardorf

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

17 years

Just a test

by Ralf Mardorf

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

17 years

JACK for openSUSE 11.0 x86_64

by Ralf Mardorf

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

17 years

[ANN] LADITools 1.0-rc1 released

by MarcO'Chapeau

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 -

17 years

[FFADO-devel] [ANN] FFADO 2.0 Release Candidate 1 (1.999.40) available

by Pieter Palmers

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

17 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev