Hey Kevin, I've been thinking(uh oh here it comes) I'll be glad to share my efforts, if you'll just answer me this:How, in depth please, are you using RealGuitar? I think that's a fair trade, and it'll help me work up a better document.
Do you use the realGuitar GUI interface, or a directized generic interface? How do you select your guitar patches? Don't worry about giving too long or involved an answer.
----- Original Message ----- From: "Kevin L. Gibbs" <kevjazz@xxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx> Sent: Friday, January 05, 2007 2:41 AM Subject: [ddots-l] Re: RealGuitar solutions
Phil, If you end up doing that, would you share it with the rest of us? K. -----Original Message----- From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On Behalf Of Phil Halton Sent: Thursday, January 04, 2007 8:51 PM To: ddots-l Subject: [ddots-l] RealGuitar solutions As I groaned in my last post, Directizer exposes all parameters for RealGuitar, but you can't use the interface to select your guitar patches. And, if you use the interface, you can select the patch, but no parameters are exposed. Such fun! Solution: each parameter has a corresponding MIDI controller number assigned to it, and the controller values set that parameter to its various values. So, by loading up controller events in a sequence with the values set, then playing the sequence to RealGuitar, it has the same effect as setting the parameters from the directized generic interface. Its kind of like using a batch file to change multiple settings in one step. MusicLabs was good enough to publish a map of parameter/MIDI controller numbers, but not the corresponding controller values for the parameter settings. using the directizer generic interface, and going one by one thru the 85 parameters(I see I'm in for a lot of grunt work here), a list of parameter/settings can be compiled and used to get around this pain in the neck. Brian, or anyone who uses RealGuitar, please spare me the trouble I've cut out for myself and tell me there's an easier way;-) This synth is so darn good, its worth the effort--but please... isn't there another way? ** To leave the list, click on the immediately-following link:- ** [mailto: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:- ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq ** To leave the list, click on the immediately-following link:- ** [mailto: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:- ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:- ** [mailto: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:- ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq