ProAudio repository for Arch users

funkmuscle · 2008-07-18 04:01:57

got lmms working the way you said to schivmeister... thanx.

btartsa · 2008-07-22 00:25:54

Schiv, I saw you cleaned up my sloppy packages on Ardour jackdmp and slv2-svn...thanks! I'm trying to contribute and I'm certainly not a programmer...so thanks for bearing with me.

Question: On jackmp-svn what is that PKGBUILD scheme you are using? I can't get it to build

$cd proaudio/jackmp-svn/
$makepkg
PKGBUILD: line 4: syntax error near unexpected token `<<<'

funkmuscle · 2008-07-22 00:50:00

btartsa, I had the same error while building Ardour, I deleted the PKGBUILD, downloaded it again and it worked. It still had the <<< in it.
What is jackmp? Is it a better version of jackd?

btartsa · 2008-07-22 03:14:06

jackmp is a fork of jack designed for smp machines. works nice on my dual p4 box.

schivmeister · 2008-07-22 05:50:00

Hey no problem, that's what a version control system is for Hmm not happening here..probably not a good thing to say so somebody else needs to confirm. Try what funkmuscle did..and do an svn stat before that to see if things were modified somehow - I don't know how the "<<<" got in there but I don't see that on my copies. Post the PKGBUILD here so we can try it out too.

pkgname=jackmp-svn
pkgver=2704
pkgrel=1
arch=(i686 x86_64)
license=('GPL')
url="http://www.grame.fr/~letz/jackdmp.html"
pkgdesc="JACK for SMP (multiprocessor) systems"
depends=('alsa-lib')
makedepends=('subversion')
conflicts=('jack-audio-connection-kit')
provides=('jack-audio-connection-kit')
#options=('!libtool')
source=()
md5sums=()

_svntrunk="http://subversion.jackaudio.org/jack/jack2/trunk/jackmp"
_svnmod="jackmp"

build() {
  cd "$srcdir"

  if [ -d $_svnmod/.svn ]; then
    (cd $_svnmod && svn up -r $pkgver)
  else
    svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod
  fi

  msg "SVN checkout done or server timeout"
  msg "Starting build..."

  cd $_svnmod

  ./waf configure  --prefix=/usr
  ./waf build $MAKEFLAGS || return 1
  ./waf --destdir="$pkgdir" install
}

Btw is it strange that I get worse performance when I use jackmp? Anything else to configure besides installing?

btartsa · 2008-07-22 20:06:40

The people over at #jack told me the options you see running waf --help are all there is.

Jackmp seems to hate hyperthreading...if that helps at all. Both jack-svn and jackmp-svn work nice on my dual P4 machine.

I'm going to package and test the experimental versions (pipelining and direct) maybe tonight...maybe those work better for you. They are available here:

http://www.grame.fr/~letz/jackdmp.html

Last edited by btartsa (2008-07-22 20:21:19)

funkmuscle · 2008-07-30 15:13:11

anybody uses rosegarden here? Since 1.7.0, I had issues with it. For one, the synths will load but I can't edit them. I can't load soundfonts in fluidsynth-dssi, etc.
Now, with KDE4 (I'm using kdemod-kde4), I get this failure message.:
rosegarden: error while loading shared libraries: libkdecore.so.4: cannot open shared object file: No such file or directory...
any help?

markc · 2008-07-30 18:10:40

@funkmuscle: I use the daily svn packages and my libkdecore is /usr/lib/libkdecore.so.5 so I'd say that missing libkdecore.so.4 is pickd up from KDE3 when Rosegaden was compiled. Isn't there a svn source proaudio package for Rosegarden ?

Anyone interested in putting together this?...

On Wed, Jul 30, 2008 at 12:21 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> We are pleased to announce the 2.6.26-rt1 tree, which can be
> downloaded from the location:
>   http://rt.et.redhat.com/download/
> Information on the RT patch can be found at:
>   http://rt.wiki.kernel.org/index.php/Main_Page
> The merge was mostly done by Steven Rostedt, I just fixed it up, added
> the fixes from .24-rt17 and tested it on x86 32/64bit.
> This is the first cut of .26-rt, so don't expect it to be perfect.
> I run out of time, so I dropped Peter's cpu-hotplug patches
> completely. The hotplug and rcupreempt code has changed radically, so
> we need to redo that lot. Peter, Paul can you please look into that ?
> I tried to address the non-x86 issues as far as I could, but I had no
> chance to compile test them. So please check the wreckage.
> to build a 2.6.26-rt1 tree, the following patches should be applied:
>
>   http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2
>   http://rt.et.redhat.com/download/patch-2.6.26-rt1.bz2

funkmuscle · 2008-07-30 18:53:14

nothing in proaudio markc. I don't thing anyone uses rosegarden there. yeah I did try the svn and this is the error:

cmake . -DCMAKE_INSTALL_PREFIX=`kde-config --prefix`
-- Found Qt3 (version 3.3.8)
-- Found KDE3 include dir: /opt/kde/include
-- Found KDE3 library dir: /opt/kde/lib
-- Found KDE3 dcopidl preprocessor: /opt/kde/bin/dcopidl
-- Found KDE3 dcopidl2cpp preprocessor: /opt/kde/bin/dcopidl2cpp
-- Found KDE3 kconfig_compiler preprocessor: /opt/kde/bin/kconfig_compiler
-- Program pkg-config found (/usr/bin/pkg-config)
-- Found LADSPA (/usr/include)
-- Program msgfmt found (/usr/bin/msgfmt)
-- KDE3HTMLDIR : share/doc/HTML
-- KDE3DATADIR : share/apps
-- KDE3ICONDIR : share/icons
-- KDE3MIMEDIR : share/mimelnk
-- KDE3MENUDIR : share/applications/kde
-- KDE3L18NDIR : share/locale
-- KDE3EXECDIR : bin
-- Program kde-config found (/opt/kde/bin/kde-config)
-- Program meinproc found (/opt/kde/bin/meinproc)
-- Rosegarden 1.7.1-svn will be built for install into /opt/kde
-- Configured to compile for release without debug information

Installation Summary
--------------------

Install Directory : /opt/kde
Build type : Release
Use Qt/KDE precompiled headers: FALSE

Xft notation font support : TRUE
No LIRC support configured.

ALSA MIDI support : TRUE
JACK audio support : TRUE
LADSPA plugin support : TRUE
DSSI synth plugin support : TRUE
Custom OSC plugin GUI support : TRUE
Audio timestretching : TRUE
LRDF plugin metadata support : TRUE

-- Configuring done
CMake Error: Unable to open check cache file for write. /home/harv/rosegarden/CMakeFiles/cmake.check_cache

btartsa · 2008-07-30 18:54:19

Hi Mark,
I built it (kernel-2.2.26-rt1) last night but have not tested it yet. I noticed a bunch of errors while compiling but it built and installed. I'll dig through the log when I get home.

Last edited by btartsa (2008-07-30 18:56:48)

schivmeister · 2008-07-31 15:08:16

I recall a similar problem on the net. It's something like a missing Qt lib for the installed KDE one, or it was mentioned that sudo may help if it's trying to make symlinks. I haven't installed kde4 but are the core libs still in /opt? It may be what markc mentioned; wrong paths. I would try it out and the redhat patch but my Arch system is hosed atm.

funkmuscle · 2008-07-31 16:35:15

I got it working with the help of 'funkyou' at kdemod.

add /opt/kde/lib to /etc/ld.so.conf

then run sudo ldconfig -v and reboot...

known bug in Archs kdelibs3, will be fixed...

Now rosegarden works but the dssi plugins have an issue still schivmeister. I think we spoke about this at the LinuxMusician's forum.
for instance, when I load fluidsynth-dssi in roegarden, it loads but I can't load soundfonts when I click on the editor which I could of done with earlier verions of rosegarden.
Also the same with dssi-vst, they load but the editor button doesn't load the editor. dssi-vst on its own works fine.

I'm lost with that one.

funkmuscle · 2008-08-03 15:43:37

Hey guys, I got a bug report that I sent to rosegarden people and someone there thinks it could be the distro.

here's the bug report and the reply to it:

----------- .xsession-errors ---------------------
21,0 - (Emu10k1 WaveTable, Emu10k1 Port 0) (WRITE ONLY) [ctype 2,
ptype 327710, cap 66]
21,1 - (Emu10k1 WaveTable, Emu10k1 Port 1) (WRITE ONLY) [ctype 2,
ptype 327710, cap 66]
21,2 - (Emu10k1 WaveTable, Emu10k1 Port 2) (WRITE ONLY) [ctype 2,
ptype 327710, cap 66]
21,3 - (Emu10k1 WaveTable, Emu10k1 Port 3) (WRITE ONLY) [ctype 2,
ptype 327710, cap 66]
RemoteVSTClient: all cache files are up-to-date, not running scanner
LADSPAPluginFactory::discoverPlugins - done
RemoteVSTClient: all cache files are up-to-date, not running scanner
PluginFactory::instance(dssi): creating new DSSIPluginFactory
LADSPAPluginFactory::discoverPlugins - discovering plugins; path is
[/usr/lib/dssi]
RemoteVSTClient: all cache files are up-to-date, not running scanner
LADSPAPluginFactory::discoverPlugins - done
AudioInstrumentMixer::setPlugin(10000, 999,
dssi:/usr/lib/dssi/fluidsynth-dssi.so:FluidSynth-DSSI)
fsd-gui starting (pid 3181)...
/usr/libexec/FluidSynth-DSSI_gtk: No such file or directory.
--------------------------------------------------

Followups:

Comments

Date: 2008-08-03 00:40
Sender: dmmcintyrProject AdminAccepting Donations
Logged In: YES
user_id=663564
Originator: NO

The key bit in all this seems to be:

/usr/libexec/FluidSynth-DSSI_gtk

That can't be right. I'm not sure how this varies by distro, but the
typical pattern for DSSI plugins is $PREFIX/dssi/$NAME_OF_SYNTH for the
location of the GUI engine for the plugin. For example, mine (on an Ubuntu
system) is at:

/usr/lib/dssi/fluidsynth-dssi/FluidSynth-DSSI_gtk

I'm not sure what is responsible for picking out this path. It might or
might not be our own code.

I'm reassigning this to Chris to encourage him to take a quick glance at
this for himself. Maybe he will jump to some quick conclusion about what
is most likely breaking down here.

cyberpatrol · 2008-08-05 00:47:22

Well, I haven't read the whole 19 pages of this thread, so please forgive me, if this question was already asked.

I've put this into my /etc/pacman.conf, when I've installed Archlinux for the first time some months ago:

[proaudio]
Server = http://arch.madfire.net/proaudio/i686

Since a long time this repository wasn't updated. Now I've found http://code.google.com/p/proaudio/ by chance, but there I can't find another server. There are two links to mirrors, but one of them doesn't exist and the other is the one, I have already in my pacman.conf.

Is this project still alive?
Have the mirrors changed?
Or was it really not updated for a long time?

Btw., a new version of alsa(-tools) is out.

btartsa · 2008-08-05 01:33:02

Your best bet is to join the googlecode group. It's community maintained and could use more contributers.

funkmuscle · 2008-08-05 01:42:49

and also do this to get all the packages PKGBUILD and build them:
svn checkout https://proaudio.googlecode.com/svn/trunk/ proaudio

markc · 2008-08-05 04:49:41

@cyberpatrol: one of those binary mirrors may have been an old link of mine so might I ask where you saw it so I can remove or update it?

FWIW I've got some space set up to start pushing binary builds again but I'm not sure how to handle any binary uploads by other folks. ATM I'm fairly well set up with a dedicated machine to build i686 and x86_64 packages and getting pretty close to starting on some proaudio packages again (I do the daily kde4 svn packages). Updating this particular binary repo is probably best managed by me just building the packages and uploading them myself, and perhaps set up a non-public ftp upload area if anyone else wants to contribute some packages... ie; the simplest way is for me to have a local proaudio binary repo and rsync that to the remote server so the db files are in sync... otherwise I have to come up with a bunch of remote server scripts to manage possible multiple contributions from other folks to make sure repo is in sync. One day but it's easier and immediately doable if I just manage a local repo and rsync it all up in one go (if all that makes sense).

If this could be useful then some idea of what packages to start with would help me get going... what's the most important first dozen packages that will be easiest to build ? (preferably from svn/cvs as I can build them on a daily basis if need be) FWIW the repo would be at http://pkg.eth-os.org/proaudio/, which could redirect to somewhere else but for now they would reside on the same server.

funkmuscle · 2008-08-05 12:42:13

markc, that great news. here are some packages...Hydrogen, Ardour, Rosegarden, Jack, lmms, kevny24......
dunno if they're easy to build but they seem to be the important ones for proaudio.

schivmeister · 2008-08-05 17:21:10

don't forget the kernel man! and if you can, please update it to 2.6.26. Since i haven't gotten my Arch Linux machine up yet the AUR one has been outdated for a few days already.

btw funkmuscle, that does look like a distro-specific problem. Check out the pkgbuild and after the build completes, check $srcdir for that file, or make sure that the library goes to /usr/lib in $pkgdir. The configuration appears to be using libexec instead.

Last edited by schivmeister (2008-08-05 17:25:50)

funkmuscle · 2008-08-05 17:51:44

thanx schivmeister and oh yeah, the kernel, how could I miss that!!??... That's the main package...

schivmeister wrote:

Check out the pkgbuild and after the build completes, check $srcdir for that file, or make sure that the library goes to /usr/lib in $pkgdir.

how do I edit the PKGBUILD to do that?

Last edited by funkmuscle (2008-08-05 18:14:33)

bangkok_manouel · 2008-08-08 06:37:11

Sincere apology for being completely off-topic here.

[OT]Anyone interested in this?[/OT]

Thanks.

markc · 2008-08-08 08:00:37

@bangkok_manouel: very interesting idea, I hope you get some contributions, and sure, this thread should have some likely candidates.

Along similar lines, anyone interested in contributing to a podcast ? It would only take some recorded skype sessions (or whatever voice chat system, skype works fine though) and a little bit of editing... topic(s) could be anything vaguely Arch related.

I've uploaded one lousy simple test package to my particular binary repo at http://pkg.eth-os.org/proaudio/i686 (and x86_64) just to make sure it works. I used my KDE daily "mpkg" script and it compiled and uploaded the files with a simple "mpkg midicomp" so I'm ready to start adding more packages... but it'll take me quite a while to get any decent content... and I'll be aiming for low hanging fruit (the easy ones) at first. However, once a package is set up to be regularly compiled it's mostly automatic so it's not like it's up to me to have to manually remember to do so in the future. My system really best suits packages under VCS control and ALSA + JACK are my main first targets, then ardour and rosegarden I guess (from svn), then whatever else is easiest after that. I'm somewhat lukewarm about putting (my) time into the real-time kernel because it's a lot of work for just a few extra millseconds of latency as I don't do any 8+ track recording... and... when I did burn quite some time chasing the low latency holy grail I found my general desktop performance really suffered. So, in a way, I'd rather use a standard kernel with good overall performance and be happy with 5ms to 10ms latency rather than try to get down below 2ms but have an obviously slowed down desktop, which makes actually using the applications a bit sluggish.

Anyone have thoughts/comments about the rt kernel performance in general ?

funkmuscle · 2008-08-08 10:58:15

Yeah, on that topic of rt kernel, how come Windows and Macs don't have issues with latency? Or if they did, what's the difference? They seem to not have proaudio issues. I don't use Mac or Windows but from my friends, they say they have no issues.
Also, I use the vanilla kernel for regular pc usage then switch to rt for recording.

funkmuscle · 2008-08-11 20:43:34

hey guys, on that rosegarden issue, could it be dssi that's the problem? I have the same problem using qtractor. I click the edit button for the plugins and nothing happens.
same read out I get as rosegarden:

6:39:57.846 Session closed.
16:39:57.848 New session: "Untitled1".
16:39:58.091 Session started.
16:39:59.636 Audio connections change.
16:39:59.642 MIDI connections change.
RemoteVSTClient: all cache files are up-to-date, not running scanner

RemoteVSTClient: all cache files are up-to-date, not running scanner

fsd-gui starting (pid 4045)...

this is what spat out from qtractor when I clicked the edit button.

funkmuscle · 2008-08-22 17:20:00

anyone uses fluidsynth here? If yes, how do you get pitch bends with it? I've been using tuxguitar connected to qsynth but the effects don't work.
I've installed tuxguitar-fluidsynth plugin and that works but now no jack connection and I can't record the audio output.
Any help?
By the way, is the thread still active as I haven't seen any activity or any replies lately.

Arch Linux

#451 2008-07-18 04:01:57

Re: ProAudio repository for Arch users

#452 2008-07-22 00:25:54

Re: ProAudio repository for Arch users

#453 2008-07-22 00:50:00

Re: ProAudio repository for Arch users

#454 2008-07-22 03:14:06

Re: ProAudio repository for Arch users

#455 2008-07-22 05:50:00

Re: ProAudio repository for Arch users

#456 2008-07-22 20:06:40

Re: ProAudio repository for Arch users

#457 2008-07-30 15:13:11

Re: ProAudio repository for Arch users

#458 2008-07-30 18:10:40

Re: ProAudio repository for Arch users

#459 2008-07-30 18:53:14

Re: ProAudio repository for Arch users

#460 2008-07-30 18:54:19

Re: ProAudio repository for Arch users

#461 2008-07-31 15:08:16

Re: ProAudio repository for Arch users

#462 2008-07-31 16:35:15

Re: ProAudio repository for Arch users

#463 2008-08-03 15:43:37

Re: ProAudio repository for Arch users

#464 2008-08-05 00:47:22

Re: ProAudio repository for Arch users

#465 2008-08-05 01:33:02

Re: ProAudio repository for Arch users

#466 2008-08-05 01:42:49

Re: ProAudio repository for Arch users

#467 2008-08-05 04:49:41

Re: ProAudio repository for Arch users

#468 2008-08-05 12:42:13

Re: ProAudio repository for Arch users

#469 2008-08-05 17:21:10

Re: ProAudio repository for Arch users

#470 2008-08-05 17:51:44

Re: ProAudio repository for Arch users

#471 2008-08-08 06:37:11

Re: ProAudio repository for Arch users

#472 2008-08-08 08:00:37

Re: ProAudio repository for Arch users

#473 2008-08-08 10:58:15

Re: ProAudio repository for Arch users

#474 2008-08-11 20:43:34

Re: ProAudio repository for Arch users

#475 2008-08-22 17:20:00

Re: ProAudio repository for Arch users

Board footer