Bug 4436 - No AES output when wordclock signal is disconnected then reconnected
: No AES output when wordclock signal is disconnected then reconnected
Status: CLOSED FIXED
Product: SB Transporter
Classification: Unclassified
Component: Hardware
: unspecified
: Macintosh MacOS X 10.4
: P2 normal (vote)
: 7.1
Assigned To: Sean Adams
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-29 09:06 UTC by Frederic Le Bas
Modified: 2008-08-04 14:02 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Le Bas 2006-10-29 09:06:03 UTC
Slimserver version used : 6.5.1 SlimServer_6.5_v2006-10-28.dmg
Transporter firmware updated with firmware included with slimserver. 

Initial setup
- connected Transporter word clock input to a 44.1 kHz word clock
- connected Transporter AES output to Tact RCS 2.2X AES input
- powered up Transporter
- selected word clock as reference

Works OK. 

Steps to reproduce the problem :
- disconnect word clock input
- reconnect word clock input
There is no usable signal on the AES output

If clock reference is set to internal clock, it works. 
If clock reference is set to external word clock (with clock on and cable connected), no AES output. 

The transporter has to be hard reset (unplug power cord) to get a signal on the AES output. 
Not very important but can cause a big loss of time. 

I think that problem is hardware or firmware related ant that SlimServer OS is not important. 


Frederic
Comment 1 Chris Owens 2006-11-01 14:05:04 UTC
Richard, is this something that could be fixed in firmware somehow, or is it truly a hardware issue?
Comment 2 Richard Titmuss 2006-11-14 02:29:15 UTC
I think this may be a xilinx issue. Will need to check with Sean.
Comment 3 Blackketter Dean 2007-10-26 09:24:34 UTC
Sean: can you comment?
Comment 4 Blackketter Dean 2007-11-25 10:55:33 UTC
Sean, any thoughts?
Comment 5 Sean Adams 2007-11-25 13:30:57 UTC
No idea, but I am revisiting a bunch of this stuff in the next couple of weeks and will look at this case. 
Comment 6 Blackketter Dean 2007-12-27 11:46:21 UTC
Sean is working on this.
Comment 7 Sean Adams 2008-01-31 16:44:56 UTC
Could not reproduce this issue in trunk 17060 / firmware 40. Either the cause of it has been fixed in FW40, or it was some other problem with the setup.
Comment 8 James Richardson 2008-04-29 11:28:37 UTC
Changing fixed target to 7.1 as FW 40 will be released then, not in 7.0.1
Comment 9 Chris Owens 2008-07-30 15:32:51 UTC
This bug has now been fixed in the 7.1 release version of SqueezeCenter!  Please download the new version from http://www.slimdevices.com if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.