The Yamaha EZ-EG Guitar Midi Controller Thread

[Markleford]

Hey, midiboss! Glad you're still using my tools!

1.Don't you think EZAG topic is worth it's own forum, where "subtopics" are separated for easier viewing? (Yamaha can sponsor it ). Any volunteers?

I've pondered getting a support forum here on KVR for the rest of my software. Of course Marc's stuff would be welcome too, as I use his stuff under the hood! There'd be no reason why general EZ topics couldn't be discussed there too.

Don't know if it's worth an *entire* forum/site, though! I suppose anyone who wanted could put up their own forum elsewhere, but I have noticed that people get the best of multi-use forums, whereas specific-topic forums sometimes are very dead except for the occasional question or short bursts on software version upgrades.

But the success of this thread is very interesting! It seems a few people find it due to the fact that I have a direct link from my EZ software page.

2.[...] Is there anything I can do about latency?

New soundcard, pretty much, or new drivers for your old one. And you're already using the old trick of using the original sound source to give you a better sense of timing, and then possibly adjusting the MIDI data after performance.

3.Can software be ported to VST or MFX for easier integration?

Marc was playing with the idea of porting his to VST. If I changed things, I'd only put mine in a more robust C++ application, as I like the processing to be distinctly separate from the host.

YAMAHA, wake up!!! Can't you see the big potential of your EZ- series??? EZ-PRO with SW support from Yamaha would be a hit, also "$maker"!

Perhaps someday an official rep will find this thread. But more likely they've already killed prouction of the EZ's and are just selling through their stock!

- m

[mbncp]

> Can software be ported to VST or MFX for easier integration?

The problem is that MFX doesn't support sysex and some host that support VST-MIDI don't support sysex either (ex: eXT).

So what I trying now, is to have an external app that will convert these triggers, making it possible with any host.

This app works also a little different from the previous script as I use the NoteOn event to trigger a fret down (or string velo) instead of the sysex, as this reduces latency by approximately 10 msec, and this does make a difference.
The app can also detect Capo and Tuning from the EZ guitars, and the plate from the AG.
But it's the mfx, vst plug (or the app) that converts the triggers to actual notes, so you can change play parameters after the recording (fret velo, open string velo, hammer mode, ..).

So, the idea is to have a standalone app that can send the triggers (to be used by the plugs), the converted events (like the script) or both.
The best would be that the app is actually a MIDI driver so there is no need for a virtual driver, this would make it also easier for a host that don't support Mfx or VSt-MIDI, sending the recorded triggers to the driver, then sending the processed events back to the host in a transparent way.

Now, if I have at least 10 people who would agree to buy the plugs+driver for 20U$, I start the project. (the DDK from MS to create the drivers is 199 U$ )
For people who prefer to wait and see, it should later be available for about 40U$ - 50 U$.
To pre-order (no money until it's done) or for more info , you can PM me or use the email address from this page : http://www.mypage.bluewin.ch/ncplus/midi_index.html

Edit:
Please specify also which host you are using and preferred usage:
1) Stand alone 2) VST-MIDI 3) Mfx 4) VSTMA (steinberg only MIDI plugs)

thanks ;

[midiboss]

Markleford, Marc,
thank you both. Maybe you could join forces together and make one hell of the EZ-XX software. As Marc said, he'd go commercial... Maybe a dollar or two could be earned for further projects So Marc, count me in for your "commercial" version, I also volunteer for testing...

[kara]

Hmm interesting... but why a standalone application ?
To be honnest if you developped a vst and it would be receptor compatible, I would by both. The receptor and your VST !!!

Rony

[mbncp]

Hmm interesting... but why a standalone application ?
To be honest if you developed a vst and it would be receptor compatible, I would by both. The receptor and your VST !!!
Rony

Hi Rony,
Very little applications support VST-MIDI and sysex, that's why the idea is to create a MIDI driver that sends specific message to a host and can also work as a standalone application to be used without a plugin.
I will also make a Vst version that doesn't require the driver for host that can deal with sysex in VST-MIDI. Now, I'm not sure that receptor supports VST-MIDI plugs and sysex.

.. he'd go commercial..

Well, as I said, the DDK from microsoft is 199U$ + 25 U$ for shipping, so it's more a "let's share the costs" idea, as I don't expect 50 people ordering the software.

Now, don't get to excited, I will first start with the standalone app and the VST plug. This should take about 2-3 weeks, with nothing fancy (basic GUI). Then I will create the MIDI driver (which will then replace the standalone app), once I get the Driver Development Kit, and this may take some time.
One of my main concern is to enhance the Hammer On, Pull Off routines, as I'm not really happy with the script right now. But globally we'll have options for open strings, fret down/up actions, Hammer On/ Pull Off Modes and maybe some fx like using the open string for harmonies (based on current note played), and for the VST version an anti machine gun mode ( for VSTi that support vst tuning), and some other fun stuff, just ask .

For Mac users, I will see what I can do, thought it doesn't sound simple (different OS, different plug type, ..). Maybe it's time to look for a Mac

marc

[kara]

Some great ideas in there Marc, I hope I'm still on your list of beta testers...

Rony

[mbncp]

Some great ideas in there Marc, I hope I'm still on your list of beta testers...

Rony

No problem Rony, but being a beta tester will cost you 20 bucks

Btw, I just checked the receptor site, but they're not talking about VST-MIDI support, so you would still need a laptop

But you could use the 'driver' with eXT (even if it doesn't support sysex). The idea about recording the 'triggers' allows you to tweak the settings after recording. This makes it easy to remove or change the fret velocity, boosting a single string, adjust hammer delays or whatever.
I noticed that if I change the patch/instrument after recording I have to tweak the MIDI a little, which is easier if we use the triggers instead of the processed events.

Anyway, the ezg-suite will work in standalone, vst-midi, vst-nonmidi, mfx and standalone plug mode.
Using a specific driver will make things easier than using a virtual driver (yoke, maple,..).
Sounds complicated, I know

marc

[AndrewSimon]

Anyway, the ezg-suite will work in standalone, vst-midi, vst-nonmidi, mfx and standalone plug mode.
Using a specific driver will make things easier than using a virtual driver (yoke, maple,..).
Sounds complicated, I know

marc

Hey Marc
Not sure I understand all this but you can count me in.

[spuddle]

Hey marc, really exciting ideas you have there.

I'd love to help and support you so if you ever need to get something organised with funds and such i'll be willing to help with any small-scale monetary issues you need to get started.

Keep us updated about your plans.

[warza]

I got the two software applets from Marc and Markleford running with my AG last night. Wow! This thing flies now. It's a $189 professional MIDI controler.

It took me a few tries to get everything working (the apps really need clear start up instructions), but Cubase shakes hands great with them now. Thank you for these tools!

Kevin

[eddu]

Marc,

Will you release a VSTi demo version?

[mbncp]

Marc,
Will you release a VSTi demo version?

Well, it looks like there's going to be nothing, only 5 people are interested so far, and for different versions. Coding all that would take me about 200-300 hours.
Coding the ocx for the scripts was already about 80 hours of work, the script was a good 100 hours or even more with all the extras.

I guess I'll have to learn to put myself some limits

Cheers,

marc

[manytone]

Hey Marc
I think more people just need to know exactly what a VST version etc. would do for them and also you need more time to get that idea out to people that own these.

Won't happen overnight my friend, but i think if users could actually picture what exactly you are doing and how it would make EZ better than it is now ... it might help.

But again ...Time is needed to get all that info and your concept out there

Also most guys need simple explanation and ease of use as alot will understand basic midi etc. but not all the mumbo jumbo.. Perhaps paint a simpler picture of what it all will do better than what we have now.
Heh .. I'm still getting my head around the apps we have now.... I always thaught some good videos demoing and explaining the different modes would be VERY usefull for getting into this stuff for new users and old
Paul

[AndrewSimon]

Marc,
Will you release a VSTi demo version?

Well, it looks like there's going to be nothing, only 5 people are interested so far, and for different versions. Coding all that would take me about 200-300 hours.
Coding the ocx for the scripts was already about 80 hours of work, the script was a good 100 hours or even more with all the extras.

I guess I'll have to learn to put myself some limits

Cheers,

marc

Hey marc

You can count me as two people if it helps.
$20 is not much for a script that turns our dream into reality.
Common EZ players show your support
E-mail marc now!

Marc hang in there, I am sure more people are interested than you might think, they simply did not see it yet or couldn't easily navigate to your site to copy the static e-mail link (just a little too complex and inconvenient).

[spuddle]

Gets my vote too