Re: [LAD] Announcing PHASEX-0.14.96

2013-01-21 Thread William Weston
> - Original Message - > From: Johannes Kroll > > On Thu, 17 Jan 2013 12:10:20 +0100 > Johannes Kroll wrote: > > > But I'm pretty sure that syncing Phasex to an external MIDI clock > > worked before, now it doesn't. I'm sending MIDI Clock from Renoise to > > Phasex. I checked that the po

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-21 Thread William Weston
> - Original Message - > From: Johannes Kroll > On Thu, 10 Jan 2013 22:26:15 -0500 > "William Weston" wrote: > > > > - Original Message - > > > From: Johannes Kroll > > > > > > I played around with it, it's fun! GUI looks very cool, too. > > > > > > After using it a few times,

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-17 Thread Johannes Kroll
On Thu, 17 Jan 2013 12:10:20 +0100 Johannes Kroll wrote: > > These files and directories are created when a session is saved via > > LASH, JACK Session, or native session management.  I've seen this > > behavior once before, when first working on LASH support, and it > > turned out to be a charac

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-17 Thread Johannes Kroll
On Thu, 17 Jan 2013 12:10:20 +0100 Johannes Kroll wrote: > But I'm pretty sure that syncing Phasex to an external MIDI clock > worked before, now it doesn't. I'm sending MIDI Clock from Renoise to > Phasex. I checked that the ports are connected and the clock is sent > with qjackctl & aseqdump. I

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-17 Thread Johannes Kroll
On Thu, 10 Jan 2013 22:26:15 -0500 "William Weston" wrote: > > - Original Message - > > From: Johannes Kroll > > > > I played around with it, it's fun! GUI looks very cool, too. > > > > After using it a few times, I noticed that some folders with strange > > names had been created with

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-10 Thread William Weston
> - Original Message - > From: Johannes Kroll > > I played around with it, it's fun! GUI looks very cool, too. > > After using it a few times, I noticed that some folders with strange > names had been created with files like patchbank, phasex.cfg, > phasex.map, sessionbank in them. The fo

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-10 Thread Diego Simak
2013/1/9 William Weston > > - 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 edit

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-09 Thread William Weston
> - 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

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-09 Thread William Weston
> - 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

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-09 Thread Jeremy Jongepier
On 01/06/2013 05:37 PM, Jeremy Jongepier wrote: 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

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-09 Thread Johannes Kroll
I played around with it, it's fun! GUI looks very cool, too. After using it a few times, I noticed that some folders with strange names had been created with files like patchbank, phasex.cfg, phasex.map, sessionbank in them. The folder names contain weird characters, Thunar file manager displays t

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-09 Thread Dave Phillips
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 us

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-08 Thread William Weston
> - Original Message - > From: Paul Davis > > On Sun, Jan 6, 2013 at 6:57 PM, William Weston 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? > > > >

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-08 Thread Diego Simak
2013/1/8 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

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-08 Thread 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/cair

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-08 Thread Diego Simak
2013/1/6 William Weston > > - 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 ty

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-08 Thread Dave Phillips
Greetings, Posted to LAU (the wrong list) : Hi William, 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 in

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-07 Thread Patrick Shirkey
Hi, svn compiled fine for me with Debian wheezy and the "experimental" repo. I can see you have put a lot of time and effort into the UI. I am missing an output meter and some example patches. I played around with the UI for a little while but couldn't get any sound out of it so not sure what I

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-07 Thread Lieven Moors
On Sun, Jan 06, 2013 at 05:44:25PM -0500, William Weston wrote: > > - 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

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-06 Thread Paul Davis
On Sun, Jan 6, 2013 at 6:57 PM, William Weston 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 fai

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-06 Thread William Weston
> - 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 d

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-06 Thread William Weston
> - 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]:

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-06 Thread 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:

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-06 Thread Lieven Moors
On Sat, Jan 05, 2013 at 08:40:25PM -0500, William Weston wrote: > > - 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 b

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-05 Thread William Weston
> - 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.

Re: [LAD] Announcing PHASEX-0.14.96

2013-01-05 Thread William Weston
> - Original Message - > From: Diego Simak > > 2012/12/30 Geoff Beasley > > > On 12/31/2012 08:53 AM, William Weston wrote: > > > >> I have a source package ready for Ubuntu 12.04 but I can't build it yet > >>> >because of the current issues with Jack1. I could try building against > >>>

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-31 Thread 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 configur

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-31 Thread Diego Simak
2012/12/30 Geoff Beasley > On 12/31/2012 08:53 AM, William Weston wrote: > >> I have a source package ready for Ubuntu 12.04 but I can't build it yet >>> >because of the current issues with Jack1. I could try building against >>> >Jack2 but then I can't test it myself because I don't use Jack2. >

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread Geoff Beasley
On 12/31/2012 08:53 AM, William Weston wrote: I have a source package ready for Ubuntu 12.04 but I can't build it yet >because of the current issues with Jack1. I could try building against >Jack2 but then I can't test it myself because I don't use Jack2. Try v0.14.97-dev in git: Still fails h

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread William Weston
> - Original Message - > From: Jeremy Jongepier > > On 12/30/2012 05:42 AM, William Weston wrote: > > 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... > > > > Great! Congrats w

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread Florian Paul Schmidt
On 12/30/2012 05:58 PM, SxDx wrote: same error here. auto[conf|make] is not my thing, so I don't know how to fix it. The following seems to do the trick. Don't know if it's the correct solution though. diff --git a/src/Makefile.am b/src/Makefile.am index 2bd2cbd..c4c740e 100644 --- a/src/Makefi

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread SxDx
> same error here. auto[conf|make] is not my thing, > so I don't know how to fix it. The following seems to do the trick. Don't know if it's the correct solution though. diff --git a/src/Makefile.am b/src/Makefile.am index 2bd2cbd..c4c740e 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -52

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread SxDx
> From: "Florian Paul Schmidt" > >> git clone https://github.com/williamweston/phasex.git > http://pastesite.com/86896 same error here. auto[conf|make] is not my thing, so I don't know how to fix it. (People, put the -l things AFTER the *.o in your gcc lines. The linker will skip unrefer

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread Jeremy Jongepier
On 12/30/2012 05:42 AM, William Weston wrote: 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... Great! Congrats with this new release! New Features: - Multitimbral (1 thread per part).

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-30 Thread Florian Paul Schmidt
On 12/30/2012 11:38 AM, Florian Paul Schmidt wrote: On 12/30/2012 05:42 AM, William Weston wrote: Happy New Year! To you, too :D Sources are available via git: git clone https://github.com/williamweston/phasex.git Sadly the build fails. After installing all dependencies indica

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-29 Thread William Weston
> - Original Message - > From: Jörn Nettingsmeier > > On 12/30/2012 05:42 AM, William Weston wrote: > > 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...

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-29 Thread William Weston
> - Original Message - > From: Robin Gareus > > It compiles cleanly and works just fine on debian. > > There's single compiler warning, nothing major, really: > > midi_event.c: In function ‘queue_midi_event’: > midi_event.c:140:47: warning: pointer targets in passing argument 1 of > ‘g_a

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-29 Thread Jörn Nettingsmeier
On 12/30/2012 05:42 AM, William Weston wrote: 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... whoohooo! just a quick feedback: distros that are moving to a unified /us

Re: [LAD] Announcing PHASEX-0.14.96

2012-12-29 Thread Robin Gareus
On 12/30/2012 05:42 AM, William Weston wrote: > Happy New Year! > > Yes, your eyes are working correctly. This is v0.14.96. Some things > are worth the wait. Certainly! Congratulations on this release. It rocks! I'm far from getting to the bottom of the rabbit hole, but playing around with ph

[LAD] Announcing PHASEX-0.14.96

2012-12-29 Thread William Weston
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