|
Thanks, Iain. Right on again.
What I now recall is: either
1) I always start with controllers at zero;
or
2) After csound is running, turn any controller that
doesn't start at zero to its initial level, *then* play my first
note.
Actually, I always use midiin with an always-on instrument
that spawns values for the other always-on instruments. Then doing the above is
far more intuitive.
Art Hunkins
----- Original Message -----
Sent: Tuesday, July 07, 2009 1:53
PM
Subject: [Csnd] RE: Re: RE: Initializing
and scaling MIDI controlled values
Hi Art (and Charles),
Unfortunately this won't work and
kdelay will adopt an initial value from the controller minimum (in this case
zero) unless initc7 is set. I just checked it!
kdelay will jump to it first
received new value because it is unaware of the initial physical locations of
the hardwares sliders. (even pointing your webcam in the direction of your
MIDI controller doesnlt help.) I borrowed one of those Behringer controllers
with motorised faders one time and Csound was able to 'tell' the Behringer
what initial locations to set its sliders to. I can't say I ever used this
feature other than as an experiment...
Bye,
Iain
From: abhunkin@uncg.edu
To: csound@lists.bath.ac.uk
Date: Tue, 7 Jul
2009 13:13:07 -0400
Subject: [Csnd] Re: RE: Initializing and scaling MIDI
controlled values
Charles,
Along with what Iain has said:
I think also that (with respect to your first
point)
kdelay init 1
kdelay ctrl7 8,13,0,4
*might* work.
Whichever way you go there still may be a
problem:
When you first move the slider, kdelay will immediately
*jump* to the new value.
As a result, I always specify either:
1) Presetting sliders to zero, or
2) Presetting sliders to initial values,
all before starting Csound.
Art Hunkins
-----
Original Message -----
Sent:
Tuesday, July 07, 2009 12:30 PM
Subject:
[Csnd] RE: Initializing and scaling MIDI controlled values
Hi Charles,
1. You have to 'fool' Csound into thinking
that a midi controller has been moved to an initial position, otherwise it
assumes it is at its minimum position. 'initc7' will give Csound an initial
position for that MIDI controller (0=min,1=max). For an initial value of '1'
in your case, use:
initc7 8,13,0.25
(1-0)/(4-0)
in
instrument 0
2. As I understand it, you want pan controller movement
to the right to transpose up to +2 octaves, to the left to transpose to -2
octaves and in the centre no transposition.
You can you 'oct' format to
quickly implement this:
;init. set at midway position
initc7
8,12,0.5
;;
;transposition in octaves
koct ctrl7
8,12,-2,2
;convert to a frequency rescaling ratio
kscale =
cpsoct(8+koct)/cpsoct(8)
Bye,
Iain
> Date: Tue, 7 Jul
2009 10:52:50 -0500
> From: chasgran@gmail.com
> To:
csound@lists.bath.ac.uk
> Subject: [Csnd] Initializing and scaling
MIDI controlled values
>
> I'm sure this info is out there, but
if someone could help or point
> that would be great!
>
>
> 1. If I have a value like a time value for delay:
>
>
kdelay ctrl7 8,13,0,4
>
> do I need to use initc7 to create the
initial value, or is there
> something else I can use? I can't seem to
do something like:
>
> kdelay = 1
> kdelay ctrl7
8,13,0,4
>
> so that kdelay will stay at one until I move the
knob.
>
>
> 2. If I'm using a controller for pvscale to
do realtime transposition
> and I want my panpot which I'm controlling
with
>
> kscale ctrl7 8,12,0.25,4.
>
> What I'd
really like is to equally divide the controller with 2
> octaves on
either side, so full left is 15va below, full right is 15va
> above
and center is 1.
>
>
> Charles
>
>
>
Send bugs reports to this list.
> To unsubscribe, send email
sympa@lists.bath.ac.uk with body "unsubscribe csound"
Windows Live™: Keep your life in sync. Check
it out.
Insert movie times and more without leaving Hotmail®. See how. |