seanadams;253693 Wrote: > achri-d, > > I have been doing some testing just now with version 33 firmware and I > am able to sync with any word clock frequency from 1KHz to 100KHz. I > can also vary the frequency, unplug and re-plug the cable, or even set > it to rapidly sweep a wide range of frequencies (that sounds really > weird!) but it always stays synced. >
I can confirm that also with firmware 31 the transporter (set to slave) is locking correctly to 44.1 kHz and 48 kHz to an external word clock serving as master.. It also transmits these frequencies to the dac via AES. The dac locks to the frequencies sent to the transporter. Playing 44,1 kHz files with the word clock set to 48 kHz makes the sound speed up, turning off the word clock slows it down distinctly. But there is another issue: Playing 96 kHz/24bit files only creates white noise with the external word clock. The white noise is speeding up with 48kHz word clock input and shows lower frequencies at 44,1 kHz and has very low frequencies without word clock input. Interestingly now switching back to 44,1 kHz files creates the same white noise symptoms. To cure it one has to shut down the transporter completely, connect it again to the network and it is working fine again. The 96 kHz files play fine when the transporter is set to master and it transmits the information via AES to the dac correctly. I have the impression that changing the input format of the files can cause issues (if connected to an external word clock) and the transporter has to be reset fully. It is often not enough to only connect it again to the network, the best is to unplug it, wait for 20 sec and then to start again. Maybe some of the different statements in this thread have been caused with the transporter being in a different start setup when checking the different situations. Another minor issue is often occurring, which cost a lot of time to do these checkouts: Reconnecting the transporter to the network the transporter often shuts down during this procedure. One has to restart this once, twice or even three times till it is connected to the slimserver. Maybe this is of some help to solve this issue. -- mofuv ------------------------------------------------------------------------ mofuv's Profile: http://forums.slimdevices.com/member.php?userid=13768 View this thread: http://forums.slimdevices.com/showthread.php?t=39770 _______________________________________________ audiophiles mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/audiophiles
