[ddots-l] Re: Determining Plug-in Parameter Settings?
- From: "Nickus de Vos" <bigboy529@xxxxxxxxx>
- To: ddots-l@xxxxxxxxxxxxx
- Date: Mon, 22 Nov 2010 22:52:34 +0200
Just a joke i know that u're good and you make good music, let me know when you
resolve the problem.
-original message-
Subject: [ddots-l] Re: Determining Plug-in Parameter Settings?
From: Chris Smart <chris_s@xxxxxxxxxxxx>
Date: 22/11/2010 22:43
I realize the ear is always the final judge of sound, and the only
one that matters. But thanks anyway.
At 02:33 PM 11/22/2010, you wrote:
>I'll put it to you as i put it to my sighted peers. Listen to how
>the music sounds don't try and see how it sounds, for you listen
>to the music not to jaws. Haha feel your pain have the same
>problem and sometimes you have to set by value can't always set by
>ear. I know some sighted people who can't mix to save their lives
>if i turn off the digital mixers screen coz they can't see the
>wave. Good luck man
>-original message-
>Subject: [ddots-l] Determining Plug-in Parameter Settings?
>From: Chris Smart <chris_s@xxxxxxxxxxxx>
>Date: 22/11/2010 21:01
>
>HI folks.
>
>I have quite a number of plug-ins that display the following behavior.
>
>When in the track inspector and changing parameter values with the
>various value change keys, Jaws seems to stay one value behind.
>
>For example, if I'm adjusting a control towards its maximum, let's
>call it 10, no matter what, I can get it one step below 10,
>according to Jaws. Let's say I go up a number of times, until the
>value is reported as 9.8 and seems to go no further. then, I go
>down one key press, and Jaws reports 10, the maximum I was trying
>to reach by going up.
>
>So, how do I reliably interpret these results? Go back and forth
>on a parameter and ssume that the second to last value reported is
>indeed where the control is set?
>
>Chris
>
>PLEASE READ THIS FOOTER AT LEAST ONCE!
>To leave the list, click on the immediately following link:
>ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
>If this link doesn't work then send a message to:
>ddots-l-request@xxxxxxxxxxxxx
>and in the Subject line type
>unsubscribe
>For other list commands such as vacation mode,
>click on the immediately following link:
>ddots-l-request@xxxxxxxxxxxxx?subject=faq or
>send a message, to
>ddots-l-request@xxxxxxxxxxxxx
>and in the Subject line type
>faq
>
>
>PLEASE READ THIS FOOTER AT LEAST ONCE!
>To leave the list, click on the immediately following link:
>ddots-l-request@xxxxxxxxxxxxx?subjectsubscribe
>If this link doesn't work then send a message to:
>ddots-l-request@xxxxxxxxxxxxx
>and in the Subject line type
>unsubscribe
>For other list commands such as vacation mode,
>click on the immediately following link:
>ddots-l-request@xxxxxxxxxxxxx?subjectúq or
>send a message, to
>ddots-l-request@xxxxxxxxxxxxx
>and in the Subject line type
>faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode,
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode,
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject�q or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
Other related posts:
