-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AJA Card support for Casparcg server #1472
Comments
Hello rakibhossensweet, Disclaimer that I am Product Manager at Bluefish444. Regards, |
AJA support could happen at some point now that their SDK is publicly accessible and MIT licensed https://github.com/aja-video/ntv2. Or as suggested already, you should consider Bluefish444 cards as they are already supported and are a better brand than the Decklinks. |
Hi AJA Technical Support here, I've been looking through the CasparCG forums, and git repo for AJA device support as we have had a couple customer come to us asking if there is AJA device support in CasparCG. If any developers are interested, we are more than happy to arrange for loaner AJA hardware to assist. If the goal of CasparCG is to maintain a 100% FOSS code-base (no proprietary blobs), we have a new repo for our MIT licensed SDK. We also have a closed-source SDK that is %100 free and can be accessed by enrolling in our developer program. If you want to arrange for loaner AJA hardware, or want to speak with us directly, call us at Thanks, |
AJA support would be nice! Best regards Tue. |
I have written source code to use the AJA Kona 4 and Kona 5 cards on CasparCG with playback and capture both, but it was developed on casparcg version 2.1. I'll develop it on the current version of CasparCG . |
Which version can you give me binary I want to try. |
Description
May broadcasters in Asia are afraid to use BMD cards because of their reliability. also, they have that card on their hand.
Solution suggestion
Please add AJA card support for I/O for Casparcg servrer.
Additional information
If you have some additional information or attachments.
The text was updated successfully, but these errors were encountered: