ons, 24 02 2010 kl. 04:02 +0100, skrev David Grundberg:
> Søren Hauberg skrev:
> > The obvious extension is to allow for
> >
> > J = imread ("myfile.tif", 3:5);
> >
>
> This is already supported. The result J is a four-dimensional matrix. I
> think it makes perfect sense.
Ahh, that is indee
On 23 February 2010 22:02, David Grundberg wrote:
>> The obvious extension is to allow for
>>
>> J = imread ("myfile.tif", 3:5);
>>
>
> This is already supported. The result J is a four-dimensional matrix. I
> think it makes perfect sense.
I tried it and it works. I would never think of a 4th di
Søren Hauberg skrev:
> tir, 23 02 2010 kl. 21:43 +0100, skrev David Grundberg:
>
>> I don't know if the underlaying tiff library supports reading single frames.
>>
>> One way to work-around any frame loading problem is to make sure that
>> all frames are loaded at once in one imread call. Maybe
On 23 February 2010 16:41, Søren Hauberg wrote:
> If I understand things correctly, you can currently do
>
> I = imread ("myfile.tif", 7);
>
> after which 'I' will contain the 7th frame of "myfile.tif". Hence, the
> class of 'I' is an array.
>
> The obvious extension is to allow for
>
> J = imre
tir, 23 02 2010 kl. 21:43 +0100, skrev David Grundberg:
> I don't know if the underlaying tiff library supports reading single frames.
>
> One way to work-around any frame loading problem is to make sure that
> all frames are loaded at once in one imread call. Maybe imread should
> read all fram
On 23 February 2010 15:43, David Grundberg wrote:
>
> I don't know if the underlaying tiff library supports reading single frames.
>
> One way to work-around any frame loading problem is to make sure that all
> frames are loaded at once in one imread call. Maybe imread should read all
> frames ava
tir, 23 02 2010 kl. 10:16 +0100, skrev David Grundberg:
> Are you running Octave 3.2 or the development version? The 3.2 suffers
> from poor imread performance. I patched octave to make imread 10x faster:
>
> http://hg.savannah.gnu.org/hgweb/octave/rev/13d382fc758b
>
> There might be a problem w
Carnë Draug wrote:
> Hi
>
> Octave seems to take a really long time to imread most of my multipage
> tiffs. Sure, I'm talking about large ones, 2500 pages of 350x300
> pixels, but still I think it's too long. More than 3 hours.
>
> I picked one image and made substacks of it with different sizes. T
Hi
Octave seems to take a really long time to imread most of my multipage
tiffs. Sure, I'm talking about large ones, 2500 pages of 350x300
pixels, but still I think it's too long. More than 3 hours.
I picked one image and made substacks of it with different sizes. The
time to read one image (one
