The other possibility is a change in the software on the 622/722 exposes a stream issue that was being ignored before. Not saying this is the case, but it is a possibility and has happend in the past. This is a hard some to grasp. Just because something that works before a software version no longer works does not necessarly point to the problem being related to the updated software. This hold especially true with external device interfaces. Ofcourse a software update introducing a bug is one possibilities. The other is that a change in the code could have been made to make the 622/722 more strict in how it handles the interaction to the external world causing what did work before because it was being ignored to be rejected. I am not saying this is the case here.. just that it is not as black and white as one may think and personally if you want to give it the best shot at getting it fixed, contacting both sides of the stream is a good idea.