On Fri, 2009-07-03 at 23:19 +0200, Ulrich Lorenz Schlüter wrote:
The release contains a simple series of logic gates. Namely an AND,
NAND, OR, NOR, XOR, XNOR and a NOT.
http://uli-plugins.sourceforge.net
So now I looked through the plugin menu in Ingen to check for the
duplication I
On Sun, 2009-07-05 at 00:51 +0200, Robert Jonsson wrote:
Hi Renato,
maybe I misunderstand you someway but does this driver not already
produce midi? If not what does it produce, keyboard events?
If it's midi, which I would suspect, then it should just be a matter
och getting Rakarrack to
On Sat, 2009-07-04 at 19:12 -0400, Mark Vitek wrote:
Hello,
I am new to audio/midi programming, but in my experience Jack is the
easier API to learn/use.
If you download midimon from sourceforce, and look in mm_jack.cc /
mm_jack.h you can see the basic usage.
Basically, you pass a callback
Hello Renato,
This should be fairly easy to do using RT Midi (
http://www.music.mcgill.ca/~gary/rtmidi/http://www.music.mcgill.ca/%7Egary/rtmidi/
)
Since there is a driver for it, you should be able to use it as an alsa midi
device. There are a few ways to route alsa midi to jack midi. I
On Sun, Jul 5, 2009 at 2:50 AM, Renato Budinichrenn...@gmail.com wrote:
On Sat, 2009-07-04 at 19:12 -0400, Mark Vitek wrote:
Hello,
I am new to audio/midi programming, but in my experience Jack is the
easier API to learn/use.
If you download midimon from sourceforce, and look in mm_jack.cc /
Thank you very much, this is interesting, I'll have a look into RtMidi
and your program. Being that the little I know is C, is it much more
difficult outputting notes using the alsa api?
Since there is a driver for it, you should be able to use it as an
alsa midi device.
uhm, i'm not
Renato Budinich wrote:
Thank you very much, this is interesting, I'll have a look into RtMidi
and your program. Being that the little I know is C, is it much more
difficult outputting notes using the alsa api?
Since there is a driver for it, you should be able to use it as an
alsa midi
I wrote:
Subject: Re: [LAD] help on creating MIDI from linux input events
Date: Sun, 05 Jul 2009 13:11:35 +0200
From: Ralf Mardorf
To: Renato Budinich
CC: linux-audio-dev@lists.linuxaudio.org
Renato Budinich wrote:
Thank you very much, this is interesting, I'll
I'm not a Linux, neither a C/C++ coder, but the answer here is very
simple, if the MIDI events (I guess this is what you mean by keyboard
events)
nope sorry, i meant EV_KEY events as in linux/input.h - they are
certainly not MIDI events.
Renato
Renato Budinich wrote:
I'm not a Linux, neither a C/C++ coder, but the answer here is very
simple, if the MIDI events (I guess this is what you mean by keyboard
events)
nope sorry, i meant EV_KEY events as in linux/input.h - they are
certainly not MIDI events.
OT a very stupid
I asked:
Renato Budinich wrote:
I'm not a Linux, neither a C/C++ coder, but the answer here is very
simple, if the MIDI events (I guess this is what you mean by keyboard
events)
nope sorry, i meant EV_KEY events as in linux/input.h - they are
certainly not MIDI events.
Am Sonntag, den 05.07.2009, 13:21 +0200 schrieb Renato Budinich:
I'm not a Linux, neither a C/C++ coder, but the answer here is very
simple, if the MIDI events (I guess this is what you mean by keyboard
events)
nope sorry, i meant EV_KEY events as in linux/input.h - they are
certainly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Everyone,
I've released a new version of the Invada LV2 plugins. Major changes are:
* Added new plugin: 'Delay - Munge'.
A delay with non-linear response in the feedback loop. The 'munge' affect is
more noticeable the higher the feedback. Also
Hi,
On Thu, 25 Jun 2009, Stefano D'Angelo wrote:
[using LADSPA unique ids]
That is bad of Ecasound, since ladspa.h says:
Plugin types should be identified by file and label rather than by index or
plugin name, which may be changed in
new plugin versions.
Ecasound allows to use both label
On Sunday 05 July 2009 05:41:11 Renato Budinich wrote:
On Sun, 2009-07-05 at 00:51 +0200, Robert Jonsson wrote:
Hi Renato,
maybe I misunderstand you someway but does this driver not already
produce midi? If not what does it produce, keyboard events?
If it's midi, which I would suspect,
Hmm, so you're saying that the device sends keyboard events. How did you
find out which kind of data it sends out?
Sending out midi note events is easy with RTMidi, check out the section on
midi out section. It contains a section on MIDI note output.
I don't have much experience on grabbing
Miguel Morales wrote:
Hmm, so you're saying that the device sends keyboard events. How did
you find out which kind of data it sends out?
Sending out midi note events is easy with RTMidi, check out the
section on midi out section. It contains a section on MIDI note output.
I don't have
It might be an overkill, but something like this is very easily done with
SuperCollider (or Chuck or Pd for that matter).
hey, i have just started using sc! I'll ask on the sc list for some
code. Thank you!
In the meanwhile i found pyrtmidi - python bindings for rtmidi, which i
could use in a
Renato Budinich wrote:
It might be an overkill, but something like this is very easily done with
SuperCollider (or Chuck or Pd for that matter).
hey, i have just started using sc! I'll ask on the sc list for some
code. Thank you!
In the meanwhile i found pyrtmidi - python bindings for
On Sun, 2009-07-05 at 11:10 +0200, Thorsten Wilms wrote:
On Fri, 2009-07-03 at 23:19 +0200, Ulrich Lorenz Schlüter wrote:
The release contains a simple series of logic gates. Namely an AND,
NAND, OR, NOR, XOR, XNOR and a NOT.
http://uli-plugins.sourceforge.net
So now I looked
On Sun, 2009-07-05 at 19:10 +0300, Kai Vehmanen wrote:
Hi,
On Thu, 25 Jun 2009, Stefano D'Angelo wrote:
[using LADSPA unique ids]
That is bad of Ecasound, since ladspa.h says:
Plugin types should be identified by file and label rather than by index
or plugin name, which may be
21 matches
Mail list logo
