Found a possible way to "batch" load multiple images in bomber plus

I'm starting to see how to do alternative grid sizes in my head, but it's gonna be a bit rough on the user. Meaning you guys are gonna have to input a couple numbers for it to work properly. But for the most part, I'm seeing it as doable. The only question is: when do I sit down and get this idea out of my head when I'm already swamped with work? lol

So here's the idea I got in my head:
1. The current version of FilterForge has no way of returning x and y pixel size for color control inputs.

2. So we need to ask the user to input those numbers instead. Like if the image is 1024x768 - assuming the grid spacing is equal and divisible, we should be able to extract images piece by piece. This does require some pre-handling but this is sounding more doable than I thought of weeks ago.

3. I figure if we had pixel size value input, we can divide that by another user input to get the grid size we need to chop stuff up.

4. Seeing how it is, I'm making huge assumptions here. I'm pretty sure there's a glaring issue with the method I'm discussing. There's just no elegance anywhere in the method I just described. But my gut feeling is that it'd probably works.

That being said, not sure when I could get to it. And no promises at all. I just know that whatever's in my head is based on some previous experience with it. I can see it happening, but it's not an elegant solution.

And the randomized output. This is truly random. It is not perfected yet, the math is ugly due to the way Bomber+ deals with non-square images.

That message was really just me thinking out loud haha. It's intended for experts I figure.

For the sake of discussion and fun though let me bring it down to your understanding.

Basically for this program to work, we need to make sure FilterForge knows how to cut an image into pieces. FilterForge is able to make sense of square images because it's easy. But when we give FilterForge other dimensions, it doesn't know what to do with it. FilterForge needs more information to cut the image into small, equal sized pieces.

My suggestion and thought process was for the user (that is you) to give THAT information to FilterForge because there is no way for FilterForge to know it.

In this case, we need the information for the size of the input image in pixels. For example, 1024pixels by 768pixels will be inputs the user will provide. Now that we know that, we then tell filter forge it's divided into 4 columns and 3 rows. Now FilterForge knows how to cut the paper into small pieces or at least should know.

But it's time consuming to do all of that. It's not elegant but it works. THat's all.

I've perfected the grid image input (for square and non-square grids) and will be releasing it as a snippet on Monday.

Thanks very much Rick Duim for making this

After testing it more I have to say that is really good and well done and I have put already some examples on the filter page

But although is very good the suggestion I made before is not solved yet, as this filter only works works with square image tiles, and what I thought is that the image tiles to be cut could be 4:3 instead of square 1:1

Quote
Lexart wrote: The well done filter made by Skybase and ThreeDee is very good for square images, but I wonder if it could be also a way to use the usual digital camera 4:3 ratio grid that is maybe one of the most used and it can be seen on wikipedia as Four Thirds system

I do not know if this could be possible in some way to be able to feed a grid image of 4:3 images as for example the ones shown below

Thanks

This is of course not any kind of request or that you have to do it, is only a possible challenge for anyone that may want and can do it

BTW, if you change the particle sorting to be big on top, you can do this:

I want to thank again to FFCreator for making his tool that is very helpful

I realized this when I was making this filter (and consequently forgot to say amongst the messy world I live in), Photoshop's Contact Sheet leaves a 1 px gap no matter how hard you try. The input for all filters here will take the gap into consideration so be warned.

I'm pretty sure other apps that do similarly don't put gaps. I say rely on those.

And I can be wrong, maybe there's a setting somewhere that disables gaps completely. Not sure.

Quote
Skybase wrote: I realized this when I was making this filter (and consequently forgot to say amongst the messy world I live in), Photoshop's Contact Sheet leaves a 1 px gap no matter how hard you try. The input for all filters here will take the gap into consideration so be warned.

Well, I have not tested yet myself to make any grid using Photoshop, although I have seen other apps that can make photo grids

Thanks for explaining and be aware of this and to know that the 1 px is already considered and included

In regards to Photoshop's Contact Sheet 1 pixel gap issue, I tried a simple solution that kinda works.

So all I did was add a scale component to the end of the bomber input that scales the image up by 0.01 units which visually is around 1 pixel(ish). Please note that this is not a pixel-perfect solution, FilterForge's numbers are relative to the size of the image. Consider this a really hack solution, the type of solution that goes against my design principles! But I did it anyway because it does save time.

I also adjusted some settings for the color control input. I changed the anchor points so now it should work correctly for all output canvas sizes. I should have noticed that earlier but I guess I was too busy doing something else.

Image Loader PhotoshopFix.ffxml

It works for both. Just try it out.