-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have been very happy with this keyboard. I bought it mainly to replace my old cheap keyboard as I liked the feel of the keys. The drum pads were nice as well. The transport and sliders were optional in a "it would be nice to get them working eventually" sort of way.
Some of the knobs and sliders made changes to zynaddsubfx so there is a lot of potential coolness here. I am still figuring this out as I have had my keyboard for about a week. Just in time for the workshop I am supposed to do for a FOSS festival tomorrow. Nothing like adding new hardware into the mix at the last minute :) One thing to be careful about is that the Axiom has internal presets that dictate how it presents itself to your computer. Niels Giesen wrote: > Hi G, > > I found out that part 10.1 of the ardour manual > http://www.ardour.org/files/manual/ch-control-surfaces.html Good to know, my google incantations were less than productive. > can be applied to generic midi interfaces too. I own an axiom61. I have the 49 key model. > Basically it is like : connect your axiom via jack to the control and > mcu ports of ardour. Then, in a template (no: no site wide config On mine I see two entries for the Axiom in the jack midi section. I do not know what the second one does (I am guessing it is presenting the midi in port on the back as a separate midi interface?) > option here :( ) press Ctrl-middle mouse button when the cursor is > over a button. This leads to a dialogue-box popping up in-place, > saying 'operate controller now'. Do so, and from then on, within that > template, the controller n the Axiom controls the control in ardour. > Only one thing strikes me, and that is that I cannot seem to bind > goto start and goto end, which seems to be a problem on the side of > ardour. Please tell whether you find the same problem. Maybe we ought > to file a bugreport there. > > By the way, it might be nice to share our Axiom and other > midi-configuration files for ardour, so that we can ease the use of > new hardware. We could start off to do this in the form of very basic > templates shared on the 'net. If we want to have plug-n-play like > stuff for this one day, we got to start of defining good defaults I > guess. For me, it is difficult for instance to decide what sliders and > rotaters to use for which functions in ardour, and I haven't yet > settled for a single approach, the consequence of which is I do not > use the controls that much. If you have a mind more orderly than mine, > please share your setup once you have settled for a sane approach. I do plan on documenting my discoveries on this nice (so far) piece of hardware. I'll keep you posted on my progress. I can also give you some space on one of my web servers if you need somewhere to upload templates and the like. I am not sure how much plug and play autoconfiguration we can do. There are so many ways that I can see this device being used, that providing a sane default would be challenging. > > greetings, Niels Cheers, Gustin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHIoD9wRXgH3rKGfMRAgwVAJ0QfkTz3B9SLk4YPdIg1rjzmNpG/ACgnzDT VHdATLFtnwBbazdT84p914c= =ZWpM -----END PGP SIGNATURE----- _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
