On 01/09/2013 12:40 AM, William Weston wrote:
>> ----- Original Message -----
>> From: Dave Phillips
>>
>> Building the latest git pull for 0.14.97 on a completely updated Arch 64
>> system:
>>
>> [dlphilp@bigblack phasex]$ aclocal
>> configure.ac:695: error: 'AM_CONFIG_HEADER': this macro is obsolete.
>> You should use the 'AC_CONFIG_HEADERS' macro instead.
>> /usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded
>> from...
>> configure.ac:695: the top level
>> autom4te: /usr/bin/m4 failed with exit status: 1
>> aclocal: error: echo failed with exit status: 1
>>
>>
> Looks like AM_CONFIG_HEADER has been depracated for a while now, and
> automake-1.13 no longer allows it. In git v0.14.97-dev, this is now
> swapped out for AC_CONFIG_HEADERS.
I pulled the new stuff this morning, no problem with the configuration now.
> Also in git v0.14.97-dev, the nodoka specific bullet_color has been
> removed from the theme files (already set in gtkenginerc for nodoka),
> so the nodoka warning should go away now. The nodoka engine is only
> used for setting radiobutton colors, so you're not missing out on
> much if you don't have it.
Okay, thanks.
>
> Please try the latest v0.14.97-dev in git. If (after a make install)
> it segfaults, could you run it through gdb and let me know where it
> fails?
Done, with no segfault now. :)
First run was choppy until I lowered the polyphony to 4, no xruns since.
Got these messages on opening :
[dlphilp@bigblack ~]$ phasex
Not sending deprecated LASH_Client_Name event
LASH client initialized. (LASH_Client_Name='phasex').
Main: LASH client started.
(phasex:8585): Gtk-CRITICAL **: IA__gtk_check_menu_item_get_active:
assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
(phasex:8585): Gtk-CRITICAL **: IA__gtk_check_menu_item_set_active:
assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
Thanks for the great synth !
Best,
dp
> ----- Original Message -----
> From: Paul Davis
>
> On Sun, Jan 6, 2013 at 6:57 PM, William Weston <whw(a)linuxmail.org> wrote:
> >
> > Explicit checks for new JACK headers library calls have been added
> > to the autoconf system instead of relying on the weakjack linkage
> > alone. Could you try it again?
> >
>
> just a note: i haven't really publically explained the very sad failure of
> the weak linkage stuff.
>
> we incorrectly assumed that the linux gcc+ld stack had the same
> capabilities as their variants on OS X. OS X provides a *very nice* design
> for weak linkage that is incredibly useful for precisely this sort of thing.
>
> alas, it turned out that the work done on the apple variants was never
> back-ported into mainstream gcc+ld, and as a result, the weak linkage test
> approach that i (and a few others advocated) does not work on linux unless
> code is specially linked in a way that is not sensible to recommend for
> applications. basically, you can do weak linkage tests *between libraries*
> (or other code linked with -fPIC, but not between libraries and
> applications.
>
> this is very sad, and the alternative (an approach first implemented by
> native instruments, of all groups!) seems like the only way to handle this.
>
> --p
I'm not familiar with the native instruments approach. Â Would it be
helpful in this case?
--ww
> ----- Original Message -----
> From: Lieven Moors
>
> > > [snip]
> > >
> > > It doesn't build yet. Same errors some other people reported:
> > >
> > > In file included from engine.h:31:0,
> > > Â from alsa_pcm.c:43:
> > > jack.h:34:2: error: unknown type name 'jack_port_type_id_t'
> > > make[3]: *** [alsa_pcm.o] Error 1
> > > make[3]: Leaving directory `/tmp/buildd/phasex-0.14.97~git20121231/src'
> > > make[2]: *** [all-recursive] Error 1
> > > make[2]: Leaving directory `/tmp/buildd/phasex-0.14.97~git20121231'
> > > make[1]: *** [all] Error 2
> > > make[1]: Leaving directory `/tmp/buildd/phasex-0.14.97~git20121231'
> > >
> > > Regards,
> > >
> > > Jeremy
> >
> > Could you try the latest in the v0.14.97-dev branch? Â All of the
> > current JACK build fixes are included, and should compile cleanly
> > for jack >= 0.117.0.
> >
> >
> > Cheers,
> > --ww
>
> I having the same error, even in the -dev branch...
>
> Greets,
>
> lieven
Oops.... Forgot to push that last commit up to github. Â It's in there
now. Â Could you try again?
--ww
Hi all,
I'm not quite sure how to interpret this, but it sounds like
linuxaudio.org will be offline for a short time (failover period) coming
Saturday January 12th 8am EST.
-------- Original Message --------
Just wanted to make sure you were aware of the upcoming maintenance this
Saturday.
Maintenance for the central storage system known as minnow.cc.vt.edu is
schedule for Saturday, January 12 starting at 8am. Several hardware
components in the filer head needs to be replaced. Since this is a
cluster storage system, the maintenance will be performed in failover
mode, so minnow services will continue to be available. During the
failover, services will pause until the failover is complete.
Yet another music notation program to pollute the internet. It's still just a
baby, but it already implements at least a few bugs.
It's not really ready for general use yet. The user interface is still rather
lacking and there are way too few sanity checks, but it does read and write
native *.sqo files (an xml format), and supports a crude and low-quality export
to standard MIDI files. The Staff Editor can display standard notation and
tablature moderately well, and work is ongoing to produce better percussion
staff and chord staff display. Tracks can be nested. Staffs can be grouped. The
score format supports multiple simultaneous time signatures.
Currently, it's just for display and editing. There's no playback yet.
Website:
http://sourceforge.net/projects/sqorlatti
Download (bzipped source tarball):
http://downloads.sourceforge.net/sqorlatti/sqorlatti-0.1.0.tar.bz2
It's written in C++ and uses Qt4. There's no config or anything yet, just Qt
project file. So, as an ordinary user:
1. Create a Sqorlatti (or whatever you want to call it) directory somewhere.
2. Unpack to the directory.
3. CD to the directory.
4. qmake
5. make
6. Install the Sqorlatti.ttf font. It's located in the fonts subdirectory. In
KDE you can install it by going to System Settings and clicking through
Computer Administration / Font Installer / Personal Fonts / Add.
7. To run, type
./Sqorlatti examples/Air.sqo
This will open one of the examples. Due to a bug in the program (just found it
today!), you have to start the program with a file. Any *.sqo file in examples
will do. Once the program is running, you can open any other *.sqo file.
If you open Staff Editor and the staffs looks huge and filled with garbage
characters, you forgot to install the font.
UserManual.pdf provides a small amount of documentation on how to use the
program. It's not all that well developed yet.
Developer documentation can be generated using doxygen. Just type
doxygen
to generate html documentation in the doc directory. You can fiddle with
doxyfile if you want to generate documentation in other formats (e.g. latex).
--
7:8
>From: "Patrick Shirkey" <pshirkey(a)boosthardware.com>
>With his insistence that he is a godly person while also being so
>aggressive it seems he has a few issues to work out which could also be
>the cause of his obvious substance abuse. However it could be that he is
>just responding to his social environment. Maybe he is from a part of the
>world where they are intolerant towards homosexuals, believe strongly in
>God and are generally agressive towards anyone who does not agree with
>their view of the world.
>Not sure which part of the world that would be though. Anyone have any
ideas?
Afganistan....or Texas ;)
Hi,
GIT repo:
https://github.com/fps/ladspamm
DOXYGEN docs (very minimal):
http://fps.github.com/ladspamm
For my own small side projects I needed a little c++ wrapper lib around
LADSPA plugins. Since someone else might be interested in it, too, I put
it on github.
ladspamm::world world;
ladspamm::plugin_instance instance(
world.libraries[0]->plugins[0], 48000
);
instance.activate();
instantiates and activates the first found plugin in the first found
library..
This is version 0.0.1 so expect bugs and missing features..
Have fun,
Flo
--
Florian Paul Schmidt
http://fps.io
> ----- Original Message -----
> From: Jeremy Jongepier
>
> On 01/06/2013 02:40 AM, William Weston wrote:
> > Could you try the latest in the v0.14.97-dev branch? All of the
> > current JACK build fixes are included, and should compile cleanly
> > for jack >= 0.117.0.
>
> Hello William,
>
> It doesn't build just yet:
>
> jack.c: In function 'jack_audio_init':
> jack.c:1027:6: error: 'jack_set_port_rename_callback' undeclared (first
> use in this function)
> jack.c:1027:6: note: each undeclared identifier is reported only once
> for each function it appears in
> jack.c:1029:4: warning: implicit declaration of function
> 'jack_set_port_rename_callback' [-Wimplicit-function-declaration]
>
> Regards,
>
> Jeremy
Explicit checks for new JACK headers library calls have been added
to the autoconf system instead of relying on the weakjack linkage
alone. Â Could you try it again?
Cheers,
--ww
CAPS 0.9.3's guitar amplification contains four new tonestacks,
distortion asymmetry dependent on output power and other sound
improvements. The modulation of the mono chorus has been smoothened,
and the Plate default parameters have been restored to be nearer the
more reverberant response of the older versions.
http://quitte.de/dsp/caps.html
There's also a 0.4.6 release, stamped 'obsolete', containing all the
plugins that were in 0.4.5 but did not make the cut to 0.9. There are
no duplicate plugin IDs, and the library is differently named, so both
versions can co-exist on one system.
http://quitte.de/dsp/caps.html#Older_Versions