You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a couple legacy plugins that open data as virtual stacks (File > Import > Stack From List and File > Import > TIFF Virtual Stack). However IJ2 will try to create memory resident stacks from the resulting ImagePluses. The legacy layer should detect when a legacy created ImagePlus is backed by a virtual stack and create an Img that is also of a virtual type.
I will, in the course of the work after uploading a new ImageJ2 (which required quite a few preparations in fiji-compat, Fiji_Updater and imagej-launcher). I also vaguely remember that this was fixed, but we still need to reconcile imglib2-ij with imagej-legacy... So all of this might be fixed in one monster flurry of commits.
There are a couple legacy plugins that open data as virtual stacks (File > Import > Stack From List and File > Import > TIFF Virtual Stack). However IJ2 will try to create memory resident stacks from the resulting ImagePluses. The legacy layer should detect when a legacy created ImagePlus is backed by a virtual stack and create an Img that is also of a virtual type.
Migrated-From: http://trac.imagej.net/ticket/1767
The text was updated successfully, but these errors were encountered: