-
Notifications
You must be signed in to change notification settings - Fork 7
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
Bayer RG 8 supported? #1
Comments
Could you please prepend your pipeline with
It shouldn't be (though it is possible that they changed the pixel format strings, it's been a while). PylonViewerApp is (or used to be) a 1:1 GUI implementation of the API. Bayer was a weird one though, because it would default to Bayer8 BG by default, and the way to change this in the API (at least for our cameras) was by using the Reverse X and Reverse Y functionality. To do this with this plugin for RG you would need to set the |
@zingmars this is the output of your suggested pipeline:
I am using "pylon 5.0.12 Camera Software Suite Linux x86 (64 bit)". |
Weird. I'll look into it, but I can't promise much since I don't have access to Basler cameras at the moment. |
@zingmars How would I go about to check the supported formats of my camera? PylonViewerApp only gives me "human readable" versions of it. |
The human readable versions correspond with API's pixel format enum ( Sadly the plugin doesn't offer a way to list all of the formats available. To do this, you would probably make your own tester. If you have some programming background, the bool getFormats(Camera_t& camera)
{
GenApi::NodeList_t Entries;
camera.PixelFormat.GetEntries(Entries);
for (size_t i = 0; i < Entries.size(); i++)
{
GenApi::INode *pNode = Entries[i];
if (IsAvailable(pNode->GetAccessMode()))
{
GenApi::IEnumEntry *pEnum = dynamic_cast<GenApi::IEnumEntry *>(pNode);
std::cout << pEnum->ToString();
}
}
} |
Is there any solution available for Bayer RG 8. I am facing the same problem with acA4112 -8gc camera. I tried flipx=true and flipy= true but still facing the same. Kindly help |
@zingmars Used it several months, with RGB imageformat until I get the old camera which support Bayer only. |
Fork and make a PR.
…On Mon, Aug 19, 2019, 13:44 faerics ***@***.***> wrote:
@zingmars <https://github.com/zingmars>
This plugin is currently *not* supporting any Bayer format due to
incorrect choosing of a filter.
Used it several months, with RGB imageformat until I get the old camera
which support Bayer only.
Successfully patched your plugin, ready to make a PR. Should I fork your
repo or I can create new branch in this one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AAG75BTZSBPSOQ5OP2JSRVTQFJ2PFA5CNFSM4FMYQ3I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4SPGJI#issuecomment-522515237>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAG75BS2TKCASDACRDO5VETQFJ2PFANCNFSM4FMYQ3IQ>
.
|
@petergerten if this is still relevant, could you try it again with the latest version? |
Hi,
I have a acA720-520uc camera using Pylon 5 and can select "Bayer RG 8" in the PylonViewerApp.
When trying to use it with gst-pylonsrc, I get:
start:<pylonsrc0> error: Camera doesn't support Bayer8.
The pipeline works with rgb8 without issues.
I wonder if the "Bayer RG 8" format listed in the PylonViewerApp is somehow different from "bayer8" here?
Peter
The text was updated successfully, but these errors were encountered: