Task #9810 (new)
Opened 11 years ago
Last modified 8 years ago
Bug: Indexed colour images not imported correctly
Reported by: | rleigh | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Rendering |
Component: | General | Version: | 5.0.8 |
Keywords: | n.a. | Cc: | jburel, mlinkert |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
Affects: Importer on dev_4_4.
Does not affect: develop/4.5.
Similar to to the bug affecting the Insight viewer for indexed images (#9789), this affects the importer in the same way.
Importing Amira images, the index is imported as uint8 greyscale, rather than doing a palette lookup and importing 24bit RGB data.
Change History (10)
comment:1 Changed 11 years ago by jmoore
- Cc jburel mlinkert-x cxallan added
- Milestone changed from Unscheduled to OMERO-4.5
comment:2 Changed 11 years ago by rleigh
This is an importer issue for all 4.4.x releases.
It's a rendering issue for FS/4.5
comment:3 Changed 11 years ago by mlinkert
Keep in mind that as with #9789 this is completely expected behavior at the moment.
comment:4 Changed 9 years ago by jamoore
- Milestone changed from 5.x to 5.1.0
- Summary changed from Bug: dev_4_4: Indexed colour images not imported correctly to Bug: Indexed colour images not imported correctly
- Version set to 5.0.8
This may become a blocker for the lookup table work. Would be good to discuss with interested parties to at least see if any breaking API changes could/must happen for 5.1.0.
comment:5 Changed 9 years ago by jamoore
- Milestone changed from 5.1.0 to 5.1.1
comment:6 Changed 9 years ago by jamoore
- Cc cxallan removed
- Milestone changed from 5.1.1 to 5.1.2
In chatting with Melissa, with lookup tables deprioritized, there's no pressing need to keep this in 5.1.1; pushing.
comment:7 Changed 9 years ago by jamoore
- Milestone changed from 5.1.2 to 5.1.3
Assuming the same for 5.1.2. If anyone disagrees, feel free to take it and move to 5.1.2.
comment:8 Changed 9 years ago by jamoore
- Milestone changed from 5.1.4 to OMERO-5.1.4
Splitting 5.1.4 due to milestone decoupling
comment:9 Changed 9 years ago by jburel
- Milestone changed from OMERO-5.1.4 to 5.x
comment:10 Changed 8 years ago by jamoore
- Milestone changed from 5.x to Rendering
Does anyone know if this is a known issue? If so, we likely want to drop the "dev_4_4" from the title, since it falls into the same pot with the rest of the bugs.