b-side wrote:Hi Dimal,
I don't think you are looking at this from the right angle.
Did MyTek test your ADC192 and test recording digital >88.2KHz on a Windows 7 64 bit machine?
Any testing they did short of your exact use case is irrelevant to addressing your issue. I/O or other electronic testing is great but if the driver they wrote for your OS is junk all those tests mean nothing. For the price of the unit THEY should be writing a custom driver for YOU to get this to work, not the other way around.
G'day "b-side"...
I'm very happy with the response from Mytek. They went out of their way and purchased the same hardware I have, assembled it and ran it with the same setup I have. I don't think you can ask for anything more than that.
They proved, without doubt and to my satisfaction, that the ST192 ADC is producing an exceptionally reliable clock pulse at all sample rate frequencies the unit is rated for.
Essentially, the ST192 ADC is nothing more than a Sig-Gen in this situation, it is not a comm's device sending
and receiving data, only sending. It works without fault on a current Mac and now on my machine running WInXP - It's the receiving end of the data stream that needs to be up to the task, not the other way around, in this case...
b-side wrote:The earliest Tascam and E-Mu 64 bit drivers all had sync or dropout issues until they fixed them. Sounds like MyTek may be in the same boat. If this were truly a known MS 64 bit issue, you can bet there would be plenty of discussions about it on MS and recording forums. But there aren't, other than this one. MS is an easy target.
Actually there are plenty to be found - I've been searching for solutions for months and there are hundreds of Win7 X64 instances of failure with this sort of combo and not Mytek in particular.
It is definitely a Windows 7 or Win7 Drivers issue and I'm not going to waste my time trying to differentiate between them.
Mal.