Ignoring tile $.Tile loaded before reset

[Shaked]

Hey,

Using the demo with the Hue filter, I encountered some parts of the images being replaced with black tiles and a console message saying:

Ignoring tile $.Tile loaded before reset: //openseadragon.github.io/example-images/highsmith/highsmith_files/10/1_0.jpg

It doesn't happen all the time, but only after playing with the filter for some time.

I suspect that it happens with all the Caman filters.

Any idea why this is happening and how it can be fixed?

Thank you!
Shaked

[cavenel]

Hi,

Any progress on this issue? @Shaked did you solve it?

I have the exact same problem, which makes the plugin impossible to use.
It is quite easy to reproduce: any tile that was still loading when changing the value of the filter will be "reseted" and will never load again.

For example, go to the demo page https://pages.nist.gov/OpenSeadragonFiltering/, add the Saturation filter, and change the range faster than the page reloads. This will make some tiles black. After playing with the slider for 10 seconds, all tiles will eventually turn black.

In my personal page, the error message is:
Ignoring tile h.Tile loaded before reset: ...
instead of
Ignoring tile $.Tile loaded before reset: ...

[rmd13]

I solved this problem a long time ago. It is the attribute of synchronous in the main html. But the exact way I cannot remember. But after modify, it runs not fluently

[cavenel]

I guess you mean the loadmode to 'sync'?

viewer.setFilterOptions({
    filters: {
        processors: OpenSeadragon.Filters.BRIGHTNESS(50)
    },
    loadMode: 'sync'
});

Unfortunately, the camanJS filters are only async, so I cannot use the synchronous mode here. And in async mode I didn't find a way to avoid this bug.

[rmd13]

Another site to modify is inside the largest core openseadragon json file

[cavenel]

For now, I found that resetting the tileMatrix for each item in world, after applying a filter, removes this bug.

for ( var i = 0; i < viewer.world._items.length; i++ ) {
    viewer.world._items[i].tilesMatrix={};
}

But this is an ugly workaround with possible side effects, and I would prefer a better solution!

[NEXCO-WestUSA]

I am having the same issue... I implemented your solution, cavenel... The tiles disappear, but reload, however the filter is not applied to the reloaded tiles... Could you figure out a solution?

[cavenel]

That is surprising, could you share a bit of the code on how you apply the filter?
I use this and it works:

viewer.setFilterOptions({
    filters: [...]
});
for ( var i = 0; i < viewer.world._items.length; i++ ) {
    viewer.world._items[i].tilesMatrix={};
}

[NEXCO-WestUSA]

`function setBrightness(image, brightness){
viewer.setFilterOptions({
filters: {
items: viewer.world.getItemAt(image),
processors: OpenSeadragon.Filters.BRIGHTNESS(parseInt(brightness))
}
});
}

var rangeBrightnessBI = $("#brightnessBI");
var valueBrightnessBI = $("#brightnessBIValue");
valueBrightnessBI.html(rangeBrightnessBI.attr("value"));
rangeBrightnessBI.on("input", function(){
valueBrightnessBI.html(this.value);';
for(j = 0; j < number_of_images; j++){
setBrightness(j, this.value);
viewer.world._items[j].tilesMatrix={};
}
});`

[NEXCO-WestUSA]

The function setBrightness applies the filter, I use it because I have several pyramids in the page. I want to apply the filter to all of them. In my app, a pyramid is just a portion of the full image, so I want to modify the whole image, not only one pyramid.

This filter is linked to the slider "#brightnessBI" which value is in the element "#brightnessBIValue"

Do you have any idea on why is not working?

[cavenel]

I think everytime you apply filters on a new image, it removes the filter on the other images. You should apply all the filters on all images at once in order to make it work. That's my guess, but maybe someone else could confirm.

[NEXCO-WestUSA]

Thanks for that!

The reality is that it was working, even without your fix. So far we have changed the location of the pyramids from the sme EC2 instance where the web code is located to an S3 storage. We are requesting the images using a presigned url, and I believe it has something to do with that... I will keep researching