The Yamaha EZ-EG Guitar Midi Controller Thread

[tq]

Ah well, so it's time to experiment with my laptop...

[AndrewSimon]

Calling on MIDI-OX experts.

I would like to set up my keyboard mod wheel to act like a switch between midiyoke1 and midiyoke2.

Basically I want to play 2 instruments at the same time, switching from one to the other while playing live.

Can this be done with MIDI-OX? Without writing custom script?

Thanks

[Max el Belga]

Far from being an expert : try a midi-merge box... .. .

[mbncp]

Basically I want to play 2 instruments at the same time, switching from one to the other while playing live.

That's easy, get a second keyboard

I don't think that MIDI-OX can do this without scripting.
The main problem is that the app/script doing the switching (port/channel) has to remember where a specific note_on was sent, otherwise you'll get stucked notes.

Another trick is to map the mod wheel so it sends volume (cc7) or better expression (cc11) to the 2 ports, but inverted on one of them.
So, if the mod wheel is all the way down, port2 will be 'muted', all the way up and port1 will be 'muted'. Anything in between you'll get a mix of both.

[Markleford]

Another trick is to map the mod wheel so it sends volume (cc7) or better expression (cc11) to the 2 ports, but inverted on one of them.

Yeah, what he said. Otherwise you have the potential for hanging notes.

Could do this with my TenCrazy.com MFX CC Map, if you have a compatible sequencer.

- m

[AndrewSimon]

Pitch bend is CC1 ... correct?
What CC is the mod wheel?

[mbncp]

Pitch bend is CC1 ... correct?
What CC is the mod wheel?

Mod wheel is cc1
pitch wheel is another type (14 bits)

http://www.borg.com/~jglatt/tech/miditech.htm
then click on: The MIDI Specification

[birgerg]

Hello Marc,

I played a bit with your new trigger.default and the
switches ... (maybe you remember)
It works ok for me. I can start/ stop a loop from the same fret.
At this point I played in the EZ_AG_3.hta with the settings
for Fret Down/Uo Action ... I was not able to change the setting for
OpenStrings and OpStrOut. Are there any limitations?

Thanks,
Birger

[mbncp]

I was not able to change the setting for OpenStrings and OpStrOut. Are there any limitations?

OpenStrings settings work like this:
Play: Always play
Mute: Always mute
Auto Mute: Mute if a fret is pressed
Mute > 1 .. Mute > 11: Mute if the last pressed fret is greater than 1 .. 11.

The OpStrOut check box.
If checked, open string that would be played use the normal output range (String Velo, Out) and the one that get muted, use the 'Op.Str Out' velocity range.

In the app, when clicking a checkbox, you need to click anywhere on the form to enable the change.

[birgerg]

Ok -
I find out that if I use the right split, then this open string function
is disabled. Without the right split it's avaliable....

[mbncp]

Updated the EZ_AG 3.hta app to version 3.09

1) The 'openstring' functions are now available when using splits.
2) Added Hammer On in Fret Down Action, and Pull Off in Fret Up Action. The Velocity field is used to decrease the velocity after each 'hit'. This is beta and could influence other settings.
3) Added a new file in the 'EZ_AG_data' folder, 'StringVelo.txt' that allows per string velocity adjustment.

The 'midix.ocx' has been changed too. Make sure to replace it and run 'register.bat' again.

marc

[ugo]

marc, thank you so much for the the new hammer on / pull off functions! this is a great addition! (i was hoping you would add something like this.)

one question though...it would appear that the higher the velocity adjustment number, the more quiet the note. so a hammer on velocity of 127 is silent but a velocity of 1 is loud. this same behavoir happens with the new string velocity adjustment too. for example, raising my low E's min velocity to 100 makes it more quiet, not louder.

is it supposed to be like this or is it reversed?

-ugo

[Markleford]

one question though...it would appear that the higher the velocity adjustment number, the more quiet the note.

I believe the "velocity" number is intended as a *subtractive* factor *each* time the event is received. So if vel is 16, a hammer on is -16 quieter each time you hammer on.

(But I'm just guessing here...)

- m

[mbncp]

Hi Ugo,
It is reversed indeed (simplifies programming )
Hammer on / pull off velocities, formula is:
New velo = old velo – velocity setting
So, if the velocity setting is 5 and the last time you triggered the string the velo was 40 then you’ll get : 35 30 25 20 15 10 5 .. then nothing
Now if the velocity is set to 0, the velocity will stay the same, so you can trigger the notes for ever.
Notice that when using the hammer/pull stuff we loose the fret down/up fixed notes.
What I do is to set split to layer, then in the second layer (right split) setting I
adjust the actions , set a different channel, and check ignore string play.

Adjusting velocities in the 'StringVelo.txt':
It’s correct that to make a string play louder, decrease the max value.
The logic is like this:
The string plays velocity in the range 30 to 100, where MIN would be 30 and MAX would be 100, so the program will remap this so it plays velocity in the range of 1 to 127. But, you should not exactly adjust as much, as this should be later set using the global function String Velo , Input Range .
Here are the setting I use for my AG ( first trial, but not to bad).

Code: Select all

 '               MIN                 MAX
StrVelo(1, 0) = 10 : StrVelo(1, 1) = 110 ' String 1 (HI E)
StrVelo(2, 0) = 10 : StrVelo(2, 1) = 110 ' String 2 (B)
StrVelo(3, 0) = 15 : StrVelo(3, 1) = 100 ' String 3 (G)
StrVelo(4, 0) = 0 : StrVelo(4, 1) = 127 ' String 4 (D)
StrVelo(5, 0) = 0 : StrVelo(5, 1) = 127 ' String 5 (A)
StrVelo(6, 0) = 0 : StrVelo(6, 1) = 127 ' String 6 (LO E)

In this case , my 3 first strings (E, B, G) where to weak. So I lowered the MAX setting. But now, I had the mid-ranges velo a bit to hi, so I raised the MIN values.

Here is a graph that shows the ramp with different settings: http://mypage.bluewin.ch/ncplus/download/chart.gif

Now, in the app, if you want to use full range velo, in Input Range , which works the same way but is global to all string, set the values to something like 30-110, the actual average velocities we get from the EZ, and in the OUT field set it to 0-127.
So, the Input Range is what we have and the OUT and Op.Str Out, are what we want.

[ugo]

ah ok...cool! thanks for the explaination. i've got a setup working quite well over here now.

-ugo