On Tue, 2008-10-14 at 23:00 +0200, Olivier Guilyardi wrote: it doesn't, but it would be nice if someone would add them. i don't know why people feel the need to be snarky about the "oh-so-famed JACK ringbuffer" ... its famed only because when we first implemented it nobody in the LAD community could find an open source implementation of the idea. i don't believe anybody has ever claimed that its the bees knees of lock-free ringbuffers (and if they did, they don't know what they are talking about). lennart also claims that the JACK implementation is borked because of "misuse of volatile". it would be nice if that was fixed too. another detail about the JACK ringbuffer model: yes, within JACK it is used in a way that involves copying data. thats because you cannot give a hardware device a pointer to your app's memory and expect it to be useful (certainly not if you want to mix streams). many other situations use a ringbuffer in a way that *doesn't* involve copying - you get the address(es) of where you can read/write in the buffer and then read/write from/to there, rather than any intermediate buffers. for example, within ardour, file i/o is done directly to/from the ringbuffer. yes, the API provides read/write methods that copy to/from some other buffer, but these are convenience methods that turn out to model the way that quite a lot of code wants to operate. i'm about to release the next jack(1), complete with 64/32 host/client support, and it would be cool to remove the longstanding memory barrier/volatile buglets from the library. --p

On Wed, 2008-10-15 at 13:02 +0200, Olivier Guilyardi wrote: the point of memory barriers is really to remove the need for test cases :) what is complex about memory barriers is understanding *why* they are necessary. their use is really quite straightforward. if you read that page carefully you will see that ross was still waiting to set up a repository when that page was last updated (2006). a shame. though i can speak, did i do anything to help it out?

Olivier Guilyardi wrote: Okay, I wrote such a test. It fails with Jack's ringbuffer (jack1 r3004) but succeeds with Portaudio's one (r1240). It's a very simple test. I'm starting two threads, writing incremented numbers into a ringbuffer, and checking that they follow each other on the reading end. The failure frequency depends on the chunk size / buffer size ratio. With relative short runs, I'm getting about 2 failures / million, for both 256 / 512 and 256 / 1024. I'm around 0.5 failure / million with a 256 / 4096 ratio. But longer runs would be necessary for exact statistics. There is no such failure with Portaudio's ringbuffer, even if I deactivate its memory barriers. But I just can't say if this bug is caused by the lack of memory barrier or not in Jack, because the two implementations are different, and all of this seems to depend on the CPU architecture, the movements of the clouds, the color of my coffee, etc.. ;) I'm running these tests on a Intel Core2 Quad Q6600 CPU, and making sure the two threads run on a different CPU by looking at the program startup output. I didn't test on a single-cpu architecture. The Portaudio code looks more and more robust to me. It's also surprisingly short. Maybe that the best would be to replace jack's ringbuffer with it? I think it should be possible to keep the jack_ringbuffer api unchanged. My test code is below. It expects the buffer size as first argument. Try with 512, 1024, 2048,... With a buffer size of 4096 bytes, I sometimes need to wait a minute or so for the first failure to appear. When saved in jack1 svn working dir, I compile it with something like: gcc -I. -o testrb -Wall testrb.c libjack/ringbuffer.c -lpthread #include <unistd.h> #include <jack/ringbuffer.h> #include <pthread.h> #include <stdio.h> #include <utmpx.h> #define ARRAY_SIZE 64 #define MAX_VALUE 0x10000 jack_ringbuffer_t *rb; static int fill_int_array (int *array, int start, int count) { int i, j = start; for (i = 0; i < count; i++) { array[i] = j; j = (j + 1) % MAX_VALUE; } return j; } static int cmp_array (int *array1, int *array2, int count) { int i; for (i = 0; i < count; i++) if (array1[i] != array2[i]) { printf("%d != %d at offset %d\n", array1[i], array2[i], i); return 0; } return 1; } static void * reader_start (void * arg) { int i = 0, a[ARRAY_SIZE], b[ARRAY_SIZE]; unsigned long j = 0, nfailures = 0; printf("reader started on cpu %d\n", sched_getcpu()); i = fill_int_array (a, i, ARRAY_SIZE); while (1) { if (jack_ringbuffer_read_space (rb) >= ARRAY_SIZE * sizeof (int)) { if (jack_ringbuffer_read (rb, (char *) b, ARRAY_SIZE * sizeof (int))) { if (!cmp_array (a, b, ARRAY_SIZE)) { nfailures++; printf("failure in chunk %lu - probability: %lu/%lu = %.3f per million\n", j, nfailures, j, (float) nfailures / (j + 1) * 1000000); i = (b[0] + ARRAY_SIZE) % MAX_VALUE; } i = fill_int_array (a, i, ARRAY_SIZE); j++; } } } return NULL; } static void * writer_start (void * arg) { int i = 0, a[ARRAY_SIZE]; printf("writer started on cpu: %d\n", sched_getcpu()); i = fill_int_array (a, i, ARRAY_SIZE); while (1) { if (jack_ringbuffer_write_space (rb) >= ARRAY_SIZE * sizeof (int)) { if (jack_ringbuffer_write (rb, (char *) a, ARRAY_SIZE * sizeof (int))) { i = fill_int_array (a, i, ARRAY_SIZE); } } } return NULL; } int main(int argc, char *argv[]) { int size; printf("starting ringbuffer stress test\n"); sscanf(argv[1], "%d", &size); printf("buffer size (bytes): %d\n", size); printf("array size (bytes): %d\n", sizeof(int) * ARRAY_SIZE); rb = jack_ringbuffer_create(size); pthread_t reader_thread, writer_thread; pthread_create (&reader_thread, NULL, reader_start, NULL); pthread_create (&writer_thread, NULL, writer_start, NULL); while (1) sleep(1); return 0; } -- Olivier Guilyardi / Samalyse

On Fri, 2008-10-17 at 14:13 +0200, Olivier Guilyardi wrote: Nice work. Nobody ask why we didn't do this 5 years ago! I'd rather add the memory barriers to the JACK code, but this could be a race to see who does what first. A memory barrier is typically single instruction. The complication tends to be defining them in a sufficiently portable way. --p

On Fri, Oct 17, 2008 at 8:46 AM, Paul Davis &lt;paul(a)linuxaudiosystems.com&gt; wrote: Why do you suspect you need memory barriers? My concern with ringbuffer.c is the non-atomic ops on the read and write pointers. They're marked volatile, but what I think you really want is make all ops on those fields atomic. Stuff like this: rb->read_ptr += n1; rb->read_ptr &= rb->size_mask; Looks like a problem to me. What happens if there's a context switch in between those 2 statements? NB: I only took a cursory glance at the code.

On Fri, Oct 17, 2008 at 03:02:30PM +0200, Paul Davis wrote: The original test fails here as well (dual i686). I attach the same test modified to use the simple C++ class I use normally. It has a slightly different API (allowing random access in the block read or written), but the essential difference is that the operations that modify the state seen by the other end (the commit() calls) are atomic. The _nrd and _nwr counters (similar to the r/w pointers in jack_ringbuffer) are never masked - the mask is applied in the testing and r/w code only. It would be quite easy to do something similar in the jack_ringbuffer code. This version procudes no errors here. Ciao, #include <unistd.h> #include <pthread.h> #include <stdio.h> #include <inttypes.h> #include <assert.h> // compile using g++ -I. -o testrb2 -Wall testrb2.cc -lpthread #define ARRAY_SIZE 64 #define MAX_VALUE 0x10000 class Lfq_u32 { public: Lfq_u32 (int size); ~Lfq_u32 (void); int write_avail (void) const { return _size - _nwr + _nrd; } void write_commit (int n) { _nwr += n; } void write (int i, uint32_t v) { _data [(_nwr + i) & _mask] = v; } int read_avail (void) const { return _nwr - _nrd; } void read_commit (int n) { _nrd += n; } uint32_t read (int i) { return _data [(_nrd + i) & _mask]; } private: uint32_t *_data; int _size; int _mask; int _nwr; int _nrd; }; Lfq_u32::Lfq_u32 (int size) : _size (size), _mask (_size - 1), _nwr (0), _nrd (0) { assert (!(_size & _mask)); _data = new uint32_t [_size]; } Lfq_u32::~Lfq_u32 (void) { delete[] _data; } static Lfq_u32 *Q; static int fill_int_array (int *array, int start, int count) { int i, j = start; for (i = 0; i < count; i++) { array[i] = j; j = (j + 1) % MAX_VALUE; } return j; } static int cmp_array (int *array1, int *array2, int count) { int i; for (i = 0; i < count; i++) if (array1[i] != array2[i]) { printf("%d != %d at offset %d\n", array1[i], array2[i], i); return 0; } return 1; } static void *reader_start (void * arg) { int k, i = 0, a[ARRAY_SIZE], b[ARRAY_SIZE]; unsigned long j = 0, nfailures = 0; printf("reader started on cpu %d\n", sched_getcpu()); i = fill_int_array (a, i, ARRAY_SIZE); while (1) { if (Q->read_avail() >= ARRAY_SIZE) { for (k = 0; k < ARRAY_SIZE; k++) b [k] = Q->read (k); Q->read_commit (ARRAY_SIZE); if (!cmp_array (a, b, ARRAY_SIZE)) { nfailures++; printf("failure in chunk %lu - probability: %lu/%lu = %.3f per million\n", j, nfailures, j, (float) nfailures / (j + 1) * 1000000); i = (b[0] + ARRAY_SIZE) % MAX_VALUE; } i = fill_int_array (a, i, ARRAY_SIZE); j++; } } return NULL; } static void *writer_start (void * arg) { int k, i = 0, a[ARRAY_SIZE]; printf("writer started on cpu %d\n", sched_getcpu()); i = fill_int_array (a, i, ARRAY_SIZE); while (1) { if (Q->write_avail() >= ARRAY_SIZE) { for (k = 0; k < ARRAY_SIZE; k++) Q->write (k, a [k]); Q->write_commit (ARRAY_SIZE); i = fill_int_array (a, i, ARRAY_SIZE); } } return NULL; } int main(int argc, char *argv[]) { int size; pthread_t reader_thread, writer_thread; if (argc < 2) return 1; sscanf(argv[1], "%d", &size); printf("starting ringbuffer stress test\n"); printf("buffer size (bytes): %d\n", size); printf("array size (bytes): %d\n", sizeof(int) * ARRAY_SIZE); Q = new Lfq_u32 (size); pthread_create (&reader_thread, NULL, reader_start, NULL); pthread_create (&writer_thread, NULL, writer_start, NULL); while (1) sleep(1); return 0; } -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa.

Here's my result. BTW, non of the machines I tested on had the sched_getcpu function, so I added "#define sched_getcpu getpid" to the file. ------------------- Machine 1: 8 X (core Intel(R) Xeon(R) CPU E5320 @ 1.86GHz) === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 17602 writer started on cpu: 17602 60288 != 60160 at offset 0 failure in chunk 373678 Rest was success ------------------- Machine 2: 1 X (AMD Sempron(TM) 3000+) Success Success Success ------------------- Machine 3: 3 X (Intel(R) Xeon(TM) CPU 2.80GHz) === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 27916 writer started on cpu: 27916 16640 != 16512 at offset 0 failure in chunk 2300164 Rest was success ------------------- Machine 4: SunOs 5.8 sun4u sparc SUNW,Ultra-4 Solaris :-) The jack test compiled fine. Portaudio version: "portaudio/pa_ringbuffer.c", line 121: #error: Memory barriers are not defined on this system. You can still compile by defining ALLOW_SMP_DANGERS, but SMP s Also: $ ./test-int-array-jack starting ringbuffer stress test (2 minutes max) Segmentation Fault

On Fri, 17 Oct 2008, Olivier Guilyardi wrote: Looks like pthreads aren't working properly: " ./test-int-array-jack 512 starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 14631 " The writer is never started. Or perhaps printf is not working, but probably not, since it's been like that for several minutes. Same with ./test-int-array-portaudio-nobarrier 512 Also note that the programs were compiled with Sun's C compiler, not gcc, since gcc doesn't seem to be installed on the machine. I'm no Sun expert, so I don't know what may cause this.

Am Freitag, den 17.10.2008, 16:39 +0200 schrieb Olivier Guilyardi: CPU Info Pentium III (Coppermine) 256 KB cache flags( - ) clocked at [ 870.022 MHz ] gcc -Wall -I. -I./jack -lpthread -o test-int-array-jack \ test-int-array.c jack/ringbuffer.c gcc -Wall -I. -I./portaudio -lpthread -o test-int-array-portaudio \ test-int-array.c portaudio/ringbuffer.c portaudio/pa_ringbuffer.c gcc -Wall -I. -I./portaudio -lpthread -o test-int-array-portaudio-nobarrier \ -DNO_MEMORY_BARRIER \ test-int-array.c portaudio/ringbuffer.c portaudio/pa_ringbuffer.c ./alltests.sh Starting ringbuffer tests (buffer size: 512) === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 0 Success === Portaudio ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 0 Success === Portaudio ringbuffer test (without memory barriers) === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 0 Success regards hermann

hermann meyer wrote: Any chance we can see the Faust source code as well? That would be far more educational for the likes of, well, me. :-) -- Darren

Hello Hermann! Do I get this right: guitarix includes a commandline interface or is this just a particular commandline-interface for a part of the whole? Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

Ah well, I thought it wouldn't be for the whole thing. Perhaps you consider it someday, making guitarix accessible by the commandline. Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

Am Sonntag, den 02.11.2008, 17:40 +0100 schrieb Dragan Noveski: Thanks You can start it with the set_env_guitarix.sh also to use the guitarix.rc and select ports to connect at start time. Maybe the $(LADSPA_PATH) Have you set it in your .bashrc for root ? when not export it or set it. If you dont wont the ladspa plugin for gutarix you can remove the install files for it from the makefile. regards hermann

On Sunday 02 November 2008 18:39:02 hermann meyer wrote: Failed to compile: g++ -O3 -Wall -MMD -MP -DVERSION=\"0.2.0\" -c -o impdata.o impdata.cc impdata.cc: In member function 'int Impdata::sf_open_read(const char*)': impdata.cc:264: error: 'SFC_WAVEX_GET_AMBISONIC' wasnot declared in this scope impdata.cc:264: error: 'SF_AMBISONIC_B_FORMAT' was not declared in this scope impdata.cc: In member function 'int Impdata::sf_open_write(const char*)': impdata.cc:306: error: 'SFC_WAVEX_SET_AMBISONIC' wasnot declared in this scope impdata.cc:306: error: 'SF_AMBISONIC_B_FORMAT' was not declared in this scope I have all the libraries, I think.

On Sun, Nov 02, 2008 at 08:39:32PM +0200, David Baron wrote: See the jconv Makefile. Jconv depends on a pre-release of libsndfile. If you don't have it then uncommenting one line in the Makefile will allow you to compile jconv. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa.

hermann meyer wrote: hallo herman, again i am getting an error when trying to install: nowhiskey@murija2:~/software/nove/guitarix/guitarix-0.03.0$ sudo make install mkdir -p mkdir: fehlender Operand »mkdir --help« gibt weitere Informationen. make: *** [install] Fehler 1 nowhiskey@murija2:~/software/nove/guitarix/guitarix-0.03.0$ could you please tell me (again) what i should change in the makefile in order to install properly? cheers, doc

hermann meyer wrote: thanks herman, that did the trick (again)! the 'control' buttons look good! i did not tested the appi very hard untill now, but it seems to be improving! anyway, it is running rather stable, i have not experienced any crashes with it. thanks for that! cheers, doc

guitarix is a simple Linux Rock Guitar amplifier for jack(Jack Audio Connektion Kit) with one input and two outputs. Designed to get nice thrash/metal/rock/blues guitar sounds. There are controls for bass, treble, gain, compressor, preamp, balance, overdrive, distortion, freeverb, impulse response (), crybaby(wah) and echo . For 'pressure' in the sound you can use the feedback and feedforward sliders. This is a bugfix release. fixed bug's : set gain persistent in jconv settings remove compiler flags ( sse + fast-math ) make guitarix_midi_out temporarly ________________________________________________________________________ changelog: guitarix (0.03.9-1) unstable; urgency=low * add Oscilloscope like wave view widget * fix bug in jconv gain settings * set jack_midi_port to be temporarly (off by default) * remove sse and fast-math flags from makefile guitarix based on Gtk, a great part is also realesed as ladspa plugin. guitarix is licensed under GPL Homepage with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ For capture guitarix make use of jack_capture ver >= 0.9.30 from Kjetil S. Matheussen. If you dont have it installed, look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Response guitarix make use of jconv from Fons Adriaensen. If you dont have it installed, look here: http://www.kokkinizita.net/linuxaudio/index.html I use faust to build the prototype and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://www.musikwissenschaft.uni-mainz.de/~ag/ag.html : Yann Orlary http://faust.grame.fr/ regards hermann

hermann meyer wrote: hallo hermann, great to hear that guitarix is being more and more developed, also that you got other people on the boat! i have problems building the new release: ... Checking for header ladspa.h : ok Checking for header boost/program_options.hpp : ok Checking for library boost_program_options-mt : not found /home/nowhiskey/software/nove/guitarix-0.04.6-1/wscript:61: error: the configuration failed (see config.log) .... i installed boost libs, once they became an ardour dependency. which version is required for building guitarix? cheers, doc

guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings in one input and two output ports to the jack graph. Release 0.05.0-1 comes with some major changes: * Completely new source structure by James * add keyboard shortcuts * improved skin handling * add logging window * improved preset handling * add middle tone control * reworked audio engine * add bypass mode * add engine state widget Please read the README for more details regarding the new options. have fun ________________________________________________________________________ The standalone version of guitarix is based on GTK2+. But guitarix is also released as a suite of LADSPA plugins and can be used in e.g. ardour. guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ For capture, guitarix uses the external application 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the convolution application 'jconv' created by Fons Adriaensen. If you don't have it installed, you can look here: http://www.kokkinizita.net/linuxaudio/index.html I(hermann) use faust to build the prototype and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://www.musikwissenschaft.uni-mainz.de/~ag/ag.html : Yann Orlary http://faust.grame.fr/ regards guitarix-dev team: Hermann Meyer & James Warden

I'm happy to announce a new guitarix release guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings in one input and two output ports to the jack graph. Release 0.05.2-1 comes with some changes: * remove dependency of the boost library (Many thanks to "thrasher13b" for the patch) * fix missing "./" in ./debian/rules reported by GMag (AV Linux) * add 2 Channel gain and delay chooser to the Jconv settings widget. * add scroll/zoom mode to the wave view * reworked Jconv settings widget UI * various GUI and feature clean-up's have fun Comments and suggestions are welcome. ________________________________________________________________________ The standalone version of guitarix is based on GTK2+. But guitarix is also released as a suite of LADSPA plugins and can be used in e.g. ardour. guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ For capture, guitarix uses the external application 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the convolution application 'jconv' created by Fons Adriaensen. If you don't have it installed, you can look here: http://www.kokkinizita.net/linuxaudio/index.html I(hermann) use faust to build the prototype and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ regards Hermann Meyer & James Warden ------------------------------------------ guitarix-dev team

Am Donnerstag, den 03.12.2009, 14:04 +0100 schrieb Hartmut Noack: Thanks Hartmut, good to hear that you like it. :-) Make guitarix a LV2-plugin, is at least a question of development power. We would love that to, but, Guitarix is a young small project, we are only 2 developers, and we both have at first other tasks in mind witch we wone implement. In fact, it will be easy for a bit experienced LV2 developer to port the "control chain" of guitarix to LV2. Our source is spiked with comments witch make it easy to jump in and grep the needed source. Guitarix is a open Project, open for developers who wone join the project. gruß hermann

guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings in one input and two output ports to the jack graph. Release 0.05.5-1 comes with some changes: * set dependency of Gtk+ down to version 2.12 (for stable users, introduced by James Morris, thanks James) * make effects moveable (reorder effect chain) have fun ________________________________________________________________________ Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ For capture, guitarix uses the external application 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the convolution application 'jconvolver' or the older 'jconv' created by Fons Adriaensen. If you don't have it installed, you can look here: http://www.kokkinizita.net/linuxaudio/index.html I(hermann) use faust to build the prototype and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ regards Hermann Meyer & James Warden ------------------------------------------

guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings in one input and two output ports to the jack graph. Release 0.05.9-1 : * add Midi learn (by Andreas Degert) * add internal direct convolution unit with 7 filter kernel (amp models) * add LADI level1 support * add a new light skin * reworked multi thread handling(by Andreas Degert) * reduced CPU usage for Oscilloscope To the midi learn function: a middle mouse button click on a controller pop's up a little widget, move the midi controller you will use, the controller number is shown in the widget. Press OK when you've done. That's it. By the way, a right click on a controller pop up a spinbox for direct enter the value with your keybord. have fun ________________________________________________________________________ guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ For capture, guitarix uses the external application 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the convolution application 'jconvolver' created by Fons Adriaensen. If you don't have it installed, you can look here: http://www.kokkinizita.net/linuxaudio/index.html I(hermann) use faust to build the prototype and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ regards Hermann Meyer, James Warden, Andreas Degert

guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings in one input and two output ports to the jack graph. Release 0.07.0 comes with a bunch of major changes : * nearly complete reworked source by Andreas Degert * amp and effect units based direct on faust expressions * all faust sources included * new accumulated tuner unit with new interface (analogue Style needle meter) * Midi controller connections could saved with in presets and/or general * a editable Midi controller map is available * new human readable preset style * knobs could be used like sliders (press ctrl + mouse-button and move the mouse horizontal, leave the ctrl and hold mouse-button for fine tune), or like real knobs (turn them around) * convolution unit based on zita-convolver is now integrated in the engine * presets could change with Midi Program Messages * I'm sure I have some things forgotten to mention here. Check out the new great sound of the faust optimized sources. To the midi learn function: a middle mouse button click on a controller pop's up a little widget, move the midi controller you will use, the controller number is shown in the widget. Press OK when you've done. That's it. By the way, a right click on a controller pop up a spinbox for direct enter the value with your keyboard. have fun ________________________________________________________________________ guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ please report bugs or suggestions here: http://sourceforge.net/apps/phpbb/guitarix/ For capture, guitarix uses the great 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the zita-convolver library by Fons Adriaensen. If you don't have it installed, you can look here: http://www.kokkinizita.net/linuxaudio/index.html We use faust to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ For faust users : You could find the tools we use to convert (and plot) the resulting faust cpp files to the needed include format in the /guitarix/tools directory. Faust dsp files are in /guitarix/src/faust and the resulting cc files are in /guitarix/src/faust-cc As default we have disable faust for build, if you wane play with the faust expressions, simply add --faust to the ./waf configure step, then faust will be used to rebuild the included faust-cc files. regards Hermann Meyer, James Warden, Andreas Degert

guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. guitarix uses the Jack Audio Connection Kit as its audio backend and brings to the jack audio graph a mono amplifier input/output port, and a FX mono input with two (stereo) output ports. guitarix provide a jack midi input port to connect a midi controller (midi learn) and a (3 channel) jack midi output port, feed by a (scalable) mix of the tuner and a beat-detector. Release 0.09.0 comes with following changes : * make distortion a multiband distortion * fix bug in resample IR-files * resample IR-files now on-the-fly * add insert point ports to the effect chain * add --optimization flag for configure the build * switch to double precision instead of single precision * fix bug in reconfigure convolver when preset change * add patch from Peder Hedlund, build against gtk-2.12.9 and gcc-4.3.1 * add faust 0.9.24 to the "good_faust_versions" have fun ________________________________________________________________________ NOTE:// Andreas have found and solved a bug in the IR-file resampler, that means that all the files you have resampled with guitarix, are "NOT RESAMPLED", only the header was change. To get rid of this, please remove the resampled files and rename the files with the extension .orig (remove .orig) That sucks, sorry for that. hermann _________________________________________________________________________ guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum here: http://sourceforge.net/apps/phpbb/guitarix/ here is a nice YouTube video about what you can do with guitarix: http://www.youtube.com/watch?v=KdlJZQT3zY4 (Thanks stevie :-)) ________________________________________________________________________ For capture, guitarix uses the great 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the zita-convolver library, and, for up/down sampling we use zita-resampler, both written by Fons Adriaensen. If you don't have it installed, get it here: http://www.kokkinizita.net/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ For faust users : All used Faust dsp files are included in /guitarix/src/faust, the resulting cc files are in /guitarix/src/faust-cc The tools we use to convert (post-processing and plot) the resulting faust cpp files to the needed include format, stay in the /guitarix/tools directory. ________________________________________________________________________ regards Hermann Meyer, James Warden, Andreas Degert

Hi Julien Sorry, I completely forget about that, :-( but here is a quickly hacked build script witch will allow you to build and install the ladspa plugins only. They are not updated for long time, so they don't contain the MultiBandDistortion or the new Amp stuff. greats hermann Am Sonntag, den 06.06.2010, 18:55 +0200 schrieb Julien Claassen:

I'm happy to announce the first public release of gx_head. gx_head is a simple guitar mono tube amplifier simulation based on the work we have done in the guitarix project. gx_head provide 3 tube models (12AX7, 12AU7, 6V6) and 8 different tonestack models(Bassman, Twin Reverb, Princeton, JCM-800, JCM-2000, M-Lead, M2199, AC30), so you can simply create the amp-model to your needs. gx_head comes with a bunch of in-build effects, like distortion, crybaby, autowah, phaser, flanger, echo, delay, . . . The effects could ordered in two Racks, on for the mono effects, witch could be load for pre or post processing, and one for the stereo effects, witch could only used in post processing. Effects are loadable over the menu, a pop-up menu in the racks, or a plugin bar. Settings could saved/load as presets. gx_head comes with some factory settings provided by guitarix/gx_head friend "funkmuscle", thanks therefore. All UI controllers could connected with jack midi via MIDI learn with your external MIDI controllers. gx_head is ready for language support via gettext() and comes thanks to Pablo Fernández with a Spanish translation. The style file gx2 is contributed by zettberlin, thanks Hartmut some features in short: * 8 tonestack models * 3 tube models * cabinet impulse response module * bass boster * easy Impulse Response file support via zita-convolver * on the fly IR-file resampling via zita-resampler * Oscilloscope and tuner * multi band distortion model * scalable EQ * phaser, flanger, stereo delay, stereo echo, * overdrive, compressor, freeverb, reverb, * chorus, moog filter, low/high pass filter, . . * MIDI learn * Patch Info widget * Preset File Load/Export option * factory settings * language support * shining User Interface via GTK/gtkmm * . . . . have fun _________________________________________________________________________ gx_head is licensed under the GPL. screenshots: http://sourceforge.net/apps/wordpress/guitarix/ direct download: http://sourceforge.net/projects/guitarix/files/gx_head/gx_head-0.12.0.tar.b… download: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum here: http://sourceforge.net/apps/phpbb/guitarix/ ________________________________________________________________________ For extra Impulse Responses, gx_head uses the zita-convolver library, and, for resampling we use zita-resampler, both written by Fons Adriaensen. http://www.kokkinizita.net/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ For faust users : All used Faust dsp files are included in /gx_head/src/faust, the resulting .cc files are in /gx_head/src/faust-cc The tools we use to convert (post-processing and plot) the resulting faust cpp files to the needed include format, stay in the /gx_head/tools directory. ________________________________________________________________________ regards guitarix development team

Am Sonntag, den 16.01.2011, 11:08 +0100 schrieb Jeremy Jongepier: Hi Jeremy Thanks for feedback, I'm glad you enjoy the project results. Yes, basically gx_head is guitarix 0.12.0, but there are so many changes internal and in the GUI that it isn't the same any more. gx_head based on the knowledge we have collected during the development of guitarix. It's a step back to the roots and two steps forward to develop a easy to use Open Source Tube Amp emulation. :-)) So yes, gx_head will replace guitarix. regards hermann

Am Sonntag, den 16.01.2011, 09:52 -0800 schrieb Steiny: Thanks for the kid words, is good to know that some people like it. :-) regards hermann

Il giorno ven, 14/01/2011 alle 21.36 +0100, hermann ha scritto: [cut] Thank you very much for your great job, Hermann! Next day I will take a tour on new features and default presets. Can you give us some tips about translation? I will glad to help about italian language, if no other wants. But I'm little confused about which words translate and wich not. For example: for the knob description (example GAIN, LEVEL, ...) I think english is well (hardware rig also use it) Ivan

2011/1/16 Ivan Tarozzi &lt;itarozzi(a)gmail.com&gt; Hi Ivan, I'm facing the exact same problem for the French translation. What are the words that can be translated and what are the ones that, if translated, will create confusion ? Basically, musicians are used with terms like the ones you list but aslo with effect names (delay, overdrive, etc) and some of them are just not translatable in French :-/ So after a long discussion on linuxMAO.org (French Linux Music Ressource), we finally decided that : - effects and parameters (delay, dry/wet, ...) should not be translated to avoid further confusion - accoustic terms (bass, treble, ...) even though used by the French musicians will be translated according to the accoustic theory - terms that have a generaly accepted translation and not only used in music software (plugin, ports, bus, client for example) will be translated - jack related terms will be translated according to the existing translation of course - others will be translated Took us quite some time to agree on that ! Hope it helps !!! jy

Am Montag, den 17.01.2011, 14:35 +0100 schrieb Ivan Tarozzi: Hi Ivan There is the GNOME Translation Project for example here is the list of teams: http://l10n.gnome.org/teams/ regards hermann

Il giorno dom, 16/01/2011 alle 10.31 -0800, Mark Knecht ha scritto: [cut] I use a SoundBlaster Audigy2-EX, not really a professional card, but I'm not professional too :) Because it has only inputs at line-level (low impedance) I use something between Guitar and interface: - Zoom G2.1 in flat mode (bypass) or - Behriger MIC200 So I can transform High impedance (pickup guitar) to lower. I think is the same to use a D.I. Box or a Audio Card with Hi-Z input. just my 2c Ivan

On 01/14/2011 12:36 PM, hermann wrote: Hermann, I'd like to thank you as well. Let me tell you, one of the main reasons that held me back from switching over to Linux for music was that I was afraid I wouldn't be able to find a good amp simulator (I was a Guitar Rig user as well). Then I found Guitarix! And I thought, sure this is pretty new and the interface needs a bit of work, but I was finding awesome tones with it, and saw the potential of this project. So I'm really excited about gx_head. I'm probably going to be playing with this for hours later today and give more feedback. Good luck in continuing development of this project. Many will benefit from this. -Kris

gx_head is a simple guitar mono tube amplifier simulation based on the work we have done in the guitarix project. gx_head provide 3 tube models (12AX7, 12AU7, 6V6) and 8 different tonestack models(Bassman, Twin Reverb, Princeton, JCM-800, JCM-2000, M-Lead, M2199, AC30), so you can simply create the amp-model to your needs. gx_head comes with a bunch of in-build effects, like distortion, crybaby, autowah, phaser, flanger, echo, delay, . . . The effects could ordered in two Racks, on for the mono effects, witch could be load for pre or post processing, and one for the stereo effects, witch could only used in post processing. Effects are loadable over the menu, a pop-up menu in the racks, or a plugin bar. Settings could saved/load as presets. gx_head comes with some factory settings provided by guitarix/gx_head friends "funkmuscle" and "zettberlin", thanks therefore. All UI controllers could connected over jack midi via MIDI learn with your external MIDI controllers. gx_head is ready for language support via gettext() and comes thanks to Pablo Fernández with Spanish , and thanks to Ivan Tarozzi with Italian translation. The style file gx3-dezert is contributed by zettberlin, thanks Hartmut new features in short: * add mix tubes * add post amp * add noise gate * add Italian translation by Ivan Tarozzi * add desert skin by zettberlin * add factory settings by zettberlin have fun _________________________________________________________________________ gx_head is licensed under the GPL. screen-shots and sound examples: http://sourceforge.net/apps/wordpress/guitarix/ direct download: http://sourceforge.net/projects/guitarix/files/gx_head/gx_head-0.13.0.tar.b… download: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum here: http://sourceforge.net/apps/phpbb/guitarix/ ________________________________________________________________________ For extra Impulse Responses, gx_head uses the zita-convolver library, and, for resampling we use zita-resampler, both written by Fons Adriaensen. http://www.kokkinizita.net/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ For faust users : All used Faust dsp files are included in /gx_head/src/faust, the resulting .cc files are in /gx_head/src/faust-generated The tools we use to convert (post-processing and plot) the resulting faust cpp files to the needed include format, stay in the /gx_head/tools directory. ________________________________________________________________________ regards guitarix development team

gx_head is a simple guitar mono tube amplifier simulation based on the work we have done in the guitarix project. WAIT, NO, We decide it's time to sync our project name and our project we work on. So we replace guitarix /gx_head by guitarix2, This release is a full replacement for guitarix and/or gx_head in any sense. You cant have install the old guitarix and/or gx_head parallel to this release. Please uninstall all older versions before use this one. please refer to our project page for more information: http://guitarix.sourceforge.net/ new features in short: * reworked GUI controllers * reworked rc-style files * replace clean tube modes by a clean <-> distortion controller * new cab models and controls (level, bass, treble) * new tonestack models * make tonestacks and cabs a move-able module * cleaner effect rack construction * customizable effect rack order (horizontal, vertical) * a bunch of what I have forget to mention here have fun _________________________________________________________________________ guitarix is licensed under the GPL. screen-shots and sound examples: http://guitarix.sourceforge.net/ direct download: http://sourceforge.net/projects/guitarix/files/guitarix/guitarix2-0.15.0.ta… download site: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum: http://sourceforge.net/apps/phpbb/guitarix/ ________________________________________________________________________ For extra Impulse Responses, gx_head uses the zita-convolver library, and, for resampling we use zita-resampler, both written by Fons Adriaensen. http://kokkinizita.linuxaudio.org/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ For faust users : All used Faust dsp files are included in /gx_head/src/faust, the resulting .cc files are in /gx_head/src/faust-generated The tools we use to convert (post-processing and plot) the resulting faust cpp files to the needed include format, stay in the /gx_head/tools directory. ________________________________________________________________________ regards guitarix development team

guitarix/gx_head is a simple guitar mono tube amplifier simulation. please refer to our project page for more information: http://guitarix.sourceforge.net/ new features in short: * fixed jack session support * add amp-model (push/pull) * add amp-model (feedback) * fix build/runtime issue on OSX * reformat source to the Google C++ Style Guide conventions * some minor fixes and maybe new bugs have fun _________________________________________________________________________ guitarix is licensed under the GPL. screen-shots and sound examples: http://guitarix.sourceforge.net/ direct download: http://sourceforge.net/projects/guitarix/files/guitarix/guitarix2-0.17.0.ta… download site: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum: http://sourceforge.net/apps/phpbb/guitarix/ ________________________________________________________________________ For extra Impulse Responses, gx_head uses the zita-convolver library, and, for resampling we use zita-resampler, both written by Fons Adriaensen. http://kokkinizita.linuxaudio.org/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ For faust users : All used Faust dsp files are included in /gx_head/src/faust, the resulting .cc files are in /gx_head/src/faust-generated The tools we use to convert (post-processing and plot) the resulting faust cpp files to the needed include format, stay in the /gx_head/tools directory. ________________________________________________________________________ regards guitarix development team

Am Samstag, den 09.07.2011, 22:50 +0400 schrieb Alexandre Prokoudine: There are no plans to change that. gx_head is the short for guitarix(amp)head, maybe that help to solve the confusion. :-) It's the name used in the jack graph and also used for the configuration folder. regards hermann

On 24.07.2011 13:12, wrote hermann: Hi Hermann, nice, but could the graphics be larger or scalable? On my screen res. of 1600x1200 I can barely see it. Thank you very much for the guitar tools. Raphael ;)

Thanks for the scaling patch Hermann- that was certainly the biggest problem I had with gxtuner (that its display was so small) but unfortunately I couldn't get the patch to apply. There is one more small feature I'd like to see in gxtuner and that is display of the notes octave number. I realise it displays the frequency of the note so you could work it out from that but it'd still be a nice addition to not have to do that (think;)! I've still not got round to trying guitarix itself but its certainly nice to have its tuner as a standalone app - especially as its the only fully working and currently maintained Linux/JACK tuner I've tried. Thanks again Hermann! Dan On Mon, Jul 25, 2011 at 6:54 PM, hermann &lt;brummer-(a)web.de&gt; wrote:

Am Mittwoch, den 27.07.2011, 10:13 +0000 schrieb Fons Adriaensen: Hi Fons well, zita-at1 is a nice app, but as a simple tuner it's a bit overhead. Not at least, thanks to your famous library zita-resampler, gxtuner needs ~1% CPU to indicate the tune and freq. Also, gxtuner, comes with the well known analogue like interface witch guitarists use all over the world. And now, it is full scalable. regards hermann

Am Mittwoch, den 27.07.2011, 11:58 +0000 schrieb Fons Adriaensen: May you would like to review the source again, I'm still learning and be far from perfect, and usually I'm open for suggestions and hints how to improve what I try to do. I break the tuner out for a user request, for nothing more. And, well we use a downsample rate of 16 const int DOWNSAMPLE = 16; m_sampleRate = sampleRate / DOWNSAMPLE; resamp.setup(sampleRate, m_sampleRate, 1, 16); for the overhead I didn't mean the mem usage or download size, like I said, gxtuner use ~1% CPU witch isn't as bad I mean, zita-at1 needs the double amount here. kind regards hermann

Am Mittwoch, den 27.07.2011, 14:21 +0000 schrieb Fons Adriaensen: Yep, zita-at1 do a lot more, that's the point, and it is a nice application, just, it isn't a simple guitar/bass tuner like gxtuner is. Anyhow, if you have more hints for me, how I could improve this thing, I will be happy to hear about. kind regards hermann

Hi Hermann! On Wed, Jul 27, 2011 at 12:06 PM, hermann &lt;brummer-(a)web.de&gt; wrote: Thanks! That compiles and scales for me now - thanks for the quick fix! I'm pleased with my new musical tool. Cool! Whilst its hardly a showstopper or even mildly pressing problem, it doesn't seem you can truly scale gxtuner up to full screen of totally fill a window of arbitrary dimensions at the mo and I presume this is down to the bitmap background it uses. It would be cool to see gxtuners interface go fully vector eventually. 2011 is such an exciting time to be part of the Linux audio community!

Am Mittwoch, den 27.07.2011, 15:33 +0100 schrieb allcoms: Okay, now I understand what you mean, arbitrary, BabelFish helps me. :-)) well that is possible with the current cairo back-end, it's just that I take care that dimensions stay stable. So here is gxtuner with a full rubber interface to scale to any arbitrary you like. http://sourceforge.net/projects/guitarix/files/gxtuner/gxtuner-1.2.tar.bz2/… greats hermann

guitarix/gx_head, a guitar mono tube amplifier simulation for jack a new release (0.18.0) is available. please refer to our project page for more information: http://guitarix.sourceforge.net/ new features in short: * add tube model 12AT7 * fix runtime issues when build with g++ > 4.5 * add presence level controller * add bass booster level controller * switch to function pointer based engine * fix issues with GtkBuilder > 2.14 and Glade files * fix correct use of included zita-resampler source * add factory settings by autoandimat download site: http://sourceforge.net/projects/guitarix/ have fun Many thanks to Fons Adriaensen for lead me to find and fix a bogus bug related to correct object bindings in C++ kudos to Fons _________________________________________________________________________ As well, a new release (1.4) of gxtuner is available, gxtuner comes now with jack_session support. Read the README for details. http://sourceforge.net/projects/guitarix/files/gxtuner/ regards guitarix development team

Am Dienstag, den 06.09.2011, 13:23 +0200 schrieb Jeremy Jongepier: Hi Jeremy Yep, it's a Bug, it's fixed in our SVN repository now. greats hermann

Hello I’m happy to announce a update release of gxtuner, a simple, small and lightweight guitar/bass tuner for jack. It's a break out of the guitarix tuner module, gxtuner-1.5 changes: * added reference pitch controller * added threshold controller * added command-line option (-i) to connect at start up gxtuner comes with a analogue like, full arbitrary scaling interface (scale), show the tune, the octave and the accumulated frequency in Hz, and it comes with full jack-session support. gxtuner use a equal-tempered scale based on A4 = 440 Hz (427Hz <-> 453Hz) gxtuner is licensed under the GPL. for more information please read the included README file. get it here: http://sourceforge.net/projects/guitarix/files/gxtuner/ direct link http://sourceforge.net/projects/guitarix/files/gxtuner/gxtuner-1.5.tar.bz2/… have fun Guitarix developers

Am Freitag, den 09.12.2011, 15:42 +0100 schrieb Jostein Chr. Andersen: Hi Jostein Thanks for your comment, . . . but it leads me to the conclusion that you didn't have try gxtuner. Anyhow, maybe a better solution for your purpose will be AT1 by Fons Adriaensen http://kokkinizita.linuxaudio.org/linuxaudio/zita-at1-doc/quickguide.html regards hermann

Am Freitag, den 09.12.2011, 21:26 +0100 schrieb Jostein Chr. Andersen: I tune one string to a reference pitch (or a tuner), and tune the other strings in relation to the tuned string (without a tuner). That is done then by hearing. I guess that is what most guitarists do. Therefore gxtuner could be a helpful tool. gxtuner isn't mean to break physical law. greats hermann

Hi Gerhard, On Saturday 10 December 2011 13.17.41 Gerhard Zintel wrote: ... Probably, but I have the fortune of having very good mechanics on my gear, so it's almost in tune even after hours of playing and whammying! :-) Tuners are in general only really needed for live playing and when you do intonation. And it seems to me that one can calibrate this tuners to specific guitars with help of presets. And with ±.02 cents guaranteed accuracy ( a trained ear is usually not better than around ±.2-3 cents) this is very good stuff. A bridge-only adjusted guitar often has tones that is as much as ± 10 cents out of tune (my subjective opinion - it can even be worse), that can in theory be as bad as 20 cents of error between 2 tones! So a tuner for live usage need to be able to have presets that says "Bulls eye" slightly out of tune for each of the open EADGBE strings in order to have a good compromise for guitars with only the bridge adjusted. Personally, I don't use tuners on stage, but the turbo-tuners look great! ..or maybe a Linux-powered one that runs on a netbook, laptop, pad or a smartphone? ;-) Jostein

Hello A update release of gxtuner is available a simple, small and lightweight guitar/bass tuner for jack (a break out of the guitarix tuner module) This update is for those, who's like to use a simple tuner with a analogue style like interface It resolve some user requests and primary added some more command-line options. Also it added all configuration options to be restored by the jack session manager. gxtuner-1.6 changes: * add command-line option reference pitch control * add command-line option threshold control * add command-line option window size * add command-line option window position * add all options to be restored by jack session manager gxtuner comes with a analogue like, full arbitrary scaling interface (scale), show the tune, the octave and the accumulated frequency in Hz, gxtuner comes with full jack-session support. gxtuner use a equal-tempered scale based on A4 = 440 Hz (427Hz <-> 453Hz) gxtuner is licensed under the GPL. for more information please read the included README file. get it here: http://sourceforge.net/projects/guitarix/files/gxtuner/ direct link http://sourceforge.net/projects/guitarix/files/gxtuner/gxtuner-1.6.tar.bz2/… have fun Guitarix developers _______________________________________________ Linux-audio-announce mailing list Linux-audio-announce(a)lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-announce

guitarix/gx_head, a guitar mono tube amplifier simulation for jack, a new release (0.21.0) is available. please refer to our project page for more information: http://guitarix.sourceforge.net/ for more help please visit our Wiki page witch is improved by Gaius Baltar, (thanks for your work on that, Gaius) http://sourceforge.net/apps/mediawiki/guitarix/index.php?title=Main_Page new features in short: * new (4 mode)racktuner replaced old gxtuner * new LADSPA wrapper for the complete engine * new online help points to the guitarix Wiki * new hide extended settings button for each module * replace waf with wafadmin to respect the DFSG * various changes in the source download site: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum: http://sourceforge.net/apps/phpbb/guitarix/ there you could found also a couple of examples produced by guitarix users: http://sourceforge.net/apps/phpbb/guitarix/viewtopic.php?f=11&t=83 have fun _________________________________________________________________________ For extra Impulse Responses, guitarix uses the zita-convolver library, and, for resampling we use zita-resampler, both written by Fons Adriaensen. http://kokkinizita.linuxaudio.org/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ guitarix development team

Olivier Guilyardi wrote: vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz stepping : 6 Starting ringbuffer tests (buffer size: 512) === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 1 48128 != 48000 at offset 0 failure in chunk 971504 === Portaudio ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 Success === Portaudio ringbuffer test (without memory barriers) === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 Success It would be great if this got fixed since we (FFADO) exercised the GPL on the jack ringbuffer code... Greets, Pieter

rob wrote: URL: http://svn.samalyse.com/misc/rbtest Repository Root: http://svn.samalyse.com Repository UUID: 45b80e9b-b122-0410-81d2-d67874e9c27f Revision: 305 Node Kind: directory Schedule: normal Last Changed Author: olivier Last Changed Rev: 305 Last Changed Date: 2008-10-17 18:13:13 +0100 (Fri, 17 Oct 2008) Target: i686-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --enable-libmudflap --disable-libssp --disable-libgcj --with-arch=i686 --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 4.1.2 (Gentoo 4.1.2 p1.0.1) === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 1 38656 != 38528 at offset 0 failure in chunk 664156 === Jack ringbuffer test (with fix 1) === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 Success === Portaudio ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 Success === Portaudio ringbuffer test (without memory barriers) === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 Success

On Fri, Oct 17, 2008 at 7:39 AM, Olivier Guilyardi &lt;ml(a)xung.org&gt; wrote: $ uname -a Linux IVES 2.6.25-gentoo-r7-a #3 SMP PREEMPT Wed Oct 1 14:45:40 PDT 2008 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AuthenticAMD GNU/Linux === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 42496 != 42368 at offset 0 failure in chunk 317080 === Jack ringbuffer test (with fix 1) === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 1 writer started on cpu: 0 Success === Portaudio ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 writer started on cpu: 1 reader started on cpu 0 Success === Portaudio ringbuffer test (without memory barriers) === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 1 Success -- Brad Fuller

Ken Restivo a écrit : I only got these warnings on Mac OS X, I suppose it depends on the gcc and/or libc version. That did not cause any segfault in my case though. I've fixed it anyway. Please update rbtest to r309. Thanks, -- Olivier Guilyardi / Samalyse

On Fri, Oct 17, 2008 at 1:20 PM, Olivier Guilyardi &lt;ml(a)xung.org&gt; wrote: Looks like I don't have to "step back" or "read the whole thread for links to relevant documents" then ;) I didn't test your patch, but my own patch (which is the same thing) works on dual Core2 duo system, whereas the original didn't. No memory barriers needed *on x86* (volatile isn't needed anywhere). Others system probably need memory barriers.

Olivier Guilyardi wrote: excuse my chiming in here, i'm not really much of a c programmer... but how can this - rb->read_ptr += n1; - rb->read_ptr &= rb->size_mask; + rb->read_ptr = (rb->read_ptr + n1) & rb->size_mask; fix anything? iiuc, both versions are equivalent. a context switch could happen just as well after the parenthesis has been computed..!? putting stuff on one line doesn't make it atomic. maybe you are now getting another compiler optimization that helps to hide the bug? no offense, just trying to learn something... jörn -- jörn nettingsmeier home://germany/45128 essen/lortzingstr. 11/ http://spunk.dnsalias.org phone://+49/201/491621 Kurt is up in Heaven now.

Fons Adriaensen wrote: I don't see why it's fragile. There's no reason for the compiler to modify rb->read_ptr if not asked to. Buf if that's the case, because of some sort of dark voodoo optimization, then we could use a temporary variable to hold the intermediary result. Better, all computation could be done on this temporary variable and transfered into rb->read_ptr once finished, so that modifying the later only involves memory copy. You class looks good, but some work is needed to provide a Jack backward compatible API based on it. IMO, one important thing is to include unit/regression tests, for the ringbuffer as well as general Jack operation, in the official jack distribution, that one can run with a simple "make test". I'll try to do this for this test suite I wrote, once cleaned up. -- Olivier Guilyardi / Samalyse

Fons Adriaensen wrote: i see. but what about the other scenario: thread A reads read_ptr. thread B runs and increments it. thread A increases the old (wrong) read_ptr value by one and writes a wrong value. isn't that a problem here? -- jörn nettingsmeier home://germany/45128 essen/lortzingstr. 11/ http://spunk.dnsalias.org phone://+49/201/491621 Kurt is up in Heaven now.

Fons Adriaensen wrote: ah, of course. one reader, one writer only. sorry for the noise. -- jörn nettingsmeier home://germany/45128 essen/lortzingstr. 11/ http://spunk.dnsalias.org phone://+49/201/491621 Kurt is up in Heaven now.

On Fri, Oct 17, 2008 at 02:33:00PM -0400, Paul Coccoli wrote: But there is nothing that stops the compiler from writing read_ptr any number of times it wants unless you make that variable volatile. Indeed. The original version really invited the problem, by *forcing* the compiler to write read_ptr twice. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa.

Paul Davis wrote: i haven't thought much about this issue, but the fact that i got a failure on an uniprocessor athlon64 seems to contradict your statement: (posted to linux-audio-dev earlier:) nettings@kleineronkel:/build/rbtest> make test gcc -Wall -I. -I./jack -lpthread -o test-int-array-jack \ test-int-array.c jack/ringbuffer.c test-int-array.c: In function ‘main’: test-int-array.c:101: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘long unsigned int’ gcc -Wall -I. -I./portaudio -lpthread -o test-int-array-portaudio \ test-int-array.c portaudio/ringbuffer.c portaudio/pa_ringbuffer.c test-int-array.c: In function ‘main’: test-int-array.c:101: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘long unsigned int’ gcc -Wall -I. -I./portaudio -lpthread -o test-int-array-portaudio-nobarrier \ -DNO_MEMORY_BARRIER \ test-int-array.c portaudio/ringbuffer.c portaudio/pa_ringbuffer.c test-int-array.c: In function ‘main’: test-int-array.c:101: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘long unsigned int’ ./alltests.sh Starting ringbuffer tests (buffer size: 512) === Jack ringbuffer test === starting ringbuffer stress test (2 minutes max) buffer size (bytes): 512 array size (bytes): 256 reader started on cpu 0 writer started on cpu: 0 49536 != 49408 at offset 0 failure in chunk 330502 -- jörn nettingsmeier home://germany/45128 essen/lortzingstr. 11/ http://spunk.dnsalias.org phone://+49/201/491621 Kurt is up in Heaven now.

On Sat, Oct 18, 2008 at 06:46:00PM +0200, Paul Davis wrote: It doesn't matter how many times it is read, but it does matter if it is ever written with a wrong value. And this *did* happen in the old version at the end of a read: rb->read_ptr += n1; rb->read_ptr &= rb->size_mask; If a context switch occurs after the first statement, and read_ptr > size (which can happen), then the writer would believe there is more space to write than there actually is. Same at the other end: an incomplete update of write_ptr (the addition is executed but not yet the mask) could make the reader believe there is more to read than there actually is. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa.

On Sat, Oct 18, 2008 at 10:56:31PM +0200, Paul Davis wrote: The only way to know is to verify all the possible cases in jack_ringbuffer_write_space() and jack_ringbuffer_read_space(), taking into account that the masking operation may not have been applied at the time these are called, and that 'the other' *_ptr could be >= size. Note that this is *much* simpler in the C++ class that I poster earlier - there are no conditions at all in write_avail() or read_avail(). The essential difference is that I don't mask the stored values of _nrd and _nwr (the equivalents of read_ptr and write_ptr). This also removes the ambiguity between an empty and full buffer. The downside is that it depends on the user code acting in the correct way (which seems reasonable). Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa.