Hi Creedon. Yes, I’d say it’s doable!
The problems described in this thread were resolved in my case once my MIDI network cabling was properly configured.
MIDI is a serial data stream, and MIDI clock seems to behave globally, not addressed to specific devices.
At some point in the process I had wondered how the devices parse clock signals. Apparently they don’t.
I had to draw diagrams of the various attempted configurations before realizing that a clock signal entering a network from two directions, or remerging after being split, will have these negative confusing effects on downstream devices.
I highly recommend drawing out your network.
I rewired my network with a Thru box (splitter) immediately after the USB interface and Merge boxes elsewhere.
One of the Mergers has my foot controller group at one input and BeatBuddy at the other, with Merger output to the GT-Pro.
If I don’t feel like booting my PC, BeatBuddy is master clock for the effects. When working with PC, the application is master; BeatBuddy and effects slave to that.
One compromise I’ve made is that the D-05 won’t be asked to provide clock, at least until I feel a need for that and a willingness to revisit my cabling.
One other important note about clock that I’ve discovered in my network:
In order for me to use GT-Pro’s software editor, its USB driver has to be enabled in the PC, of course.
However, the driver gives clock input priority to the USB, disabling clock reception over the 5-pin MIDI cable.
For this reason, I have to disable the driver when slaving GT-Pro to BeatBuddy, etc.
MIDI note data and Control Change messages/values are addressed to specific devices/channels, so being sure that you’ve avoided the clock conflicts above, you should have good success.