No, there’s actually two digital signals. The digital data signal from your computer to your DAC and then the digital signal from your DACs input to the input of your DAC’s DAC chip. The timing of the former is controlled by the computer and the timing of the latter is controlled by your DAC. In the case of asynchronous USB transfer, the timing of the former is completely independent and unrelated to the timing of the latter. In the case of synchronous USB transfer, the timing of the former is not independent or unrelated to the latter but is modified by your DAC’s clock recovery circuitry (typically involving some sort of PLL) after the signal is received, before the data is then passed to the input of the DAC chip.
As above, the USB digital signal is “timed” by the computer. The DDC then re-clocks it to the timing of the digital protocol its outputting. Your DAC then re-clocks it again in the case of an asynchronous protocol or modifies it with its clock recovery circuitry in the case of a synchronous protocol. This is the same as above, which is obvious if you think about it, as your DAC obviously doesn’t know (or care) whether it’s input signal has come from a computer, DDC or any other digital audio device.
The clock master of the digital signal entering your DAC chip (the only place it matters) is effectively ALWAYS your DAC, whatever your digital audio protocol/s or digital devices you have in the chain. The only difference is that your DAC is only modifying the embedded clock with synchronous protocols, rather than generating it from scratch in the case of asynchronous protocols.
G