Just using the quick controls set up for Halion Sonic and I am realizing that the automation is not written under the track where the quick controls are set up but in the Halion Sonic folder. 
Quite disappointed in that set up. Very inefficient. Is there a work around?
Cheers,
James
I do sympathize, (and would find that option useful myself, sometimes), but, as you have no doubt discovered, it is the parameter itself which gets the written automation, not the Quick Controls fader (or itās remote).
If you really do need the latter, there is a workaround (although Iād hardly call it āefficientā either 
)ā¦
Bear in mind that Quick Controls is really just a special implementation of a āregularā Generic Remote Device, whose actual MIDI input is received in the Device Panel, totally independently of MIDI inputs to the Project window.
So the āworkaroundā is to create a MIDI track in the Project window, whose MIDI output can be routed (externally) to the Quick Controls (or Generic Remote) MIDI input.
That can be achieved (on PC) by running MIDI Yoke or similar, or on Mac by activating an IAC Bus in Appleās Audio MIDI Setup, and setting the output of the MIDI track to MIDI Yoke (or the IAC Bus), and setting the MIDI input of the Quick Controls Device panel to the corresponding Yoke (or IAC).
In that way, it is always that MIDI track that will be piloting Quick Controls (meaning that you can edit the MIDI track), and you donāt really even need to write-enable the resulting Quick Controls automation (although you could eventually do so, once happy with the result, and then youād have to mute that MIDI track).
ATTENTION.
this ONE Midi track, whoās output is routet through a MIDI loopback back into the QuickControl Remote Device, THIS ONE Midi tracks MIDI data then always control the Quick Controls of the CURRENTLY SELECTED TRACK!!!
if you have MIDI on that track and select another track than the one you want to control by quick control, your MIDI data might destroy some plugin settingsā¦ no undoā¦
Valid point, Tabsel 
, but that MIDI track could also be the MIDI track to which you have the desired Instrument routed. In that case, you would use a MIDI Send from that track, to the MIDI Yoke (IAC Bus). That way, at least, all is contained on the same MIDI track.
ā¦ and donāt forget that you can ALT-click on a Quick Controls slot, in order to access parameters on other tracks
(itās certainly not a āset it up once, then forget about itā situation )
hat MIDI track could also be the MIDI track to which you have the desired Instrument routed. In that case, you would use a MIDI Send from that track, to the MIDI Yoke (IAC Bus).
so that whenever you want to listen to VSTi that is driven by that MIDI track, the Quick Controls of the currently selected track are adressedā¦ perfectly āhiddenā in a send MIDI routing, so you will wonder why these fā¦ing knobs and dials of your compressor plugin on your vocal track move whenever you listen to your VSTi and editing your vocals 
be carefull
but, I guess, the OP wondered why the automation curves were not visible on the selected track, but instead on the track that the quick controls pointed toā¦
Exactly