>Hmmm, I think the alsa api is a bit huge/complicated. I would never
>reccomend doing alsa directly, and I think it was a very bad advice
>actually. Check out portaudio, sndlib or jack instead, which provides
>easier interface to the soundcard than alsa, and works on top of alsa (and
>others).
Portaudio doesn't support mixers so you still need some alsa or oss
code.
I bet I'm not asking the right list ...
Anyone here knows about good "phrase trainer" application ?
It should be able to play audio file at slower speed without changing
the pitch.
--
Francois Isabelle <isabellf(a)sympatico.ca>
http://www.notam02.no/arkiv/src/
Mammut will FFT your sound in one single gigantic analysis (no windows).
These spectral data, where the development in time is incorporated in
mysterious ways, may then be transformed by different algorithms prior to
resynthesis. An interesting aspect of Mammut is its completely
non-intuitive sound transformation approach.
This is very minor update. If you already have mammut, theres probably not
much point in upgrading. The "big" change in this release is the first
entry in the changelog. I must also warn that mammut can be a bit hard
to compile up, now that pygtk1 has been replaced with pygtk2 in all
recent distributions I know about.
0.16 -> 0.17
-Initialize sound at startup, so that mammut appears in jack patch bays.
-Removed the included sndlib binary.
-Added a point in the INSTALL file about how to configure mammut to
find the pygtk1 files.
-Added a note in the INSTALL file about that sndlib for some reason
does not work with delta cards when using the alsa driver. The oss
driver (under alsa emulation), and the jack driver works just fine.
--
iain duncan wrote:
>>I think that 'groove quantise' does have quite a specific meaning :
>>> To take the timing from one midi part, and apply it to another.
>>> So, you get the midi timing from a real drummer grooving away and
>>apply
>>> it to your beat. Then it pulls your beats to the nearest beat in the
>>> groove, rather than to the normal 16th or whatever.
>
>
>That was one sequencer's implementation of the term, but certainly not >a
>universally accepted strict definition.
I guess so. It's only Cubase that calls it that. Emagic logic, Fruity
Loops, Pro Tools, Groove Slicer, Cakewalk Sonar and Digital Performer
all call using the timing from one part on another a 'groove template',
which is much clearer.
If the 'groove' was pulling the notes towards a dotted or triplet feel,
I'd call it 'shuffle' or 'swing' to differentiate it.
'groove quantise' should perhaps be used when a sequencer or drum
machine is applying a groove more complex than a simple triplet feel,
but not using a template based on another recording.
>Iain
HI all,
There was a discussion on the LAU list about jamin using FFT
based filtering. I I missed much of the discussion but that
particular point just jumped out at me.
Has anyone thought of trying linear phase FIR filters instead of
FFT methods? Any filter that can be specified in the frequency
domain can be implemented in the time domain and vice-versa.
Often (but not always), the time domain version is significantly
cheaper in CPU cycles.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"Neither noise nor information is predictable."
-- Ray Kurzweil
Hi all,
Does anyone know of a page somewhere that explains just what (on a
developer level) MIDI "groove" is? I want to implement it in a
sequencer, but all I can find is user documentation pages with useless
information.
Is it as simple as each note having a time offset (ie snare is early .5
ms, hi-hate late 1ms, etc.) or something more?
Thanks..
-DR-
Hi!
I want to programme my mic and my speakers on my FC2 box. I am running
KDE. Is there a library which I should look at or is the ALSA API the way
to go?
Thanks,
Catalin
--
<<<< ================================== >>>>
<< We are what we repeatedly do. >>
<< Excellence, therefore, is not an act >>
<< but a habit. >>
<<<< ================================== >>>>
Dave Robillard wrote:
>Hi all,
>
>Does anyone know of a page somewhere that explains just what (on a
>developer level) MIDI "groove" is? I want to implement it in a
>sequencer, but all I can find is user documentation pages with useless
>information.
>
>Is it as simple as each note having a time offset (ie snare is early .5
>ms, hi-hate late 1ms, etc.) or something more?
>
>Thanks..
I think that 'groove quantise' does have quite a specific meaning :
To take the timing from one midi part, and apply it to another.
So, you get the midi timing from a real drummer grooving away and apply
it to your beat. Then it pulls your beats to the nearest beat in the
groove, rather than to the normal 16th or whatever.
I seem to remember having some floppys of grooves back in the atari days
and doing this with midi shaker patterns and the like, but it's been a
long time....
Hans Fugal:
>
> ALSA. If you want to tie yourself to KDE and endless misery, try artsd,
> but I warned you.
>
Hmmm, I think the alsa api is a bit huge/complicated. I would never
reccomend doing alsa directly, and I think it was a very bad advice
actually. Check out portaudio, sndlib or jack instead, which provides
easier interface to the soundcard than alsa, and works on top of alsa (and
others).
--
Hello,
I trying my first steps with Supercollider. Build and install
went without any probles, and I learned just enough elisp to
get scel running in emacs.
Now the problem seems to be that sclang and scsynth do not
talk to each other. How is the sclang -> scsynth UDP link
configured ? There is no option in sclang to set the port
number it sends to so probably this is fixed. OTOH, scsynth
requires a port number for the -u option, but what should
this be ?
TIA,
--
Fons
