Re: [LAU] Tapestrea synth from Princeton

Hallo, thomas fisher hat gesagt: // thomas fisher wrote: It's damn cool! At least according to the video, but I have a problem running it. I built the jack-version, but something is wrong with the GUI. here's my error: TAPESTREA version: 0.1.0.4 exe target: linux (jack) http://taps.cs.princeton.edu/ [taps^]:(2:SYSTEM): setting log level to: 5 (INFORM)... [taps^]:(2:SYSTEM): initializing audio engine... [taps^]:(2:SYSTEM): | sample rate: 48000 [taps^]:(2:SYSTEM): | buffer size: 1024 [taps^]:(2:SYSTEM): | signal size: 128 [taps^]:(2:SYSTEM): | num buffers: 4 [taps^]:(2:SYSTEM): | channels: 2 [taps^]:(2:SYSTEM): | allocating parallel bus... [taps^]:(2:SYSTEM): | allocating 8 audio buses... [taps^]:(5:INFORM): | | initializing audio bus 0... [taps^]:(5:INFORM): | | initializing audio bus 1... [taps^]:(5:INFORM): | | initializing audio bus 2... [taps^]:(5:INFORM): | | initializing audio bus 3... [taps^]:(5:INFORM): | | initializing audio bus 4... [taps^]:(5:INFORM): | | initializing audio bus 5... [taps^]:(5:INFORM): | | initializing audio bus 6... [taps^]:(5:INFORM): | | initializing audio bus 7... [taps^]:(2:SYSTEM): | initializing cache manager... [taps^]:(2:SYSTEM): | starting real-time audio... [taps^]:(2:SYSTEM): initializing graphics engine... [taps^]:(2:SYSTEM): | maximum frame rate: 30 [taps^]:(2:SYSTEM): | setting cursor state: ON [taps^]:(2:SYSTEM): | initializing opengl/glut... [taps^]:(2:SYSTEM): initializing windowing system... [taps^]:(2:SYSTEM): | setting window size: 1024 x 768... [taps^]:(2:SYSTEM): | setting window position: 0, 0... freeglut (tapestrea): ERROR: Internal error <Visual with necessary capabilities not found> in function fgOpenWindow The program 'taps' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 23 error_code 3 request_code 4 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Does this reflect a bird, ahem, bug in the program? Note that I'm using a slightly older card (Matrox G450, 16MB), but I can run GL normally (e.g. Gem in Pd). Ciao -- Frank Barknecht _ ______footils.org__