Ilan Gold

No I think it's time to create some sort of option for showing or hiding the controls if the data is not interleaved but 3 channels/8bit. You're not the first...

My concern about looking at the names is if people name things something like "red" or "g"

@andreasg123 If I understand you right, I think you are right that the number of channels in an image can be greater than 6. However the number of channels can...

Ok @andreasg123 that can be done.

Apparently, deck.gl offers hooks to temporarily change blending parameters per draw call: https://github.com/visgl/deck.gl/discussions/5450#discussioncomment-355534 See: https://github.com/visgl/deck.gl/blob/b1a068120e53220892616b0977de4d27c49913b2/modules/core/src/lib/layer.js#L742-L751 This needs serious consideration. The likely thorn in our side appears to be the additive...

Is this a standardized format? Looking at the PR, there is a CSV but who makes that? I see you comment [here](https://github.com/hms-dbmi/viv/pull/610/files#diff-4007bd4ffba0b764b00852047369fac9a5d1763a391373128fecc380f15519ddR61) that it "only supports flat tiffs" but who...

Right yes! Ok! I thought the name looked familiar! @keller-mark and I are in the process of updating Vitessce right now to allow for registering custom loaders and much more...

So, I'd say, fear not, because your code will get used somewhere **and** you can stop maintaining two forks!

I think what @keller-mark is saying is that you get to keep the loader in your repo, unfork viv/vitessce, and then just "register" the loader as a plugin file type...

Ah sorry yes @keller-mark you're right. I think we would be willing to accept a PR for just generic TIFFs but I am not sure what level of abstraction would...