music April 2010

music@lists.fedoraproject.org

7 participants
20 discussions

Re: [Fedora Update] [old_testing] rakarrack-0.2.0-5.fc8 / fc9
by Development discussions related to Fedora 27 Jan '26

27 Jan '26

updates(a)fedoraproject.org wrote: > The update for rakarrack-0.2.0-5.fc8 has been in 'testing' status for over 2 weeks. .. > ================================================================================ > rakarrack-0.2.0-5.fc8 > ================================================================================ > Update ID: FEDORA-2008-9033 > Release: Fedora 8 > Status: testing > Type: newpackage > Karma: 0 > Bugs: 455953 - Review Request: rakarrack - Audio effects processing rack > : for guitar > Notes: Initial build of rakarrack for fedora > Submitter: dtimms > Submitted: 2008-10-20 21:46:29 > Comments: dtimms - 2008-10-20 21:46:32 (karma 0) > This update has been submitted for testing > bodhi - 2008-10-23 16:35:19 (karma 0) > This update has been pushed to testing > > http://admin.fedoraproject.org/updates/F8/FEDORA-2008-9033 Hi fedora-music lovers, I would be keen for some feedback on whether rakarrack that is now in fedora testing works for you ? To fully test you'll need a guitar and pickup plugged into your soundcard, but even a go/nogo on whether it starts would be helpful. Where I developed the package, it works OK, but another older AMD machine, it fails during startup. This will help me to decide whether to push it to the F8,F9 updates repos. DaveT.

6 11

whysynth doesn't work
by Florin Andrei 07 Jan '26

07 Jan '26

I got whysynth-dssi-20060122-7.src.rpm from here: http://people.redhat.com/green/FE/devel/ I rebuilt it on FC6 without problems. The thing is, the GUI doesn't show up. The program appears to be working, I see the outputs being automatically routed in qjackctl, but there's no GUI anywhere! ############################################### $ jack-dssi-host whysynth.so jack-dssi-host: Warning: DSSI path not set jack-dssi-host: Defaulting to "/usr/local/lib/dssi:/usr/lib/dssi:/home/florin/.dssi" jack-dssi-host: OSC URL is: osc.udp://rivendell.home.local:15040/dssi/whysynth/WhySynth/chan00 host: Ready WhySynth_gtk starting (pid 4305)... ############################################### -- Florin Andrei http://florin.myip.org/

6 16

qxgedit-0.1.0-2.rncbc.suse112.x86_64.rpm on Fedora12
by Niels Mayer 13 May '10

13 May '10

http://lalists.stanford.edu/laa/2010/04/0017.html > Remember that piece of junk that I rig on every desktop which still has some PCI card slots anyway? If you don't, I'll tell you once more: the Yamaha DB50XG piggyback. I know it's not easy find those nowadays, but there's always that auction sites for you to try. Moreover the hosting sound-cards which exposes a Creatine Labs Waveblaster daughter-board expansion port, are no easier too. Ah, the good old nineties... > Never mind, so here it goes again: > QXGEdit 0.1.0 has fallen from the attic Note these binaries probably work on Fedora too: http://downloads.sourceforge.net/qxgedit/qxgedit-0.1.0-2.rncbc.suse112.i586… http://downloads.sourceforge.net/qxgedit/qxgedit-0.1.0-2.rncbc.suse112.x86_… The latter "worksforme" in Fedora 12: > sudo rpm -ivh qxgedit-0.1.0-2.rncbc.suse112.x86_64.rpm Preparing... ########################################### > [100%] 1:qxgedit ########################################### > [100%] This synth is a daughterboard card for http://en.wikipedia.org/wiki/Creative_Wave_Blaster ... Well reviewed ... http://www.soundonsound.com/sos/1996_articles/may96/yamahadb50xg.html and still available http://cgi.ebay.com/Yamaha-DB50XG-DB60XG-Sound-Daughter-Board-SW1000XG-/200… . This program looks nice enough that I almost want to find one of these cards and daughterboard for sale cheap on ebay. I wish I had patch editors on linux that look as nice as qxgedit. Niels http://nielsmayer.com PS: Anybody know whether this can control other Yamaha GM chips -- like the one in my Suzuki Q-Chord or Yamaha DD-55?? I did a quick test and although the lights on the midi box flashed, the sound didn't change any. That's why I tested this out in the first place.

2 4

Python problem building AudioLab on Fedora
by Niels Mayer 30 Apr '10

30 Apr '10

I tried http://sourceforge.net/projects/soundviewer/ but got stuck trying to install its main dependency, a python libsndfile wrapper http://www.ar.media.kyoto-u.ac.jp/members/david/softwares/audiolab/ :: Any suggestions or help on this one? For all I know, even though I've got 67 Fedora python packages installed, this error might be happening from the one package i'm missing. ............................... I'm attempting to follow the instructions at http://www.ar.media.kyoto-u.ac.jp/members/david/softwares/audiolab/sphinx/i… on Fedora 12 (2.6.32.11-99.fc12.x86_64) with numpy-1.3.0-7.fc12.x86_64 and python-2.6.2-4.fc12.x86_64 installed as standard RPM packages. Unfortunately, I get this error: > gnulem-109-~/scikits.audiolab-0.10.2> python -v setup.py install > ... > # /usr/lib64/python2.6/collections.pyc matches /usr/lib64/python2.6/collections.py > import collections # precompiled from /usr/lib64/python2.6/collections.pyc > dlopen("/usr/lib64/python2.6/lib-dynload/_collectionsmodule.so", 2); > import _collections # dynamically loaded from /usr/lib64/python2.6/lib-dynload/_collectionsmodule.so > # /usr/lib64/python2.6/keyword.pyc matches /usr/lib64/python2.6/keyword.py > import keyword # precompiled from /usr/lib64/python2.6/keyword.pyc > # /usr/lib64/python2.6/site-packages/numpy/ma/extras.pyc matches /usr/lib64/python2.6/site-packages/numpy/ma/extras.py > import numpy.ma.extras # precompiled from /usr/lib64/python2.6/site-packages/numpy/ma/extras.pyc > # /usr/lib64/python2.6/site-packages/numpy/setup.pyc matches /usr/lib64/python2.6/site-packages/numpy/setup.py > import numpy.setup # precompiled from /usr/lib64/python2.6/site-packages/numpy/setup.pyc > # /home/npm/scikits.audiolab-0.10.2/common.pyc matches /home/npm/scikits.audiolab-0.10.2/common.py > import common # precompiled from /home/npm/scikits.audiolab-0.10.2/common.pyc > Traceback (most recent call last): > File "setup.py", line 84, in <module> > classifiers=CLASSIFIERS) > TypeError: 'module' object is not callable > .... Where line 84 is the main call in setup.py: > setup(configuration=configuration, > name=DISTNAME, > install_requires=INSTALL_REQUIRE, > namespace_packages=['scikits'], > packages=setuptools.find_packages(), > include_package_data = True, > test_suite="tester", > zip_safe=False, > classifiers=CLASSIFIERS) Any suggestions on what I'm doing wrong? ----------------------- Niels http://nielsmayer.com

1 1

Re: [Fedora-music-list] [mididings] Building mididings on Fedora 12
by Niels Mayer 29 Apr '10

29 Apr '10

Dominic -- Thanks for the suggestion, it got rid of all the errors and warnings. Here's the result of "starting from scratch". (next step: figure out how to turn off "-g" for GCC) gnulem-8-~> tar xzf ~/Download/mididings-20100413.tar.gz gnulem-10-~/mididings-20100413> diff setup.py.~1~ setup.py 48c48 < for libdir in ('/usr/lib', '/usr/local/lib'): --- > for libdir in ('/usr/lib64', '/usr/local/lib64'): gnulem-11-~/mididings-20100413> ./setup.py build running build running build_py creating build creating build/lib.linux-x86_64-2.6 creating build/lib.linux-x86_64-2.6/mididings copying mididings/event.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/setup.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/constants.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/engine.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/util.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/patch.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/misc.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/scene.py -> build/lib.linux-x86_64-2.6/mididings copying mididings/__init__.py -> build/lib.linux-x86_64-2.6/mididings creating build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/engine.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/filters.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/base.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/call.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/init.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/generators.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/modifiers.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/__init__.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/splits.py -> > build/lib.linux-x86_64-2.6/mididings/units copying mididings/units/printing.py -> > build/lib.linux-x86_64-2.6/mididings/units creating build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/harmonizer.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/memorize_scene.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/voices.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/dbus.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/pedal_noteoff.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/key_color.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/osc.py -> build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/inotify.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/floating_split.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/gm.py -> build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/polyphony.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/latch.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/suppress_pc.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/per_channel.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/__init__.py -> > build/lib.linux-x86_64-2.6/mididings/extra copying mididings/extra/panic.py -> > build/lib.linux-x86_64-2.6/mididings/extra creating build/lib.linux-x86_64-2.6/mididings/live copying mididings/live/livedings.py -> > build/lib.linux-x86_64-2.6/mididings/live copying mididings/live/__init__.py -> > build/lib.linux-x86_64-2.6/mididings/live copying mididings/live/widgets.py -> > build/lib.linux-x86_64-2.6/mididings/live copying mididings/live/osc_control.py -> > build/lib.linux-x86_64-2.6/mididings/live running build_ext building '_mididings' extension creating build/temp.linux-x86_64-2.6 creating build/temp.linux-x86_64-2.6/src gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/backend.cc -o build/temp.linux-x86_64-2.6/src/backend.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/engine.cc -o build/temp.linux-x86_64-2.6/src/engine.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/patch.cc -o build/temp.linux-x86_64-2.6/src/patch.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/python_caller.cc -o build/temp.linux-x86_64-2.6/src/python_caller.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/python_module.cc -o build/temp.linux-x86_64-2.6/src/python_module.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/backend_alsa.cc -o build/temp.linux-x86_64-2.6/src/backend_alsa.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/backend_jack.cc -o build/temp.linux-x86_64-2.6/src/backend_jack.o g++ -pthread -shared build/temp.linux-x86_64-2.6/src/backend.o > build/temp.linux-x86_64-2.6/src/engine.o > build/temp.linux-x86_64-2.6/src/patch.o > build/temp.linux-x86_64-2.6/src/python_caller.o > build/temp.linux-x86_64-2.6/src/python_module.o > build/temp.linux-x86_64-2.6/src/backend_alsa.o > build/temp.linux-x86_64-2.6/src/backend_jack.o -L/usr/lib64 -lglib-2.0 > -lboost_python -lboost_thread-mt -lasound -ljack -lpython2.6 -o > build/lib.linux-x86_64-2.6/_mididings.so running build_scripts creating build/scripts-2.6 copying and adjusting scripts/mididings -> build/scripts-2.6 copying and adjusting scripts/livedings -> build/scripts-2.6 changing mode of build/scripts-2.6/mididings from 644 to 755 changing mode of build/scripts-2.6/livedings from 644 to 755 gnulem-12-~/mididings-20100413> sudo ./setup.py install running install running build running build_py running build_ext running build_scripts running install_lib copying build/lib.linux-x86_64-2.6/_mididings.so -> > /usr/lib64/python2.6/site-packages running install_scripts copying build/scripts-2.6/mididings -> /usr/bin copying build/scripts-2.6/livedings -> /usr/bin changing mode of /usr/bin/mididings to 755 changing mode of /usr/bin/livedings to 755 running install_egg_info Removing > /usr/lib64/python2.6/site-packages/mididings-20100413-py2.6.egg-info Writing /usr/lib64/python2.6/site-packages/mididings-20100413-py2.6.egg-info Niels http://nielsmayer.com

2 1

Re: [Fedora-music-list] [PlanetCCRMA] Attempt at using Suse CLAM rpm's on Fedora (was Re: [CLAM] bad link to download in 1.4 announcement // any 1.4 RPMs??)
by Simon Lewis 29 Apr '10

29 Apr '10

Hi Niels libCLAM (core) will build on Fc12 with 64bit libs - the problem is the plug-ins or better said scons. To build the plug-ins sconstruct checks to see if libCLAM is present in the root and/or build root. Unfortunately scons looks in the lib and not the lib64 directories, even though the pkg_config_path is set correctly. This has something to do with the automation in scons... Simon + for i in Filters GuitarEffects MIDI resampling samplebysample sndfile spacialization speech osc + pushd plugins/Filters ~/rpmbuild/BUILD/CLAM-1.4.0/plugins/Filters ~/rpmbuild/BUILD/CLAM-1.4.0 + export PKG_CONFIG_PATH=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/lib64/pkgconfig + PKG_CONFIG_PATH=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/lib64/pkgconfig + scons clam_prefix=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr prefix=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr scons: Reading SConscript files ... Package clam_core was not found in the pkg-config search path. Perhaps you should add the directory containing `clam_core.pc' to the PKG_CONFIG_PATH environment variable No package 'clam_core' found OSError: 'PKG_CONFIG_PATH=/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/lib/pkgconfig pkg-config clam_core --libs --cflags' exited 1: File "/home/simon/rpmbuild/BUILD/CLAM-1.4.0/plugins/Filters/SConstruct", line 36: env.EnableClamModules(clamDependencies, CLAMInstallDir) File "/usr/lib/scons/SCons/Environment.py", line 217: return apply(self.method, nargs, kwargs) File "/home/simon/rpmbuild/BUILDROOT/libclam_core1_4-1.4.0-2.sl.fc12.x86_64/usr/share/clam/sconstools/clam.py", line 166: ' '.join(libs))) File "/usr/lib/scons/SCons/Environment.py", line 1447: return function(self, self.backtick(command)) File "/usr/lib/scons/SCons/Environment.py", line 585: raise OSError("'%s' exited %d" % (command, status)) Am 28.04.2010 03:18, schrieb michael noble: > Niels, > > On Wed, Apr 28, 2010 at 1:26 AM, Niels Mayer <nielsmayer(a)gmail.com > <mailto:nielsmayer@gmail.com>> wrote: > > On Mon, Apr 26, 2010 at 5:57 PM, michael noble <looplog(a)gmail.com > <mailto:looplog@gmail.com>> wrote: > > If you search Packman the 1.4 rpms are there. Or just use this > link: > http://packman.links2linux.de/search?scope=name&q=clam > <http://packman.links2linux.de/search?scope=name&q=clam> > > > Thanks for making these available. Any chance x86_64 RPMs can be > built? > > > These are not my handiwork, and I wouldn't want to steal credit for them! > > Toni Graffy is the packager, as stated at Packman. He is subscribed to > clam-devel, not sure if he is on the users list. > > As to x86_64, I believe that problem came up before and there was some > show-stopper that made packaging everything impossible, so Toni chose > to drop 64 bit. You'd have to take it up with him, though. > > Regarding the rest, I'm afraid I can't offer much help... > > -m > > > _______________________________________________ > PlanetCCRMA mailing list > PlanetCCRMA(a)ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma >

1 0

Building mididings on Fedora 12
by Niels Mayer 28 Apr '10

28 Apr '10

Following the installation instructions at http://das.nasophon.de/mididings/ I've built and installed mididings on Fedora 12 (2.6.32.11-99.fc12.x86_64) with python-2.6.2-4.fc12.x86_64. I had to make one small change in setup.py to get it to build and install successfully. I have not tested it yet, however. (1) Installed the following RPMs to get setup.py to stop complaining of missing packages, and files: pyliblo-0.8.1-1.fc12.x86_64, dbus-devel-1.2.16-9.fc12.x86_64, dbus-python-devel-0.83.0-6.fc12.x86_64, python-inotify-0.8.8-1.fc12.noarch, python-inotify-examples-0.8.8-1.fc12.noarch, tcl-8.5.7-5.fc12.x86_64, tk-8.5.7-3.fc12.x86_64, tix-8.4.3-4.fc12.x86_64, tkinter-2.6.2-4.fc12.x86_64, glib2-devel-2.22.5-1.fc12.x86_64,alsa-lib-devel-1.0.22-2.fc12.x86_64,jack-audio-connection-kit-devel-1.9.4-1.fc12.ccrma.x86_64, python-devel-2.6.2-4.fc12.x86_64, boost-devel-1.39.0-9.fc12.x86_64 (2) Building: gets an error "/usr/bin/ld: cannot find -lboost_thread" even though boost-thread-1.39.0-9.fc12.x86_64 installed. gnulem-57-~/mididings-20100413> ./setup.py build running build running build_py running build_ext building '_mididings' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/backend.cc -o build/temp.linux-x86_64-2.6/src/backend.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/engine.cc -o build/temp.linux-x86_64-2.6/src/engine.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/patch.cc -o build/temp.linux-x86_64-2.6/src/patch.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/python_caller.cc -o build/temp.linux-x86_64-2.6/src/python_caller.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/python_module.cc -o build/temp.linux-x86_64-2.6/src/python_module.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/backend_alsa.cc -o build/temp.linux-x86_64-2.6/src/backend_alsa.o gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC > -DENABLE_ALSA_SEQ=1 -DENABLE_JACK_MIDI=1 -Isrc -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include/alsa -I/usr/include/python2.6 > -c src/backend_jack.cc -o build/temp.linux-x86_64-2.6/src/backend_jack.o g++ -pthread -shared build/temp.linux-x86_64-2.6/src/backend.o > build/temp.linux-x86_64-2.6/src/engine.o > build/temp.linux-x86_64-2.6/src/patch.o > build/temp.linux-x86_64-2.6/src/python_caller.o > build/temp.linux-x86_64-2.6/src/python_module.o > build/temp.linux-x86_64-2.6/src/backend_alsa.o > build/temp.linux-x86_64-2.6/src/backend_jack.o -L/usr/lib64 -lglib-2.0 > -lboost_python -lboost_thread -lasound -ljack -lpython2.6 -o > build/lib.linux-x86_64-2.6/_mididings.so /usr/bin/ld: cannot find -lboost_thread collect2: ld returned 1 exit status error: command 'g++' failed with exit status 1 (3) Fixed Setup.py to link the library from boost-thread RPM: gnulem-72-~/mididings-20100413> diff -c setup.py.~1~ setup.py *** setup.py.~1~ 2010-04-12 18:33:14.000000000 -0700 --- setup.py 2010-04-27 19:23:53.515386499 -0700 *************** *** 71,77 **** pkgconfig('glib-2.0') libraries.append(boost_lib_name('boost_python')) ! libraries.append(boost_lib_name('boost_thread')) #include_dirs.append('/opt/boost1.42-py3/include') #library_dirs.append('/opt/boost1.42-py3/lib') --- 71,77 ---- pkgconfig('glib-2.0') libraries.append(boost_lib_name('boost_python')) ! libraries.append(boost_lib_name('boost_thread-mt')) #include_dirs.append('/opt/boost1.42-py3/include') #library_dirs.append('/opt/boost1.42-py3/lib') (4) Sucess: gnulem-70-~/mididings-20100413> ./setup.py build running build running build_py running build_ext building '_mididings' extension g++ -pthread -shared build/temp.linux-x86_64-2.6/src/backend.o > build/temp.linux-x86_64-2.6/src/engine.o > build/temp.linux-x86_64-2.6/src/patch.o > build/temp.linux-x86_64-2.6/src/python_caller.o > build/temp.linux-x86_64-2.6/src/python_module.o > build/temp.linux-x86_64-2.6/src/backend_alsa.o > build/temp.linux-x86_64-2.6/src/backend_jack.o -L/usr/lib64 -lglib-2.0 > -lboost_python -lboost_thread-mt -lasound -ljack -lpython2.6 -o > build/lib.linux-x86_64-2.6/_mididings.so running build_scripts creating build/scripts-2.6 copying and adjusting scripts/mididings -> build/scripts-2.6 copying and adjusting scripts/livedings -> build/scripts-2.6 changing mode of build/scripts-2.6/mididings from 644 to 755 changing mode of build/scripts-2.6/livedings from 644 to 755 gnulem-73-~/mididings-20100413> sudo ./setup.py install running install running build running build_py running build_ext running build_scripts running install_lib creating /usr/lib64/python2.6/site-packages/mididings [...] byte-compiling /usr/lib64/python2.6/site-packages/mididings/live/widgets.py > to widgets.pyc byte-compiling > /usr/lib64/python2.6/site-packages/mididings/live/osc_control.py to > osc_control.pyc running install_scripts copying build/scripts-2.6/mididings -> /usr/bin copying build/scripts-2.6/livedings -> /usr/bin changing mode of /usr/bin/mididings to 755 changing mode of /usr/bin/livedings to 755 running install_egg_info Writing /usr/lib64/python2.6/site-packages/mididings-20100413-py2.6.egg-info Niels http://nielsmayer.com

1 0

CLAM on CCRMA or Fedora please??
by Niels Mayer 28 Apr '10

28 Apr '10

I noticed that CLAM stopped being supported by PlanetCCRMA around F8 timeframe. It looks like a lot of new and cool stuff is available. Any interest in getting this added? http://clam-project.org/ CLAM 1.4.0, 3D molluscs in the space > The CLAM project is delighted to announce the long awaited 1.4.0 release > of CLAM, the C++ framework for audio and music, code name 3D molluscs in the > space. > In summary, this long term release includes a lot of new spacialization > modules for 3D audio; MIDI, OSC and guitar effectsmodules; architectural > enhancements such as typed controls; nice usability features for the > NetworkEditor interface; convenience tools and scripts to make CLAM > experience better; enhanced building of LADSPA plugins and new support > for LV2 and VST plugin building; a new easy to use application to explore > songs chords called Chordata; many optimizations, bug fixing and code clean > ups. It looks great and easy to use: http://clam-project.org/wiki/Development_screenshots See also: <http://clam-project.org/wiki/Development_screenshots> http://vokicodder.blogspot.com/2007/04/educational-vowel-synth-and.html http://vokicodder.blogspot.com/2007/04/realtime-mfcc-and-lpc-analysis.html http://vokicodder.blogspot.com/2007/04/realtime-voice-gender-change.html http://vokicodder.blogspot.com/2009/04/vst-plugins-with-qt-user-interface.h… ... CLAM allows to visually build JACK and PortAudio based applications with > Qt interfaces as well as GUI-less VST and LADSPA plugins. The more flashy > feature of VST is user interfaces that are mostly built using VSTGUI. We are > using Qt as interface for JACK and Portaudio based apps because we are using > the nice features of Qt toolkit to dynamically bind the UI elements and the > underlaying processing. Moreover, Qt styling features enables shinning > designer-made interfaces. Why not being able to reuse the same interface for > VST and JACK? That has been a long standing TODO in CLAM so now is time to > address it. > In summary, we fully solved croscompiling vst's from linux and we even > started using qt interfaces as vst gui. In that last point, there still is a > lot of work to do, but the basic question on whether you can use qt to edit > a vst plugin is now out of any doubt. > To make the spike simpler, and in order not to collide with other CLAM > developers, currently working on it, i just left apart all the CLAM wrapping > part, just addressing vst crosscompiling and Qt with the sdk examples. > Cross compilation was pretty easy. This time I found lot more documentation > on mingw and even scons. Just by adding the crossmingw scons tool we are > already using for the apps and i managed to get Linux cross-compiled plugins > running on Wine. Niels http://nielsmayer.com

2 2

Attempt at using Suse CLAM rpm's on Fedora (was Re: [CLAM] bad link to download in 1.4 announcement // any 1.4 RPMs??)
by Niels Mayer 27 Apr '10

27 Apr '10

On Mon, Apr 26, 2010 at 5:57 PM, michael noble <looplog(a)gmail.com> wrote: > If you search Packman the 1.4 rpms are there. Or just use this link: > http://packman.links2linux.de/search?scope=name&q=clam Thanks for making these available. Any chance x86_64 RPMs can be built? I tried installing these openSUSE 11.2 i586 RPMs on Fedora 12 and it didn't work out too well: http://nielsmayer.com/clam1.4-suserpm-on-fedora-FAIL.txt (will need to try again as 1.5 rpm's just got uploaded). Although you can bring all the programs up -- and they look beautiful -- loading a file in the filebrowser widget, or trying to play a sound gives an error. Normally this kind of "hack" works better -- this time, there seems to be some fundamental Gtk mismatch. Of course, normally, the hack of using a different distros RPM works fine when staying within the x86_64 arch. This time I had to install a bunch of 32 bit i686 libs as dependencies to make it work.... Independent of this I'm getting a ladspa-rubberband warning as I had earlier compiled my own version of a number of libs for my own project ( http://nielsmayer.com/trainspodder-prototype.jpg ), and there's some interaction with some lib->lib64 symlink hackage I did to make some other build work. However, I do not think that's what's causing the problem here. My hunch is that the problem has more to do with a Gtk incompatibility: "QGtkStyle was unable to detect the current GTK+ theme." example: gnulem-126-~/Download> /usr/bin/Prototyper > /usr/share/networkeditor/example-data/spectralAndTonal.ui Error loading: /usr/local/lib/ladspa/ladspa-rubberband.so reason: > /usr/local/lib/ladspa/ladspa-rubberband.so: wrong ELF class: ELFCLASS64 [LADSPA Plugin] Warning: trying to open non ladspa plugin: > /usr/local/lib/ladspa/ladspa-rubberband.so Error loading: /usr/local/lib/ladspa/ladspa-rubberband.cat reason: > /usr/local/lib/ladspa/ladspa-rubberband.cat: invalid ELF header [LADSPA Plugin] Warning: trying to open non ladspa plugin: > /usr/local/lib/ladspa/ladspa-rubberband.cat QGtkStyle was unable to detect the current GTK+ theme. Jack: JackClient::SetupDriverSync driver sem in flush mode Jack: JackFifo::ConnectAux name = > /dev/shm/jack_fifo.571_default_spectralAndTonal Jack: Already connected name = spectralAndTonal Jack: Clock source : system clock via clock_gettime Jack: JackLibClient::Open name = spectralAndTonal refnum = 3 Backend 'jack' selected. > (process:19061): GLib-GObject-CRITICAL **: gtype.c:2458: initialization > assertion failed, use IA__g_type_init() prior to this function > (process:19061): GLib-CRITICAL **: g_once_init_leave: assertion > `initialization_value != 0' failed > (process:19061): GLib-GObject-CRITICAL **: gtype.c:2458: initialization > assertion failed, use IA__g_type_init() prior to this function > (process:19061): GLib-GObject-CRITICAL **: gtype.c:2458: initialization > assertion failed, use IA__g_type_init() prior to this function > (process:19061): GLib-GObject-CRITICAL **: gtype.c:2458: initialization > assertion failed, use IA__g_type_init() prior to this function > (process:19061): GLib-GObject-CRITICAL **: g_type_add_interface_static: > assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed > (process:19061): GLib-GObject-CRITICAL **: gtype.c:2458: initialization > assertion failed, use IA__g_type_init() prior to this function > (process:19061): GLib-GObject-CRITICAL **: g_type_add_interface_static: > assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed > (process:19061): Gtk-CRITICAL **: gtk_widget_style_get: assertion > `GTK_IS_WIDGET (widget)' failed Niels http://nielsmayer.com

1 0

Yamaha Motif XS, the remote control feature and Rosegarden
by David Sommerseth 23 Apr '10

23 Apr '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Have anyone of you tried make the remote control feature found in the Yamaha Motif XS synths work in Rosegarden? It works pretty nicely in Cubase, but I'm trying to avoid booting up Windows as much as possible when I want to play and have fun :) I'm also interested in trying out different ideas on how to make this work. My google searches have not led me closer to some clues yet. I would be willing to help getting Rosegarden to understand one of the remote control profiles the Motif XS provides. It supports Cubase, Sonar, Digital Performer and Logic according to the Owners Manual [1] (page 52) kind regards, David Sommerseth [1] <http://www.yamahasynth.com/downloads/manuals/synthesizers/motif_xs/english/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkvRaWwACgkQIIWEatLf4He0dACggcPf0WV+UKsGCDYipN8zOtK7 VFQAni1dc+QQxmBm1RCbaVSng8JBrqCh =U5/A -----END PGP SIGNATURE-----

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

music April 2010