Hi,
Many thanks for all feedback on my original posting about what
features you would like to see in an open midi controller...
Based on your "requests" I've started experimenting a bit with adding
rotary encoders and a 20x4 lcd display. I've changed to a more
powerful (but still cheap and easy to work with) microcontroller
atmega128 (from atmega16). If you're not familiar with
microcontrollers you might be familiar with the arduino platform which
also uses an atmega (but the lesses atmega168).
Now to my question: Does anyone have some sample velocity curves, like
a mapping from key velocity to midi velocity for different instruments
(grand piano etc)? There doesn't seem to be any convention on how to
handle velocity data?? Does some synths expect linear mapping and does
the "mapping" in software??
--Albin
Hey everyone.
I hope there is some bright minds on this mailing list who can help me.
EMU1212 output 4 differen stereo signals throug ADAT plauying 4 different
sound streams simultasniosly.
The card is installed and alsa recognises it.
aplay -l lists three devices on card 0
device 0 has 32 subdevices.
device 1 is missing
device 2: has 8 subdevices and is named something with FX controller
Device 3 har 1 subdevice
*sury i dont have the real output at the monet*
In alsamixer (playback) I can select a souce for each of the 2 analog
outputs and each of the 8 ADAT outputs from ADAT0-ADAT7
The sources include DSP0-DSP31 and ADAT0-ADAT7 and some more
Natually i think that the 32 subdevicec in device 0 coresponed to the 32
DSP's in ALSA.
But no matter which of the subdevices i try to guide mplayer ot aply
through, it only plays through the sam DSP's
DSp 0 and DSP1 are respectivly left and rigth channel, dsp 6 and 7 is a
player e damped signal of one of dsp0 or ds1 and dsp8 is also playing one of
DSP1 and 2 undamped though.
the rest of the dsp's does not rout any music unless the souround volume is
turned up.
I Testeed this by listning on all the diferens outputs analog 1 and 2 and
the 8 adat channels while chagin through the diferent sources.,
I can sucessfully send sound from DSP1 and or = to each of the outputs and
therefor the physical output is working fine.
But i am not able to use other DSP than 0 and 1 dispite what commands I give
mplayer.
e.q. mplayer -ao alsa:device=hw=0.0.x MUSIC_FILE
I have tried combinations and all the devices
device 2 and 3 returns an device error.
What can I do ?
Humm, than that seems to be the reverse of what we would expect,
that must be then probably because of the missing samples.
If samples were not missing (say
samples from the two channels got distributed between four
channels) then it should go up in pitch, because each channel
would run through the entire data twice as fast, similarly
to what would happen if a mono file was opened as stereo.
If on the other hand you were opening a stereo file as mono,
then the pitch would go down (with some distortion possibly).
Maybe that is what is happening, your stereo file became 4
identical mono tracks.
Victor
----- Original Message -----
From: "Raymond Martin" <laseray(a)gmail.com>
To: "victor" <Victor.Lazzarini(a)nuim.ie>
Sent: Monday, October 05, 2009 10:39 PM
Subject: Re: [LAD] Half speed audio playback issue
> Hi Victor,
>
>> I thought something like that was happening. But I'm curious: if a
>> 2-channel file is played over 4-channels it should go up an octave,
>> should
>> it not? You'd
>> have half as much data for 4 channels as you'd have for 2 channels and so
>> it would seem like it's going faster? Or my reasoning is wrong somewhere
>> (it could
>> well be, I often get things like that mixed up)?
>
> Since you have half as much data your processing (e.g., D to A conversion)
> will interpret this as being at half the rate. Perhaps like it seeing
> every
> second sample, with a blank one in between them, that could lead to
> interpolation that results in a signal at half the frequency. Sort of like
> every second sample is missing (in my case, two of every four are going
> to unused channels). I'm not too fresh on the details presently, but it
> is something this is easy to find mentioned in a standard DSP book.
>
> Best regards,
>
> Raymond
Hi everyone,
Just a word to say that Csound 5.11 is out now. Here is
John ffitch's official announcement.
Victor
======================================================
many of you may have heard the rumours, but it is true, Csound 5.11 is
now released and available from Sourceforge
The release notes are below; the notes at SF are missing GEN49
So, on with 5.12; we await the requests with interest...
==John ffitch
------------------------------------------------------------------------
Notes for 5.11
==============
New Opcodes:
tabsum to sum sections of ftables
p5glove -- not working very well yet
MixerSetLevel_i -- an init-time only version of MixerSetLevel
wiimote opcodes to allow games controller to be read directly in
Csound.
mp3in -- like diskin but reads MP3 files
doppler -- details to follow
filebit -- reports bit size of files
New Gen:
None (well actually there is a gen49 to read mp3 files)
Modified Opcodes and Gens:
Added rounding bin code to pvsscale
Added NP2 support for ftload and ftsave
GEN23 totally rewritten to be more consistent in what constitutes
a separator and comments. (Still no /* */ comments)
Bugs fixed:
Use of automatic numbering of ftables reuses table numbers
seed with positive argument was wrong
sprints with an empty string printed wrong data
mute now works with both numeric and named instruments
Comments in new parser fixed
Byteorder in loading files fixed
Small fixes in diskin, and in tablexkt
System Changes:
Revised Windows installer
SConstruct now builds completely independent shared libraries
for Python, Lua, and Java wrappers.
New Parser almost usable
Redrawing of graphs fixed so that only selected ones get redrawn.
RT-alsa more forgiving on near sample rates
It is possible to have the score generated by an external program
rather than using standard score format using
<CScore bin="translater"> to call the program translater on the
score data
lpc_export fixed
Removed limit on macro names length
PMAX, the number of arguments to a score event has been reduced
by 2, and an overflow system introduced so GENs can have
arbitrary numbers of arguments.
API:
Increased API version to 2.1.
New API function pointer ldmemfile2withCB() which is
a version of ldmemfile() allowing a callback to be set and called
exactly once to process the MEMFIL buffer after it is loaded.
csound->floatsize set; zero in earlier versions
GetChannelLock added
Internal:
usual collection of gratuitous minor changes, layout and comments
*end*
Hello, I've sent this email in July on the jack-rack-devel list but
haven't got response... I'm posting it here in the hope of some dev to
take up this idea, which IMHO is really missing from jack-rack and
would take it a step further.
[jack-rack-devel] feature request: preset change through midi
From: Renato Budinich <rennabh@gm...> - 2009-07-17 08:37
hello,
It would be great if it were possible to browse saved presets from a
separate window, and sending midi program changes to go up or down the
list. (the window is actually a detail, what i think is really missing
is the possibility to change presets from say a pedal board if one is
occupied playing an instrument)
for the rest i think jack-rack is great! Great midi implementation
Renato
Hi,
I have tried the contact form on the FFADO website and through the email
address provided in the contact pages at the SourceForge.net project page to
no avail. I'm not sure where else to ask except here. Are any of the FFADO
developers on this email group that can provide a contact email that will
garner a response?
Thanks,
Alex
--
When you gotta have it, you gotta have it. Lesson learned from days of
record shopping.
Hi,
I'm new to the list so I hope this is not the wrong forum!
I've been working on a midi keyboard ("physical" hardware 88-keys
"professional" = no toy) for a while for which I plan to release the
schematics and source as open source.
It's based around a Fatar keybed (they make Studiologic) and an Atmel
AVR mcu. The code is all in C and is very portable.
Current features are:
- Velocity sensitivity.
- Pedal support.
- Custom velocity curves.
- Only normal MIDI serial "current" link. No USB, yet...
My questions are, Is there an interest in this sort of thing..? What
features would you like to see, what are you missing from
off-the-shelf products?
Atb,
Albin
Hello everyone,
I'm new to this list. My names Paul, I'm developing a plugin in Supercollider.
It allows a user to define algorithmic processes using a GUI and trigger them via MIDI.
I have the following question, how does one go about making this available cross platform as an AU instrument or VST instrument?
It should suffice in the first instance to just receive midi note triggers.
Thanks for any pointers
Paul
Send instant messages to your online friends http://uk.messenger.yahoo.com