Quick note about midi editing
-
- KVRAF
- 4143 posts since 7 Sep, 2001 from Melbourne, Australia
Just wanted to chime in and say good job for starting to incorporate decent midi editing functions into Luna's midi editor.
Don't know if it's exactly at Muzys stage yet, but still great.
I wish more hosts would spend a little effort implementing things like Modify Keys, Modify Times, Modify Velocities etc... on selected events.
Would be nice to see the Logical Selection functionality that existed in Muzys3 as well.
This might seem like a delayed reaction, but pre-release 8.4 is the first version of Luna I've downloaded.
Regards
Caleb
Don't know if it's exactly at Muzys stage yet, but still great.
I wish more hosts would spend a little effort implementing things like Modify Keys, Modify Times, Modify Velocities etc... on selected events.
Would be nice to see the Logical Selection functionality that existed in Muzys3 as well.
This might seem like a delayed reaction, but pre-release 8.4 is the first version of Luna I've downloaded.
Regards
Caleb
Happiness is the hidden behind the obvious.
-
- KVRist
- 41 posts since 16 Apr, 2005
Thanks for reminding me that I've been meaning to ask about this
. I have not understood how to use the editor, because I don't understand the meaning of and how to use the signs '+', '%', '=', '[]' and '*' with a 'factor' between 1 and 127. Short practical explanation (or update of manual
) would be nice.
rgds,
grizzly
rgds,
grizzly
-
- KVRAF
- 1645 posts since 24 May, 2002
Ok, i'll update the manual. Good that you ask!
Very quick now:
+ = add value e.g. x + 5
% = percent e.g. x * 75%
= = set value x = value
* = multiply e.g. x * 2
[] = limit x between value1 and value 2
Very quick now:
+ = add value e.g. x + 5
% = percent e.g. x * 75%
= = set value x = value
* = multiply e.g. x * 2
[] = limit x between value1 and value 2
-
- KVRAF
- 1645 posts since 24 May, 2002
Yes, this will be remadeCaleb wrote:Would be nice to see the Logical Selection functionality that existed in Muzys3 as well.
-
- KVRist
- 41 posts since 16 Apr, 2005
Thnx!muzycian wrote:Ok, i'll update the manual. Good that you ask!
Very quick now:
+ = add value e.g. x + 5
% = percent e.g. x * 75%
= = set value x = value
* = multiply e.g. x * 2
[] = limit x between value1 and value 2
grizzly
-
- KVRAF
- 1645 posts since 24 May, 2002
-
- KVRAF
- 1645 posts since 24 May, 2002
Sorry, that must be:muzycian wrote:* = multiply e.g. x * 2
* = Random
So, e.g. you can randomize (aka "humanize") the velocity.
The higher the factor, the more random it gets.
I.e. a factor 10 adds/subtracts up to 10 to/from the velocities, at random.
-
- KVRian
- 951 posts since 14 Apr, 2004 from Maryland, USA
So I plunged into this today and quickly got confused. My best take on what this means, you tell me if I'm right or wrong!muzycian wrote:Ok, i'll update the manual. Good that you ask! Very quick now:
+ = add value e.g. x + 5
% = percent e.g. x * 75%
= = set value x = value
* = multiply e.g. x * 2
[] = limit x between value1 and value 2
- "Add Value": Add X to current value (e.g., if editing velocities, increase them all by X)
- "Percent" asks for a percentage and a reference. I don't get this one at all: how do either the percentage or the reference relate to the current value?
- "Equal" means make the relevant parameter of all selected items equal to the specified value.
- "Range" means scale (?) the existing range to the specified range (e.g., if currently velocities ranged from 75-95, you could achieve some compression by specifying a range of 80-90).
- "Random" means modifying the existing values by randomly adding or subtracting a random value between 0 and a factor, where factor <=127 (maximum value of a MIDI parameter), with the result presumably constrained to be 0 <= result <= 127.
Do I have that about right? My two biggest points of uncertainty are the percentage function, and whether the range function actually scales values. Maybe I'm just dense on this stuff, as I've not done very much MIDI editing in any program in the past, but from where I sit, the explanations in the LUNA documentation need to be a little more expansive.
DaveL
You can twist perceptions, reality won't budge.
-- Rush Show Don't Tell
-- Rush Show Don't Tell
-
- KVRAF
- 1645 posts since 24 May, 2002
Suppose your velocity value is 70."Percent" asks for a percentage and a reference. I don't get this one at all: how do either the percentage or the reference relate to the current value?
Now you set 150% with reference 0 => Result = (70-0)*(150/100) = 105
Now you set 150% with reference 40 => Result = 40+((70-40)*(150/100)) = 85
The reference is an important parameter as it defines from where on you want to apply the percent.
For velocities this may be 0 most of the time, but the reference is definitely an important parameter when changing event times.
If you find the reference parameter too difficult, leave it at 0, and then it won't hurt.
no, values are just limited within the range.- "Range" means scale (?) the existing range to the specified range (e.g., if currently velocities ranged from 75-95, you could achieve some compression by specifying a range of 80-90).
if velocity is 70, and range = 80-90, result will be 80
correct.- "Random" means modifying the existing values by randomly adding or subtracting a random value between 0 and a factor, where factor <=127 (maximum value of a MIDI parameter), with the result presumably constrained to be 0 <= result <= 127.
-
- KVRAF
- 1645 posts since 24 May, 2002
-
- KVRian
- 951 posts since 14 Apr, 2004 from Maryland, USA
The last example starts sounding way too much like how my taxes are computed.muzycian wrote:Suppose your velocity value is 70."Percent" asks for a percentage and a reference. I don't get this one at all: how do either the percentage or the reference relate to the current value?
Now you set 150% with reference 0 => Result = (70-0)*(150/100) = 105
Now you set 150% with reference 40 => Result = 40+((70-40)*(150/100)) = 85
Maybe I just like options, but it seems like a scale vs. limit option might make this a more flexible / useful manipulation.muzycian wrote:no, values are just limited within the range.- "Range" means scale (?) the existing range to the specified range
if velocity is 70, and range = 80-90, result will be 80
DaveL
You can twist perceptions, reality won't budge.
-- Rush Show Don't Tell
-- Rush Show Don't Tell
-
- KVRAF
- 1645 posts since 24 May, 2002
I know you're joking but about the Percent operator:DaveL60 wrote:The last example starts sounding way too much like how my taxes are computed.muzycian wrote:Suppose your velocity value is 70."Percent" asks for a percentage and a reference. I don't get this one at all: how do either the percentage or the reference relate to the current value?
Now you set 150% with reference 0 => Result = (70-0)*(150/100) = 105
Now you set 150% with reference 40 => Result = 40+((70-40)*(150/100)) = 85![]()
Just leave the reference zero. Then it's very simple: e.g. 150% of 70 = 105
True, i also think Scaling might be more interesting than Limiting.Maybe I just like options, but it seems like a scale vs. limit option might make this a more flexible / useful manipulation.muzycian wrote:no, values are just limited within the range.- "Range" means scale (?) the existing range to the specified range
if velocity is 70, and range = 80-90, result will be 80
But what input range should be taken then? That's needed to calculatethe scale factor.
Should that always be full scale, ie 0-127 for velocities? I guess that's the only option.
Would you keep the "Limit" option, or just replace it with "Scale"?
What character symbol could i use for scaling? Limit = [], Scale = ? -> maybe ()
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
How about:
"..." as the symbol.
It takes a lower and upper bound for the output values.
It reads all the input events to determine the input lower and upper bounds.
Then it scales all the input event values evenly to fall within the output values.
"..." as the symbol.
It takes a lower and upper bound for the output values.
It reads all the input events to determine the input lower and upper bounds.
Then it scales all the input event values evenly to fall within the output values.
-
- KVRAF
- 1645 posts since 24 May, 2002
Huh, i don't see the link with "Scaling"?pljones wrote:How about:
"..." as the symbol.
Yes, that sounds goodIt takes a lower and upper bound for the output values.
It reads all the input events to determine the input lower and upper bounds.
Then it scales all the input event values evenly to fall within the output values.
I'll add it to the WhishList.
As you know, some other things dominate the WhishList (working on one of the Big Things these days
-
- KVRian
- 951 posts since 14 Apr, 2004 from Maryland, USA
PL expressed what I was thinking. Not what I'd call a high priority.
I think I like [] for limiting and <> for scaling.
DaveL
I think I like [] for limiting and <> for scaling.
DaveL
You can twist perceptions, reality won't budge.
-- Rush Show Don't Tell
-- Rush Show Don't Tell
