Skip to main content
Eric_Engelmann
Eric_Engelmann
Inspiring
January 10, 2013
Answered

Latest Adobe Connect add-in breaks Osprey 230 video

  • January 10, 2013
  • 4 replies
  • 2422 views

If I uninstall the addin, and refuse to let it re-install, the Osprey 230 card video works great. As soon as the add-in is installed, I only get a black screen for video. Since it was Adobe that suggested the Osprey 230 for professional video feeds, I'm hoping they can update the Connect Addin to work with it.

    This topic has been closed for replies.
    Correct answer Jorma_at_CoSo

    The compatibility with the Osprey 230 card is a known bug. It will likely be resolved in a future release.

    Bug number: 3220472, 3187138, 3215650

    http://helpx.adobe.com/adobe-connect/release-note/connect-9-known-issues.html

    4 replies

    Eric_Engelmann
    Eric_EngelmannAuthor
    Inspiring
    May 23, 2013

    The Adobe Connect Addin 11.2.261.0 fixes the Osprey problem for me.

    Eric_Engelmann
    Eric_EngelmannAuthor
    Inspiring
    January 28, 2013

    Still no comment...

    U
    user717
    Participant
    January 28, 2013

    Time to write a letter to management? Nobody from Adobe feels a need to respond?

    Jorma_at_CoSo
    Jorma_at_CoSoCorrect answer
    Legend
    January 28, 2013

    The compatibility with the Osprey 230 card is a known bug. It will likely be resolved in a future release.

    Bug number: 3220472, 3187138, 3215650

    http://helpx.adobe.com/adobe-connect/release-note/connect-9-known-issues.html

    Eric_Engelmann
    Eric_EngelmannAuthor
    Inspiring
    January 22, 2013

    The Opsrey video will still work if I send it through Splitcam software, but installing another app confuses my users.

    Come on, Adobe! At least let us know you are working on it.

    If nothing is going to be done, then I can revise my startup configuration and revise my documentation to specify Splitcam as the input for Adobe Connect in my conference rooms.

    U
    user717
    Participant
    January 18, 2013

    I think many people on this board are waiting for Adobe to fix this problem.  Unfortunately, I did not see any responses from Adobe support staff so far. Hope they read this and update us on the status of this problem, and when we could expect it to be resolved.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices