Great feedback from the list guys, am more excited about it now than i was when i got it mostly functional! I will definitely add keyboard shortcuts - There's a QT4 port in the works, not sure how configurable QT3's shortcuts are. I think i'll put in some hardcoded ones initially. If user-configurable actions are easy to implement in QT3 then i might just do that. The actual electribe hardware has a 'virtual keyboard' mode where the 16 step keys can be used as a 1-and-a-bit octave keyboard, but i think i may just implement midi recording + midi thru to allow a real keyboard to be used, or the virtual keyboard of your choice - i really want to make this sequencer simple and modular, rather than an all-things-to-all-people sequencer. I'm also going to fix the JACK API calls that are breaking on older versions of JACK (requires an nframes_t arg on some calls when newer versions of the API don't) I've had reported slowness problems with gentoo - I'll add a debug enable flag to the app can be launched with this to generate a report I can use to try and identify the problem. Thanks for your interest and thoughts, -Pete On 8/06/2008, at 12:18 AM, Rui Nuno Capela wrote:

Hallo, Malte Steiner hat gesagt: // Malte Steiner wrote: I just stumbled upon the Non Sequencer, which seems to be nice for live performance as well: http://non.tuxfamily.org/ Never tried it, though (and probably I never will use it very much as I'm comfortable with Pd. ;) Ciao -- Frank Barknecht _ ______footils.org__

Dave Phillips <dlphillips(a)woh.rr.com> writes: Dave, let me know if you have any issues. I'll be happy to answer any questions you may have--I know the manual needs a bit more fleshing out ;-) There are many things left for me to do in the way of improving the interface (making key-bindings more easily discoverable is high on the list). But I have been spending all my available free-time working on Non-DAW lately and haven't really done anything but port some build system improvements over to Non-Sequencer. I haven't forgotten it, though, and I've got a number of new FLTK tricks up my sleeve that I'm itching to port over to Non-Sequencer as well--just as soon as I get the Non-DAW (pre?) release out of the way.

I read that, pretty bold statement. Dont see that SEQ24 is that unoptimized, I think its rather good. I wonder why the creator didn't jump onboard seq24 and improved it. Typical open source behaviour, but maybe he is heading in another direction. I hope the NON is good in live context, any experience, anyone? Seq24 is doing 90% what I expect from it and about the rest I am thinking of joining that project instead of creating another one. Cheers, Malte -- ------------- Malte Steiner http://www.block4.com media art + development next event: 13.6.2008: Elektronengehirn live OpenEar Festival Cardiff,UK

Malte Steiner <steiner(a)block4.com> writes: Do you *really* want me to go into more detail? Don't get me wrong. I used seq24 extensively. I read the code inside and out and I know what it's limitations are. I'm a practical person. I'm a free-software developer, not an 'open source' developer (whatever that means). I needed a program to suit my needs. I looked at seq24, I looked at Dino, and a hundred other seqs that didn't really provide anything close to what I wanted. I know I would not have been happy with a version of seq24 with phrases tacked-on but retaining the same tired old piano role + timeline interface--not to mention the wildly inefficient drawing algoirthms and datastructures. By the time I ripped out all that's broken in seq24 there would have been nothing left. Therefore I decided to start from scratch. I would have *loved* to have been able to use Dino's libdinoseq as my engine instead of writting all that from scratch, but, unfortunately, there's more to code compatibility than just licensing. The libdinoseq design just doesn't mesh at all with what I wanted to do in Non. That being said, seq24's design is not highly compatible with JACK MIDI either--and I decided going into Non that it was going to be pure JACK MIDI. I bet if you asked Rob Buse wheter he would like to be able to take the time to do a complete re-write on seq24 he would say, emphatically yes, as would any other author of a medium to large sized program. If someone is totally in love with seq24, then I would love to see them put in the work required to clean up and optimize it--it would not be impossible, just a lot of (boring) work. And, BTW, I'm on record saying *far* harsher things about other software--seq24 has been good to me, all things considered. But I definitely outgrew it. Since when is competition a bad thing anyway? ;-)

Pelle, Yeah, i think i will build a separate 'keyboard widget' into the app, with a key to switch between keyboard and part mute key mappings. Will probably support channel splitting so you can play 2 parts simultaneously + drums from the keys - Obviously range, and most likely any ability to chord effectively - will be limited with a QWERTY instead of a proper external keyboard . I looked at the source for jack-keyboard and it implements the same keymap as Impulse Tracker does, so i'll probably follow that layout. Using the step keys as an 'emulated' keyboard isn't very usable, even on the actual electribe. Using a separate app for a virtual keyboard is not ideal, but will probably be implemented first - mostly because i want to use my external MIDI keyboard with it. -Pete