azr3-jack & gtkmm-2.4 dependencies

Problem with AZR3 compiling on 64 Studio is this...First of all, lash-dev should have a hard dependency on libasound2-dev but it does not in 64 Studio. You have to manually install the libasound2-dev package. Secondly, you have to make sure that you have the g++ package installed. Just installing the required dev packages only installs g++ 3.3, you need g++ 4.1 installed or the program won't even begin to compile. That's all there is to it, and it compiles just fine.

I got it to compile, but every time I try to run it I get this: lash_open_socket: could not connect to host 'localhost', service '14541' lash_comm_connect_to_server: could not create server connection lash_init: could not connect to server 'localhost' - disabling LASH Could not initialise LASH! Jack is running. Why the program is trying to connect to port 14541 makes no sense to me unless that's a port that Jack listens on. But I can nmap localhost and that port isn't listed at all. Kinda sad, Beatrix is a damn good Hammond emulator, but has no GUI, no support for Jack, and does not have any implementation for a sustain/hold pedal through MIDI. Bristol, I'm sorry to say, is the worst Hammond simulation I've ever heard and seriously needs documentation. Maybe the other synth models will come in handy someday, but for now, v0.30 is so poor sounding that it's useless. Nice eye candy, but that's it, and eye candy doesn't sound worth a damn on stage or on a recording. So, I was really hoping this program would work. No way I'm buying a Native Instruments Hammond emulator, I don't run Linux so I can run Windows programs.

You need the Lash-dev file, if I am not mistaken...

Hi. I installed 2.1 a few days ago (after I tried Fedora + CCRMA for a while and found it too cutting edge for my needs). I also needed some -dev packages (for compiling an own version of ardour and japa - wich BTW I think should be included in 64Studio as it currently lacks a capable analyser. ;) ). I finally enabled the etch-backports but wondered why the -dev packages are not included in the default repo. Installing the needed packages pulled in an unwanted upgrade and fiddling around I finally messed up some things, so I think I better reinstall. But before doing this it would be good to have some suggestions wich sources should be enabled and if there is some advice for apt-pinning and possibly additional apt.conf settings to avoid unwanted side effects. My idea is to stay with stable 64Studio, have all the -dev packages and sources for stable available, receiving security updates, being able to install additional packages from etch and do handselected updates from 64Studios etch-backports. Advice would be highly appreciated. Axel. ^.^

Some of the dev files are hiding in there...