Skip to content
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

FileReaderModule does not use the frame metadata to create the data frame but uses the original size of the file #374

Open
kushaljain-apra opened this issue Jul 29, 2024 · 0 comments

Comments

@kushaljain-apra
Copy link
Collaborator

Describe the bug
In the FileReader Module, it does not use frame metadata that we set to create the data frame but instead uses the original size of the file to create the frame. This can be problematic in cases where we need some extra buffer space than the original file's size.

To Reproduce
Steps to reproduce the behavior:

  1. Create a frame metadata with explicit frame size like use RawImageFrameMetadata with explicit step size.
  2. Send it to external module and check the data size of the frame, it will be the original size of the file instead of the size you would expect after setting the metadata.

Expected behavior
We should be able to set frame metadata to the frame in the FileReader Module.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. chrome, safari]
  • Cuda Version [e.g. 22]
  • Architecture [e.g. x86_64, arm64]

Additional context
Add any other context about the problem here.

Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant