[RDP] Anyone know why rdairplay sends TWO SP commands?

Dan Mills dmills at exponent.myzen.co.uk
Sat Oct 27 18:15:31 EDT 2007


On Sat, 2007-10-27 at 22:52 +0100, Dan Mills wrote:
> Ok, this one is weird (and explains a race that I thought was in caed),
> I have just build a caed with print commands turned on and am seeing
> that whenever a manual stop of a cart is issued (on the sound panel or
> on the log) the following sequence is reported:
> 
> CAE: connection 0 receiving SP 49 
> CAE: Connection 0 sending SP 49 +!
> CAE: connection 0 receiving SP 49 
> CAE: Connection 0 sending SP 49 -!
> CAE: connection 0 receiving UP 49 
> CAE: Connection 0 sending UP 49 +!
> 

Weirder and weirder....

Here is what happens as far as caed is concerned when running a segue
with no times set (so basically a play transition (you would think)):

CAE: Connection 0 sending SP 50 +!
CAE: connection 0 receiving SP 50 
CAE: Connection 0 sending SP 50 -!
CAE: connection 0 receiving LP 0 000141_001 
CAE: Connection 0 sending LP 0 000141_001 1 51 +!

<Chop a load of volume mute commands>

CAE: connection 0 receiving OV 0 1 0 0 
CAE: Connection 0 sending OV 0 1 0 0 +!
CAE: connection 0 receiving PP 51 339 
CAE: Connection 0 sending PP 51 339 +!

<Chop a load more mute output commands>

CAE: connection 0 receiving OV 0 1 0 0 
CAE: Connection 0 sending OV 0 1 0 0 +!
CAE: connection 0 receiving FV 0 1 0 0 10 
CAE: Connection 0 sending FV 0 1 0 0 10 +!
CAE: connection 0 receiving PY 51 148363 1000 0 
CAE: Connection 0 sending PY 51 148363 1000 +!
CAE: connection 0 receiving SP 50 
CAE: Connection 0 sending SP 50 -!
CAE: connection 0 receiving SP 50 
CAE: Connection 0 sending SP 50 -!
CAE: connection 0 receiving UP 50 
CAE: Connection 0 sending UP 50 +!
CAE: connection 0 receiving UP 50 
CAE: Connection 0 sending UP 50 -!

So that is 3 spurious stops on handle 50, and one spurious unload on
handle 50, something is rotten in rdairplay. 

Here is the same thing for a straightforward PLAY transition:

Note that caed initiates things by reporting a end of cart, I am not
sure this is quite right, as bulk log timing should be done to wall
clock (to ensure everything runs to time) not sample clock, but be that
as it may. 

CAE: Connection 0 sending SP 54 +!
CAE: connection 0 receiving UP 54 
CAE: Connection 0 sending UP 54 +!
CAE: connection 0 receiving LP 0 000133_001 
CAE: Connection 0 sending LP 0 000133_001 0 55 +!
<Chop block of mute commands>
CAE: connection 0 receiving OV 0 0 0 0 
CAE: Connection 0 sending OV 0 0 0 0 +!
CAE: connection 0 receiving PP 55 235 
CAE: Connection 0 sending PP 55 235 +!
<Chop more mute commands>
CAE: connection 0 receiving OV 0 0 0 0 
CAE: Connection 0 sending OV 0 0 0 0 +!
CAE: connection 0 receiving FV 0 0 0 0 10 
CAE: Connection 0 sending FV 0 0 0 0 10 +!
CAE: connection 0 receiving PY 55 145907 1000 0 
CAE: Connection 0 sending PY 55 145907 1000 +!

Which (apart from a few minor spurious mute requests), looks perfectly
reasonable. 

Hope someone can make sense of this....

Regards, Dan.



More information about the Rivendell-prog mailing list