-
Notifications
You must be signed in to change notification settings - Fork 52
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
Processing file bigger than 4GB on Picasso Localize #199
Comments
Hi, |
Is this a TIFF file or RAW file? The original TIFF format only supports files up to 4 GB. If you have a TIFF file larger than that, it is in the new "BigTiff" format which is not yet supported by the main Picasso (at least, it wasn't when I last checked 2 years ago). I have made a fork that implements support for BigTiff format and reads TIFF files larger than 4 GB without issues. I wanted to submit a PR into the main branch, but I just haven't had time to polish it yet. You can find here: https://github.com/scholer/picasso/tree/bigtiff Alternatively, you can also convert your large TIFF file to .RAW format and load that with Picasso instead. |
Hi, is there any plan to implement the file reader to support "BigTiff" any time soon? I have been generated a lot of (huge) datasets and it would be a lifesaver if I don't have to convert the .tif file to .raw (which also eats up my storage space very fast as now I am doubling the size of each dataset). Thanks! |
We are planning to include this file format too, however, this will come in further releases. |
Hello, |
@rafalkowalewski1 I would also appreciate bigTiff support. We have files about 4.4 GB in size and the error is: @IrrelevantNameTom Do you know what the naming of the files has to be, for picasso to load all the frames? |
Description
I need to process the localization for file bigger than 4GB, is there a way to process it with Picasso localize? I do not want to crop my movie that contains 90000 frames.
I look forward for some solution that I can try.
The text was updated successfully, but these errors were encountered: