On Friday 04 May 2007 05:42, William Weston wrote:
> On Thu, 3 May 2007, Nigel Henry wrote:
> > Well it looks superb. I've still to hear it, as I'm attempting to
> > initially build it on FC2, but am getting a problem with "make".
> >
> > What are the build requirements for Phasex? I don't want to waste a lot
> > of time trying to get it to build on FC2, if it's not possible.
>
> I wouldn't expect it to be possible on FC2. Not until I take the time to
> make the GTK code compile on older versions of GTK-2.x.
> Could you let me know how that FC5 and Debian builds go?
>
> Thanks,
> --ww
It builds ok on Debian Etch, using v0.10.1, but segfaults after a few seconds,
even without touching anything on the GUI. If I try to load a patch, or open
the file menu, it segfaults immediately. GTK version on Etch is libgtk2.0-0
installed 2.8.20-7. Output from starting Phasex on the CLI below.
Well it was going to be below. I ssh'd into Etch from FC2 so as to start
Phasex from FC2, and paste the output from the CLI before the segfault to
you.
Now this is really weird. I started Phasex from FC2, and the GUI opened in
FC2, and I'm waiting for it to segfault. A minute later, and it's still
running. So I play around with the file menu, load one of the patches, play a
bit, and I cannot get it to segfault.
Close it on FC2, and no problems showing on the CLI on FC2, as below.
djmons@debian:~$ phasex
Thank you for using PHASEX!
(C) 1999-2007 William Weston <weston(a)sysex.net>
Released under the GNU Public License, Ver. 2
djmons@debian:~$ exit
logout
Connection to 192.168.0.8 closed.
[djmons@localhost djmons]$
Why would it segfault when I run it from Debian Etch, but when I run it from
FC2, ssh'd into Etch, Phasex works perfectly? Anyway with a bit of file
creation, and ftp'ing the segfault errors from Etch to FC2, they *are* now
below.
I must say I love the arp's, and like this bit in your TODO.
"Create a programmable arpeggiator".
djmons@debian:~$ phasex
(<unknown>:10435): Gtk-CRITICAL **: gtk_style_finalize: assertion
d`style->attach_count == 0' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE
(style)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE
(style)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion
`GTK_IS_STYLE (style)' failed
Segmentation fault
djmons@debian:~$
Nice work William. Phasex sounds really nice. I'll post again with any
problems with the build on FC5.
Nigel.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
My spiffy new ASUS laptop that I thought was so great, is saddled with the dreaded Ricoh firewire chip (as well as having it on a shared interrupt with, well, *everything*).
Rather than throw good money after bad and buy an external FireWire card, I may be a smarter move to give up on FireWire and try USB instead. (And, no, it's too late to return the laptop. Which is what I knew would happen).
I do *not* need high-bandwidth, heavy-duty multichannel audio I/O. I don't record bands or live audio. Almost all my music is done inside the computer with softsynths. I will have stereo outs, and that's all that will used. Occasionaly I will plug in a guitar, so I'd need one (1) Hi-Z input. So a simple, cheap interface with two analog/SPDIF out and two analog ins, is really slightly more than I need.
I would, however, like as low latency as possible. I'm used to -n3 -p128 on firewire, so if I could find a USB interface that could handle that, I'd be totally happy.
The M-Audio Delta seems like the default answer. Any other recommendations?
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGO3qge8HF+6xeOIcRApZaAKDz6ChUj5Hat6PwghID+8QF7EvBZwCgju+n
4GeUxchZruE9UWCkLo1JVPo=
=5sec
-----END PGP SIGNATURE-----
Thanks for your comments Thorsten. They are again really constructive.
The laidback timing is too late at places, so the feeling
> becomes sloppy, nerving, imho.
Indeed. I need to work on the rythm. I was in fact trying to give the
drums a real feeling, by playing hydrogen from my keyboard. But, I'm out of
rythm in some places. Also, I'm not sure what you mean by 'laidback timing',
but what I think you mean is the first piano loop which has some blanks
which last too long (1 out of 4)?
The lead tries hard to be dramatic.
>
I don't understand. You mean that the guitar tries to be sad?
But this has quite some potential.
> I would straighten up the timing just a bit, shorten the
> track aiming at 4 minutes, make the lead sound clearly
> unlike a guitar and more smooth.
>
--
> Thorsten Wilms
>
> Thorwil's Design for Free Software:
> http://thorwil.wordpress.com
I think it could remain at 6 minutes if I add some variations. In fact the
whole thing is in 1 chord..I should add some chord variations, and not play
the guitar solo loop 2 times. 1 should be enough. I like the guitar sound. I
don't think I would change it. I agree on the point of straighten up the
timing as said before.
Julien.
http://www.archive.org/details/TheTimelessClock
On Friday 04 May 2007 05:42, William Weston wrote:
> On Thu, 3 May 2007, Nigel Henry wrote:
> > Well it looks superb. I've still to hear it, as I'm attempting to
> > initially build it on FC2, but am getting a problem with "make".
> >
> > What are the build requirements for Phasex? I don't want to waste a lot
> > of time trying to get it to build on FC2, if it's not possible.
>
> I wouldn't expect it to be possible on FC2. Not until I take the time to
> make the GTK code compile on older versions of GTK-2.x.
> Could you let me know how that FC5 and Debian builds go?
>
> Thanks,
> --ww
Update for the FC5 build on the same machine as Debian Etch (see previous
post)
Phasex builds ok on FC5. GTK version is 2.8.20-1, but again segfaults when
clicking on the file menu.
Again, if I ssh from FC2 into FC5, and run Phasex from FC2, there are no
problems. Closing Phasex from FC2 shows a segfault on closure. Running Phasex
from the CLI on FC5 gives this output.
[djmons@localhost ~]$ phasex
(<unknown>:19775): Gtk-CRITICAL **: gtk_style_finalize: assertion
`style->attach_count == 0' failed
Segmentation fault
[djmons@localhost ~]$
Weird how I can ssh into the other machine from FC2, whether it's running
Debian Etch, or FC5, and Phasex runs with no problems, but segfaults when I
start it from the machine that it's installed on.
Nigel.
Hi all,
Here a song I made yesterday night.
It is the last song (Interstellar vacuum) on :
http://www.archive.org/details/TheTimelessClock
Comments are of course welcome.
Enjoy!
p.s : of course, all made with linux :-) (Freewheeling, Qynth/piano
soundfont, ZynAdd and Hydrogen)
Julien.
hellew. i made this song as part of a quixit (
http://r2h.org/doc/quixit-faq.txt). it's where ppl from em411.com get
together in irc and make a tune in an hour, hour and a half...
link: http://r2h.org/music/everamzah-to_my_ear.mp3
using only the samples provided in the quixit (think one hour compo), i
proceeded to slice them up in snd. i loaded the pieces of the drum break
into one instance of specimen, and pieces of the flute and airy pad in
another instance of specimen. i then programmed an 8 bar drum loop in seq24,
alongside an 8 bar loop of a melody i made using the flute+pad. i recorded
both of these into ardour2 (rc2, worked like a charm), alongside with sample
tweak-out using kluppe. after that i adjusted the arrangement a touch, and
fired up tranches (controlled using vkeybd), routed the recorded drums into
tranches from and back into ardour2, and did beat repeating/slicing from
half way though in-on-out. i'm pleased with the end result. all made in
approx one hour. :)
thanks for listening,
james
--
r2h.org
Apologies for cross-posting.
This is generally a nice conference (and an opportunity to visit Brazil).
Sao Paulo is a great city to visit.
Victor
>------------------------------------------------------
>
>CALL FOR PAPERS
>==========================================
>11th Brazilian Symposium on Computer Music
>September 1-3 2007
>São Paulo - Brazil
>http://gsd.ime.usp.br/sbcm/2007
>==========================================
>
>The Symposium
>-------------
>
>The Brazilian symposia on computer music have consolidated the significance of
>Brazil's international position in the field of Computer Music. The 11th
>Brazilian Symposium on Computer Music is organized by NUCOM, the computer
>music branch of the Brazilian Computing Society (SBC), and it will be held
>in São Paulo from September 1st to 3rd, 2007.
>
>During the symposium there will be speeches by renowned researchers, technical
>and music paper sessions, discussion panels, and concerts. Researchers,
>scientists, composers, educators, manufacturers, and all concerned with the
>interplay between music and technology are invited to submit work. The
>program
>will include, among others, a keynote speech and a workshop by Roger B.
>Dannenberg (Carnegie-Mellon University, USA).
>
>The program committee will give a prize for the best student papers presented
>at SBCM. Papers that have a student as a major author are eligible. Two awards
>will be given: one for the best technical paper and another for the best
>music
>paper.
>
>ORGANIZATION
>------------
>General Chairs: Fabio Kon (University of São Paulo)
> Fernando Iazzetta (University of São Paulo)
>Technical Papers Chair: Geber Ramalho (Federal University of Pernambuco)
>Music Papers Chair: Mikhail Malt (IRCAM/Sorbonne-Paris IV)
>Local Arrangements Chair: Marcelo Queiroz (University of São Paulo)
>
>IMPORTANT DATES
>---------------
>June 3rd Full papers and posters submissions due
>July 15th Full papers and posters notification of acceptance
>July 30th Camera-ready version of papers and posters due
>
>TECHNICAL TOPICS OF INTEREST
>----------------------------
>The topics to be covered include, but are not limited to
>. Acoustics, Diffusion, Sonorization
>. Artificial Intelligence
>. Artificial Life and Evolutionary Music Systems
>. Audio Hardware design
>. Audio Digital Signal Processing
>. Computer-Aided Music Analysis
>. Computer-Aided Musical Education
>. Computer-Aided Musicology
>. Distributed Music
>. Internet and Web Applications
>. Multimedia Systems and Applications
>. Music Data Structures and Representation
>. Music Information Retrieval
>. Music Notation, Printing, and Optical Recognition
>. Quality of Service for Audio
>. Psychoacoustics and Cognitive Modeling
>. Real-time Interactive Systems
>. Software Systems and Languages for Composition
>. Sound Synthesis
>
>Technical Program committee
>---------------------------
>Adolfo Maia Jr. Universidade Estadual de Campinas
>Aluizio Arcela Universidade de Brasilia
>Andrew Horner The Hong Kong University of Science & Technology
>Chris Chafe Stanford University
>Edilson Ferneda Universidade Católica de Brasília
>Eduardo Miranda University of Plymouth
>Emilios Cambouropoulous Aristotle University of Thessaloniki
>Fabio Kon Universidade de São Paulo
>Flávio Soares Silva Universidade de São Paulo
>François Pachet Sony Computer Science Laboratory
>Gérard Assayag IRCAM
>Geber Ramalho Universidade Federal de Pernambuco
>Giordano Cabral Université Paris 6
>Henkjan Honing University of Amsterdam
>Hugo de Paula PUC Minas
>Ian Whalley University of Waikato
>Jean-Pierre Briot CNRS - Université Paris 6 & PUC-Rio
>Jonatas Manzolli Universidade Estadual de Campinas
>Lelio Camilleri University of Bologna
>Luis Jure Universidad de la República
>Marcelo Pimenta Universidade Federal do Rio Grande do Sul
>Marcelo Queiroz Universidade de São Paulo
>Marcelo Wanderley McGill University
>Marcio Brandao Universidade de Brasilia
>Maurício Loureiro Universidade Federal de Minas Gerais
>Oscar Di Liscia Universidad Nacional de Quilmes
>Palle Dahlstedt Göteborg University/Chalmers Univ. of Technology
>Peter Beyls Hogeschool Gent
>Petri Toiviainen University of Jyvaskyla
>Regis R. A. Faria Universidade de São Paulo
>Roger Dannenberg Carnegie Mellon University
>Rosa Viccari Universidade Federal do Rio Grande do Sul
>Sever Tipei University of Illinois School of Music
>Victor Lazzarini National University of Ireland
>
>Music Papers Program Committee
>------------------------------
>Mikhail Malt (chair) IRCAM/Sorbonne-Paris IV
>Alexandre Lunsqui Columbia University, NY -USA
>Fernando Iazzetta Universidade de São Paulo, Brazil
>Jonathas Manzoli UNICAMP, Brazil
>Karim Haddad IIRCAM, Paris-France
>Daniel Teruggi Ina-GRM, Paris- France
>Marc Battier Sorbonne-Paris IV, France
>Martin Supper Berlin University of the Arts, Germany
>
>Papers Submission
>-----------------
>Papers must be submitted in PDF format via the JEMS online system
>(https://submissoes.sbc.org.br/home.cgi?c=450).
>Technical papers, up to 12 pages long, are supposed to present original
>research with scientific contributions. Music papers, up to 12 pages long,
>describe the experience of composers and users of computational tools to
>produce music. Extended abstracts of posters, up to 4 pages long, should
>present
>on-going research. Please carefully comply with instructions in publication
>templates. Papers which do not fulfill the requirements can not be published.
>Download files for manuscript preparation in accordance with the SBC
>guidelines
>from http://gsd.ime.usp.br/sbcm/2007/templates
>
>In order to get the paper published, it is required that at least one author
>register for the symposium by August 1st.
>
>More Information
>================
>
>For further information, please visit the symposium home page at
>http://gsd.ime.usp.br/sbcm/2007.
>For questions regarding the technical papers, contact Geber Ramalho
>(glr at cin.ufpe.br), for music papers, contact Mikhail Malt
>(Mikhail.Malt at ircam.fr). For other inquiries contact the symposium general
>chairs Fernando Iazzetta (iazzetta at usp.br) or Fabio Kon
>(kon at ime.usp.br).
Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth
PHASEX-0.10.1 is a buildfix and bugfix release, highly recommended for
anyone who currently has 0.10.0. Here's the changelog:
* Fixed delay buffer size crash bug.
* Rebuilt config.h from configure.ac (fixes undefined PHASEX_DIR).
* Added engine thread cancellation point.
* Changed order of setting up JACK callbacks (might help jackdmp?)
* Moved main sample rate init code from samplerate callback to jack thread.
* Fixed oversampling mode.
* Fixed typo on bank.c.
* Disabled debug output in help.c.
* Added --enable-debug= option to configure.
* Fixed volume of bassy-plucked-lead and zeroed input boost on all
patches.
I'm still looking into issues with older versions of GTK-2.x. It looks
like the current minimum GTK version is somewhere around 2.6 or 2.8. Most
of the non-FC6 build issues appear to be related to this.
Reports for SMP, non-FC6, and jackdmp systems would be very helpful, as
these are the things I can't test right now.
Thank you all for the valuable feedback! I'm already getting a good sense
of what's needed most and where things should go in the project roadmap.
Based on responses so far, the roadmap up to 0.20.0 should look something
like this:
0.11.0 Bugfixes, buildfixes, code cleanups, GUI aesthetic issues.
0.12.0 Rework patch bank system to support alternate patch dirs and
include a patch chooser.
0.13.0 LASH support.
0.14.0 Fine-tune threads (remove locks), optimize dsp code more.
0.15.0 New small features and simple GUI enhancements.
0.16.0 Implement LFO clock-sync for MIDI clock and JACK transport.
0.17.0 JACK MIDI support.
0.18.0 Multitimbral or multiple instance support.
0.19.0 Overhaul parameters to add generic ctlr-float conversions
and add mod-matrix (w/ velocity and aftertouch handling).
0.20.0 OSC and DSSI support.
Cheers,
--ww
--
/* William Weston <weston(a)sysex.net> */
On Thu, May 03, 2007 at 08:33:35PM -0700, William Weston wrote:
>
> Velocity sensitivity mapping and a modulation matrix are already on the
> TODO list. Aftertouch handling should be very similar to velocity
> handling.
Cool. Real luxury would be having curves (comparable to GIMP's gradation
curves) so influence isn't limited to being linear.
For Ardour, a routing matrix is planned. I wonder if the requirements
might be comparable enough for a common implementation / shared code.
> Left click is reserved for future drag and drop capabilities.
Wow.
> > You could use a single checkbox in those cases where you have
> > Off/On radio buttons.
>
> Most of the widgets used will be changing once I can come up with a truly
> better way of handling things. For on/off buttons, I'm thinking of
> something that looks like a mechanical toggle switch.
I have been thinking about mechanical looking switches. The problem is
that they look like something that needs to be moved/dragged, while
simple clicking is the only sane operation efficiency-wise.
You could use toggle buttons. It's quite braindead that common themes
make them look like command buttons, but you could add an icon that
looks like an LED or change the colours to make the button look like
one of those milky-translucent backlit buttons like Korg and Roland
use.
> Thanks for the read. The sliders with text really seem to solve the
> screen real-estate issue. I'll have to rethink the use of sliders all
> over again.
Would be nice to see them implemented.
As part of the Phat toolkit, perhaps ;)
Sven of the GIMP team showed some interest, what could lead to another
chance of implementation.
--
Thorsten Wilms
Thorwil's Design for Free Software:
http://thorwil.wordpress.com
