Hi jorgen

When I look at the automation track in logic for the energy xt it says "not enable" on all automation prameters.!!

I think It would be better with standart midi-controller names

Logic reads names of parameters of the plugin. The name should be the controller numbers...so when I asign 74 to cutoff in a synth in energy xt...I can find controller 74 in logic

Keep up the good work

Simon
(the guy with the midi-hang problem moths ago...thanks for fixing that!!)

i noticed this too in SX2 where SX only showed empty parameters (i beleive 128 of them which is probably some kind of default value).
i think it would be a nice feature to have them 'populated' , maybe , if eXT could transmit something like "<plugin/comp_name><#of_instance>*-<controller_name>" and thus make each (if in use) available in a host.

Thats easy. The automation for midi tracks shows CC's, but audioinst tracks don't. Just make a midi track in logic, and wire it to energy XT.

I believe we have discussed this in the past, and it's a dear topic to me since I wish to be able to automate components/plugins inside eXT from the outside (inside the VST host) through the automation controls of the VST host. I can't recall that we came to any resolution on whether it was a good idea or not to implement automation forwarding through the VST automation parameters (today they just read "not enable" just as simonhans73 pointed out). Personally I think it would be a splendid idea to make good use of this automation feature.

Correct me if I'm wrong, but those automation parameters have nothing to do with midi-controllers, right? The parameters are used to automate VST plugins independently of midi (with a resolution of 32-bit float numbers, instead of the lousy resolution that is used in midi). So why involve standard midi controller naming conventions here? Why not instead set up an array of parameters into eXT and route them as you please well within eXT (the automation parameters would be called 1, 2, 3... or whatever)? So if you wish to use a automation parameter to control filter cutoff in a eXT plugin from the outside, you just route "parameter 1 -> midi cc#74 -> target plugin" (involving a conversion from VST automation parameters to midi parameters of course).

Does it make sense?

Best regards,
Tomas

Its true it would be even better if automation was more implementet in energy xt

But!!!to start with controllernames would help.!

...and ..no its not a good idea to wire it in logic with a midi instrument ( I know it would somehow solve the problem) because ....well...Is more direct if u play without...

Nah you guys just complain too much

mmhhh...its seemes that the automation names "not enable" does not mean the same as contoller 1 to 128

actually I cant automate energy xt in logic using the normal automation procedure!!??

The name energy xt respons to is "unused" 1 til 128...

I found out ..because I convertet midi controller date to logic automation data

...

Jorgen has released some "test" versions which did give us 128 parameters to automate..., but he wants to do something clever with the automation...probably something like giving instant MidiLearn to all plugins loaded inside XT ...with Max/Min scaling and inversion of course. You can still automate XT through CC#s (128x16=2048) ...do you really need to automate more than 2048 parameters? ...seriously though, this is something I definately expected before Audio and Automation tracks...

nF

Looking foreward for that!!!!