Known Issues

[bangnoise]

These are issues for developers using the Syphon Framework. See http://forums.v002.info/topic.php?id=8 for issues with our implementations.

SyphonClient is not Key-Value-Observable for the isValid property. This will be fixed before release.

SyphonClient sometimes returns YES for isValid when it could return NO. This will be improved before release.

SyphonClient is not Key-Value-Observable for the hasNewFrame property. This will likely not change. If you need to observe this, use a new-frame handler instead.

SyphonServer is slow to publish frames when a SyphonClient with a new-frame handler is attached, or may stutter if a SyphonClient exists in an application which has hung (the blocking call will be publishFrameTexture:textureTarget:imageRegion:textureDimensions:flipped: or unbindAndPublish). This will be fixed before release.

The Framework Documentation mis-describes properties and shows internal versions of the header files. This will be fixed before release.

[bangnoise]

A SyphonClient with a very short lifetime can cause a remote app to crash. A new beta will include this fix.

Edit: Fixed in Beta 2

[bangnoise]

SyphonClients can erroneously report NO for hasNewFrame if a server emits one frame and then one more frame of a different size. This will be fixed in the next beta.

Edit: Fixed in Beta 2

[bangnoise]

SyphonClient will return unusable SyphonImages from newFrameForContext: if used with multiple contexts which aren’t shared. This will be fixed in the next beta.

Edit: Fixed in public beta.

[Author]

Posts