Hello,
First of all I want to announce that the next version of NASPRO will
shift to LV2 as its internal model, which means that it will contain a
collection of bridges from other APIs to LV2 and viceversa
In order to accomplish such a thing (writing wrappers for LV2), a
special extension is need
Hi there,
In my quest to compile and package qTribe, i thought i'd use my iBook to
see how much of a pain it will be to run it under OS X.
(I know Jack OS X doesnt support CoreMIDI port-bridging yet so it won't
be too useful on OS X)
I can compile it quite happily with the Qt I downloaded from
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-co
"Patrick Stinson":
>
> I know that the rule is to never block in a real time audio thread,
> but what about blocking for resources shared between real-time
> threads? In the case of a sequencing app that uses one thread per
> audio/instrument track (as most do), is it OK to share a lock between
>
Howdy!
I am pleased to announce this new and long due release of QjackCtl, the
Qt GUI for the awesome JACK Audio Connection Kit.
Release highlights are mainly about final JACK-MIDI support for the
"evil" Patchbay, new Messages file logging and the most intriguing
application window instance un
Malte Steiner wrote:
> Hi,
>
> looks like an interesting partner for my Minicomputer synthesizer. You
> write that it should be used with a touchscreen but could you make the
> buttons mapped to standard alphanumeric keyboard too?
>
better yet, let that be completely user configurable: map all
Hi,
looks like an interesting partner for my Minicomputer synthesizer. You
write that it should be used with a touchscreen but could you make the
buttons mapped to standard alphanumeric keyboard too?
About packaging, I didn't bother for my projects so far and usually its
up to package maintain
On Sat, Jun 07, 2008 at 12:20:23AM +0200, [EMAIL PROTECTED] wrote:
> ...
> note that this just asks for params 512-639 (the first loop
> of the previous posting is commented)
>
> so, after receiving param 590 i receive only every fifth or
> fourth param, the rest is gone void.
> this is repeata
