Plug Data does not support Ableton Link out of the box and does not allow externals to be loaded like Pure Data, so you have to use Pure Data as an external application to link with Ableton link GP.
Thank you so much - going to try out this evening!
Works like a charm, finally my LFOs in hardware synths are tempo synced to GP tempo (which in turn is sometimes linked to Bitwig and scenes with modulated tempo 
)
1 Like
Exactly the same use case I had, but I was using an external merge. Now I can use this directly in GP.
I have been looking at the Plug Data option and I think I can get a VST version running from the GP playhead, but in my tests I cannot get a clock directly out of a VST. This also seems to hold true for Cantabile, so I am guessing this is a VST or PlugData issue, as per @Frank1119 comment. So at the moment a crude test version is using the CC#102 trick.
I can also confirm that a JUCE built VST does not output MIDI Clock.
Why not? Where did you get that info?
I built a JUCE VST example that was an arpeggiator and tested it worked in GP. Knowing that I could get a clock out through a GP midi out block, I then added a MIDI clock output to the arpeggiator tested again, the arpeggiator output was there but still no midi clock.
I will take another look but a really crude method of generating a midi clock message and outputting it regardless of any consideration of time did not work, maybe you have to force in directly into the MIDI buffer???
I would be interested if anyone else can get this working?
The JUCE example is a MTC class not a MIDI clock.
Maybe in the past you could build a VST2 in Juce, but I also tried generating midi clock in a Juce plugin (VST3) and failed. BUT, it did work with a Mac AU format.
1 Like
Thanks for saving my sanity. I use Windows as well as Macs, so I had been sticking with VST3.
Itâs not really about Juce: the problem lies with vst3. Steinbergs point of view is that vsts are meant for audio and should be able to consume note messages, but arenât supposed to consume or produce cc messages. The host should handle these and route them to the parameters of the plugin. Same principle applies to start and stop midi messages, clock messages, etc. Vst2s on the other hand donât limit the plugin developer in this respect, but these are, as far as Steinberg is concerned, deprecated.
I must add that Juce 7 has a workaround for cc messages in a vst3, because Steinberg did relax the constraints for cc messages (albeit via a different interface). Juce 7 reroutes the cc messages to this new interface. This way the developer can create a vst2 and a vst3 with one code base and still have the cc messages sent. But this relaxed approach of Steinberg only applies to cc messages.
(Disclaimer: this is how I understand things from discussions at the forum of Steinberg. Itâs in line with my own experience and tests. Furthermore, Juce may have implemented the workaround earlier (for example in Juce 6), but I didnât check that. Juce 5.4.5 doesnât have the workaround.)
1 Like
Because music only has notes ---- letâs make it really difficult for developers to do anything else and to hell with something that has worked well for decades!
Sigh
2 Likes
Thatâs another way of phrasing this. 
1 Like
Which one?
1 Like