For the incoming data stream not to trigger either the wave form would have to be very badly distorted on the leading edge or the overshoot would need to be in the high double figures. another possible option could be the clock recovery circuit being of mediocre design with fairly high corner stone frequency and very average PLL ability this would lead to issues and a large increase in distorted sounds if not drop outs so pretty rare for this situation to happen
Yes the alignment of the audio data to word bit data would not be ideal at all, simply as the main timing (derived from the word clocking circuitry) would be sub optimal and therefore an increase in time interval error (TIE) would occur with out question
Any wave form deviation from the normal incoming wave form that point the circuit would usually see during normal operations can result in an in jitter.
These deviations are cause by the following:-
TRANSMISSION LINE problems, impedance mis-matching all the whole line no just the cables or board connectors, circuit board embedded pathways, components in that circuit where inductors capacitors or resistors.
BANDWIDTH data line not being sufficiently capable of handling the full amount of transmitted data remember audio word clocks are a staple 10Mhz so a pretty low level data stream required, however if all of the those components that make that pathway are not up to the task then jitter will occur. We use a tool called an eye diagram to look at serial data transmission lanes and can determine by observing the decoded patterns where a great many issues actually line in the circuit.
CROSSTALK pretty obvious where other signals which should be totally isolated from the clocking sections of device actually interferes with the clock for data circuit that is connected to the clock causing introduced noise which leads to unwanted induced jitter
Data generated jitter which is caused by bad programming at the core cpu or PFGA etc this can generate ISI (intersymbal interference) induced jitter and duty cycle distortion this is quite common in either highly complex devices where a lot of processing power is required to run a device and it takes a long time for total debug or in a simple device with novice programmer skills
We have special seial data analysis tools to look at all these types of jitter problems more on that later
RANDOM NOISE
which is cause by thermal flunctations the higher the temperature the more jitter.
This next one can be difficult to understand ,shot noise which is the random movement of electrons within the circuit like black holes and large celestial bodies mbe moved by dark matter not a lot you can do to take into account for this issue!
Lastly in this section frequency noise or pink noise the lower the frequency the more noise is introduced into the design all if these items designs take into account when coming up with a new product so tradeoffs are going to happen
All of the above cited problems can cause data line data corruption problems which will lead to the Rx end of your data stream incorrectly reading the edge crossing if the data which will result in jitter factor of electronics life.
There are more items that need addressing with jitter we have just touched on the surface however that is for a later post.