> ----- Original Message -----
> From: Diego Simak
>
> Thank you very much.
> Please confirm if it was fixed to dev branch, because it seems that it was
> included in the v.014.96 branch which has other error (jack_port_type_id_t)
>
> I've manually edited timekeeping.c from 0.14.97-dev with your fix and now
> it compiles OK, but I'm getting a Segmentation fault during execution:
>
> diego@ruidosa:~$ phasex
>
> (<unknown>:7002): Gtk-WARNING **: Unable to locate theme engine in
> module_path: "nodoka",
>
> (<unknown>:7002): Gtk-WARNING **: Unable to locate theme engine in
> module_path: "nodoka",
> Segmentation fault
> diego@ruidosa:~$
>
>
> Let me know any file that I can provide you.
>
> Thank you very much.
> Diego
This looks like the same nodoka warnings and segfault Dave Phillips was
seeing. Â Git branch v0.14.97-dev contains all the new fixes. Â v0.14.97
should be out by the end of the week.
Cheers,
--ww
> ----- Original Message -----
> From: Adrian Knoth
>
> On Tue, Jan 08, 2013 at 02:06:46PM -0200, Diego Simak wrote:
>
> > I'm using v.0.14.97-dev branch now but I got this error:
> >
> > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/alsa -pthread
> > -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
> > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> > -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
> > -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1
> > -I/usr/include/freetype2 -I/usr/include/directfb
> > -I/usr/include/libpng12 -I/usr/include/lash-1.0 -I/usr/include/alsa
> > -I/usr/include/uuid -D_GNU_SOURCE -D_XOPEN_SOURCE=600 -D_REENTRANT
> > -DARCH_BITS=64 -DPHASEX_CPU_POWER=2 -DNUM_PARTS=2 -std=gnu99 -pipe -Wall
> > -mtune=native -march=native -m64 -O3 -ffast-math -fomit-frame-pointer
> > -fsingle-precision-constant -MT timekeeping.o -MD -MP -MF
> > .deps/timekeeping.Tpo -c -o timekeeping.o timekeeping.c
> > timekeeping.c:60: error: ‘CLOCK_MONOTONIC_RAW’ undeclared here (not in a
> > function)
>
> A classic. ;) Fixed now:
>
> Â https://github.com/adiknoth/phasex
>
>
> Pull request sent, so I guess it will eventually end up in William's
> repo, too.
Thanks Adrian,
This is now in git v0.14.97-dev. Â The jack_bufsize crash you reported
on github is also fixed. Â These seem to be the last of the build/crash
issues with v0.14.96, so now I can concentrate on getting v0.14.97 out
by the end of the week.
Cheers,
--ww
> ----- Original Message -----
> From: Jeremy Jongepier
>
> On 12/30/2012 10:53 PM, William Weston wrote:
> >> ----- Original Message -----
> >> From: Jeremy Jongepier
> >> So this means starting multiple instances has become unnecessary?
> >
> > Correct. Multi-instance worked, but it was a pain. Currently, number
> > of voices is set at compile time, so be sure to run configure with
> > --enable-parts=4, or however may parts you want to use. More than two
> > parts per CPU core is not currently recommended, however.
> >
>
> So 4 parts is 2 parts per CPU? Or doesn't it work that way?
On a dual-core, this would be true. Â Eventually I would like to make
this a runtime configuration, but there's some other work that should
really happen first (CPU affinity, cgroup support, detecting number
of cores/CPUs, etc.). Â I'm looking at getting this in sometime during
the v0.15.x development cycle.
> [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
Happy New Year!
Yes, your eyes are working correctly. Â This is v0.14.96. Â Some things
are worth the wait. Â I know it's been a while, but I haven't forgotton
about PHASEX... just had to put it on the back burner for some time
while life moves on. Â After more troubles than I'd like to go into
detail about with the old server, old hosting arrangement, the old
bug-ridden codebase, old laptop, and life in general, I've come back
to "finish" what I've started (as if software projects ever "finish"
these days...). Â Over the past eleven months, I've taken the time to
overhaul most aspects of the PHASEX source code. Â After two failed
attempts at going multitimbral, and two mishaps with the laptop dev
tree and was supposed to be v0.12.0, I decided to bump the version
twice, start the new development with v0.14.x, and move on. Â Here's
the short list of what's new since v0.12.x:
New Features:
- Multitimbral (1 thread per part).
- Session bank (very much like the patch bank).
- Jack Session.
- Stereo- and Multi- outputs for JACK.
- ALSA PCM audio.
- JACK MIDI.
- ALSA Raw MIDI.
- Generic MIDI (/dev/midi support).
- MIDI clock for timestamping and queuing events.
- Active Sensing.
- New oscillator waveforms.
- Portamento for Osc Transpose events.
- FM oscillator latching.
- New LFO parameters.
- Moog (24db/octave) filter.
- Fast fade-out mono retriggering.
- Interpolated oscillator table lookups.
- Ability to run with no GUI.
- JACK MIDI / ALSA Raw / ALSA Seq connections in menus.
- Widescreen layout mode.
- New preferences dialog w/ nearly all settings.
- New knobs.
- Pure 64-bit math in builds with --enable-cpu-power=4.
New Features from Anton Kormakov:
- LASH.
- MIDI Hold pedal.
- JACK Transport.
Bugs Removed and/or Squashed:
- The "bad PHASEX noise" is gone.
- GUI widget sensitivity is fixed.
- Notebook tabs behave properly (and quickly).
- Patch loading bugs are gone.
- MIDI program change works dependably.
- Spurious envelope triggering pops are gone.
- Offsets for neg. filter env. now calculated properly.
- Chopped portamento slides are fixed.
- Keytriggering for all keymodes is fixed.
- Voice stealing works as expected.
- Chorus phase balance issues have been corrected.
- System lockup on shutdown is a thing of the past.
- Denormals don't eat up all the CPU anymore.
Code Overhaul:
- Build system overhaul.
- Reorganization of source code.
- Rebuilt data structures for multimbral architecture.
- New driver layer (engine relies on no libraries).
- Replaced pthreads based buffer synchronization code.
- New lightweight patch parser / patch format.
- New thread-safe MIDI event queue.
- Restructured engine, GUI, and MIDI code.
- Almost complete separation of GUI and engine.
 (still need to separate bank changes from the GUI.)
Sources are available via git:
    git clone https://github.com/williamweston/phasex.git
Number of parts is configurable at compile time (1-2 parts per core
should be very dependable. Â Tested extensively with 8 parts on a
quad-core.) Â As usual, YMMV:
   aclocal && autoconf && automake && autoheader
   ./configure --enable-arch=native --enable-parts=2
Overall, I am pleased with where PHASEX has arrived. Â In the past, I
had always been disappointed with PHASEX and its shortcomings, and for
many reasons. Â Until now. Â The code is cleaner and easier to work on.
Most of the old bugs have been replaced with more intelligent design.
On an -rt kernel, xruns are a thing of the past. Â Sound quality is
cleaner. Â GUI is much more responsive. Â Dependence on the command line
is kept to a bare minimum. Â Sessions can be managed with ease. Â Per
part memory and CPU utilization has decreased vs. multi-instance
v0.12.x. Â Timing is almost as good as it gets (sample accurate for
JACK MIDI, near sample accurate for ALSA seq, and almost as good as
your hardware will allow for ALSA raw MIDI.) Â All or the major
barriers to use that I've identified over the years have been
eliminated. Â I can actually sit down and work on some of those tracks
that got shelved due to bad timing. Â Of all the new features and code,
I am most pleased with the new MIDI clock. Â (Anyone interested in
timing of MIDI events and successive audio buffer processing cycles
can enable timing debug with '-d timing'. Â Once I finish putting all
my notes together, a detailed explanation of the MIDI clock will
follow.) Â The rest of the new features should be self-explanatory to
readers of linux-audio-dev, so I'll spare the details (unless of
course anyone asks).
Many thanks go out to Anton Kormakov for his work on PHASEX and his
git repo, which appear to have served the community well in the time
since the old server went down. Â And of course, I'd like to thank the
regular posters to this list (and linux-rt-users) for sharing the
knowledge that's made this release possible. Â A lot of you have
dropped some hints over the years about what the design of PHASEX (or
any synth) really needs to perform well (or at least to not perform
badly). Â I've been listening, as a lot of the work this year is a
result of finally getting around to a lot of the suggestions made by
members of linux-audio-dev.
So please, enjoy the new PHASEX. Â This release aims to be as bug-free
as possible (and IMHO, v0.14.96 is already more stable and
trouble-free than any previous version). Â As is usual with GPL'ed
software, there's no warranty whatsoever and I'm not responsible if
you blow out your speakers (or your hearing), but please don't let
that hold you back from trying it out.
This version is fully tested with Fedora 17 and 18, and should be just
as trouble free on any Fedora >= 14 or CentOS >= 6.0. Â At some point
next month, I'll be rebuilding my RAID and dedicating some space to
running other distributions. Â Until then, a request goes out for build
reports from other distros, especially Debian/Ubuntu, Arch, and Mint.
There's still time to get build files from other distros into the git
tree before v0.15.0 comes out.
So what do we do, now that the world didn't end?
Let's make some music!
Cheers,
--William Weston
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 ;)
