feat: write meta channels in PSD files #8393

arturo32 · 2025-10-08T12:07:52Z

arturo32
Oct 8, 2025

ImageMagick version

7.1.2-3

Operating system, version and so on

Linux

Description

There are several issues and discussions about problems when converting files to and from PSD: they are about "alpha" channels being lost or ignored. These "alpha" channels are, most of the time, meta channels that the PSD format support, but IM seems unable to read and work with them.

I have seen some discussions about "multispectral images" and the support for PSD files (which would imply support for meta channels as well) is always cited together with TIFF files, but this seems not to be the case. I can create meta channels for TIFF files without a problem with IM, but not for PSD files.

My use case is that I want to create and save a meta channel called "white" for a DTG printer in a PSD file. This channel is also called a "spot channel". I accept that IM can't change the name for meta channels but if it could at least support their existence for PSD files that would be nice.

Where would someone go (as in edit some code file) to make this feature possible? How difficult it may be to implement it?

Related discussions and issues:

snibgo · 2025-10-08T14:48:13Z

snibgo
Oct 8, 2025

Your request is not clear. Do you want IM to write an image that contains meta channels to a PSD file? Or something else?

From the code in coders/psd.c, IM can read meta channels from PSD files, but can't write meta channels to PSD files. To do this, I suppose WritePSDChannels() would need to be modified, stepping through the meta channels. I don't know how difficult that would be.

2 replies

arturo32 Oct 9, 2025
Author

Your request is not clear. Do you want IM to write an image that contains meta channels to a PSD file? Or something else?

Exactly, I want IM to write a PSD file with meta channels. Something like this:

./magick original.psd  \( +clone -negate \) -channel-fx "| gray=>meta0" out.psd

Currently the command above works fine with TIFF files and the new meta channel shows up as "TIFF channel" in GIMP. A meta1 channel shows up as "TIFF channel #1" and so on.

I do wonder if the secret for writing meta channels in PSD is in TIFF's WriteTIFFChannels() function...

arturo32 Oct 9, 2025
Author

In the TIFF code, WriteTIFFChannels() can be called with multiple QuantumType values, one of which is called MultispectralQuantum, when the number_meta_channels is greater than 0:

ImageMagick/coders/tiff.c

Line 4181 in 98686c7

status=WriteTIFFChannels(image,tiff,tiff_info,quantum_info,

In the PSD code, WritePSDChannel() can be called with IndexQuantum, GrayQuantum, RedQuantum, GreenQuantum, BlueQuantum, BlackQuantum, AlphaQuantum, but it is never called with MultispectralQuantum.

arturo32 · 2025-10-09T03:13:42Z

arturo32
Oct 9, 2025
Author

Naively I just added the code below just after line 3306 of the psd code and of course it didn't work. But I think I'm on the right track... Maybe just something wrong with the rows calculations etc, I really didn't think much about it.

ssize_t
    number_meta_channels;
QuantumInfo
  *quantum_info;
ssize_t
  i;
number_meta_channels=(ssize_t) channels-psd_info->min_channels;
if ((image->alpha_trait & BlendPixelTrait) != 0)
  number_meta_channels--;

quantum_info=AcquireQuantumInfo(image_info,layer);
for (i=0; i < number_meta_channels; i++)
{
  (void) SetQuantumMetaChannel(image,quantum_info,i);
  length=WritePSDChannel(psd_info,image_info,image,layer,
    MultispectralQuantum,compact_pixels,rows_offset,separate,compression,
    exception);
  if (separate != MagickFalse)
    size_offset+=WritePSDSize(psd_info,image,length,size_offset)+2;
  else
  {
    rows_offset+=(MagickOffsetType) offset_length;
    total_length+=length;
    break;
  }
  total_length+=length;
}
(void) SetQuantumMetaChannel(image,quantum_info,-1);

0 replies

arturo32 · 2025-10-09T23:19:09Z

arturo32
Oct 9, 2025
Author

I was looking at commits in the TIFF coder file and... wow, the full support for meta channels in TIFF is only 4 weeks old!! I also decided that this is a bit beyond my knowledge so I hope someone else will take this task 🙏

0 replies

arturo32 · 2025-11-10T11:59:03Z

arturo32
Nov 10, 2025
Author

Can I have the confirmation that this is possible with PSD files from one of the developers? Like, the only thing that prevents ImageMagick support this feature is just the time to implement it and that an implementation of this feature would be very similar with how the write to metachannels were implemented for TIFF files?
I know that @dlemstra implemented this feature for TIFF files, could you give some feedback on this?

0 replies

dlemstra · 2025-11-10T19:57:30Z

dlemstra
Nov 10, 2025
Maintainer

The answer now is maybe? I haven't made time to investigate this yet. The PSD format is complicated and I don't have Photoshop to test changes I would make. We do support reading meta channels so I suspect we could also write them in the same way.

6 replies

arturo32 Nov 11, 2025
Author

I'm currently using GIMP to test meta channels in TIFF files (I used Krita, but it's useless for metachannels).
The ideal solution for me would be to also name them. My plan is to implement "write metachannels to PSD files" first and then try to add "named metachannels" to both types of files afterwards, in another submission.

(again, I say "I" but I also don't know when I'll have time to Try to implement this)

(also, while I'm here, how can someone print something in the stdout for debugging while developing? Is there a easy way or is better to use proper debugging tools? :) )

arturo32 Dec 3, 2025
Author

Hey, if I wanted to hard code a name to any meta channel in the source code... Would that be easy? We are kind desperate trying to write spot channels in PSD files..

In Photoshop the names sometimes change to "Alpha 1" or "Alpha 2" for meta channels created by ImageMagick. They are, or course, not "photoshop's spot channels", which is a thing...

fmw42 Dec 3, 2025
Collaborator

As far as I know, Imagemagick can only write to meta channels in TIFF. It does not support that in PSD. Furthermore, Imagemagick knows nothing about spot channels. The IM developers can correct me if I am wrong.

arturo32 Dec 4, 2025
Author

I'm really sorry for the confusion. The end goal of my team is indeed to add spot channels to psd files. I already accepted that ImageMagick can't do that. My mind was a little bit confused when I was writing my last comment.

What I truly want to know is that if I can, with some ugly code, modify the source code of ImageMagick so that any metachannel it writes in a TIFF file would have a name like "white" in Photoshop instead of "Alpha 1". I understand if this is complex, I'm just asking in the hope of an answer like "oh, you just need to modify this one line" or "ah, you can just use the magick command that modifies any meta data...".

I'm really sorry for the time taken and notifications...

fmw42 Dec 4, 2025
Collaborator

I am sure that can be done. But I do not know how. One of the IM developers would have to comment.

snibgo · 2025-12-04T14:50:47Z

snibgo
Dec 4, 2025

... modify the source code of ImageMagick so that any metachannel it writes in a TIFF file would have a name like "white" in Photoshop ...

I don't think there is a simple answer.

I suggest you find or make a TIFF file with named channels. Using tiffinfo and exiftool, identify which tags store that metadata. If the tags are public (eg InkSet, NumberofInks, InkNames) then they should be documented in the TIFF 6.0 specification. If they are private Photoshop tags (eg AlphaChannelsNames), they may be documented in https://exiftool.org/TagNames/Photoshop.html .

With luck, you then know which tags you need to add to TIFF files, so you can modify your copy of ImageMagick.

0 replies

snibgo · 2025-12-05T15:14:46Z

snibgo
Dec 5, 2025

@arturo32: Attached is x.zip which contains x.tiff, which is has an image with 4 meta channels, each with a name (I hope).

I don't have Photoshop, and can't test this.

Please read this with Photoshop, and see if it can read the names.

x.zip

3 replies

fmw42 Dec 5, 2025
Collaborator

snibgo: I do not see any attachment. I have PS and could test.

snibgo Dec 5, 2025

Oops, sorry. Edited.

fmw42 Dec 5, 2025
Collaborator

I see meta channels in PS labeled: abcd, snibgo and abd

fmw42 · 2025-12-05T18:16:34Z

fmw42
Dec 5, 2025
Collaborator

If someone wanted to implement this in Imagemagick, one could consider adding defines for tiff and psd for the meta channel names when using -channel-fx.

0 replies

snibgo · 2025-12-05T18:29:38Z

snibgo
Dec 5, 2025

Okay, good. I have recorded the names in the AlphaChannelsNames metadata. It doesn't need any changes to ImageMagick.

AlphaChannelsNames is a Photoshop tag within a 8BIM profile. IM can write a 8BIM profile. Beware: the 8BIM profile is used for many purposes, and if it already exists, this process will entirely replace it with just the AlphaChannelsNames.

The 8BIM profile is a sequence of (binary, not text) bytes that start with the magic characters "8BIM". The following C program wrAlpChNm.c will write the profile to stdout. It constructs the profile from 4 channel names: "abcd" etc. The program can be enhanced to take the names as program arguments, or the equivalent code can be put inside IM as a -define, or whatever.

/* Write to stdout a Photoshop 8BIM profile for Alpha Channels Names (AlphaChannelsNames).

   This program wrAlpChNm.c is a hack, for proof of concept.

   This program is public domain.
   It may do nothing useful, or may cause harm.
   Use at your own peril.

   References:
     https://exiftool.org/TagNames/Photoshop.html
*/

#include <stdio.h>
#include <string.h>
#include <stdlib.h>

#define MaxLenNames 256

typedef struct {
  size_t nUsed;
  unsigned char Chars[MaxLenNames];
} NamesT;

static NamesT Names;

static void AddName (const char * Name)
{
  size_t i;
  size_t Len = strlen (Name);
  if (Names.nUsed + Len >= MaxLenNames) {
    printf ("MaxLenNames is too small.\n");
    exit (1);
  }
  if (Len == 0 || Len > 255) {
    printf ("Each name must be less than 256 characters.\n");
    exit (1);
  }
  Names.Chars[Names.nUsed] = (unsigned char)Len;
  Names.nUsed++;
  for (i=0; i < Len; i++) {
    Names.Chars[Names.nUsed] = (unsigned char)Name[i];
    Names.nUsed++;
  }
}

static void Wr8bim (void)
{
  size_t i;
  int NeedPadByte = (Names.nUsed % 2 == 1);

  fputs ("8BIM", stdout);
  fputc (0x03, stdout);
  fputc (0xEE, stdout);
  fputc (0x00, stdout);
  fputc (0x00, stdout);

  /* Write the length of the names as 4 bytes, MSB order.*/
  fputc (0x00, stdout);
  fputc (0x00, stdout);
  fputc ((int)(Names.nUsed / 256), stdout);
  fputc ((int)(Names.nUsed % 256), stdout);

  /* Write the names. */
  for (i=0; i < Names.nUsed; i++) {
    fputc (Names.Chars[i], stdout);
  }

  if (NeedPadByte) {
    fputc (0x00, stdout);
  }
}

int main (void)
{
  Names.nUsed = 0;

  AddName ("abcd");
  AddName ("snibgo");
  AddName ("abc");
  AddName ("snibg");

  Wr8bim ();

  return 0;
}

Compile the program, then run it like this, directing stdout to any file:

wrAlpChNm >8bim.bin

To test this, I make an image with 4 meta channels, and assign the names from the profile:

magick -size 100x100 gradient:blue-red -channel-fx "red=>meta0,blue=>meta1,red=>meta2,blue=>meta2" -profile 8bim.bin x.tiff

"exiftool x.tiff" reports:

Alpha Channels Names            : abcd, snibgo, abc, snibg

4 replies

fmw42 Dec 5, 2025
Collaborator

snibgo: If an 8BIM profile already exists can you not copy it, edit it for the names and then replace the old on with the edited one?

snibgo Dec 5, 2025

Yes, and that is how it should be done, by modifying coders/tiff.c in IM. My work above is just to test the concept.

fmw42 Dec 5, 2025
Collaborator

I do not know how to find any other meta channels other than what shows in the PS window. Are you sure you created 4 extra channels? My Mac Ventura is not fully compatible with PS 2025 - I get a message about that from PS. I would need to upgrade my Mac. But I doubt that would affect the number of extra channels that I get in PS. If one shows, it is likely showing all that it finds.

arturo32 Feb 13, 2026
Author

I expanded your code to add ChannelOptions information (more specifically, the kind of the channel - a Spot Color). It was very hard for me because I never did something similar to this. There is some mysterious bytes that I don't know why they are there, I have to tinker a lot to discover that they are necessary haha. I probably get the "pad byte" wrong too:

/* Write to stdout a Photoshop 8BIM profile for Alpha Channels Names (AlphaChannelsNames).

   This program wrAlpChNm.c is a hack, for proof of concept.

   This program is public domain.
   It may do nothing useful, or may cause harm.
   Use at your own peril.

   References:
     https://exiftool.org/TagNames/Photoshop.html
*/

#include <stdio.h>
#include <string.h>
#include <stdlib.h>

#define MaxLenNames 256

typedef struct {
  size_t nUsed;
  unsigned char Chars[MaxLenNames];
} NamesT;

static NamesT Names;
static int ChannelCount = 0;

static void AddName (const char * Name)
{
  size_t i;
  size_t Len = strlen (Name);
  if (Names.nUsed + Len >= MaxLenNames) {
    printf ("MaxLenNames is too small.\n");
    exit (1);
  }
  if (Len == 0 || Len > 255) {
    printf ("Each name must be less than 256 characters.\n");
    exit (1);
  }
  Names.Chars[Names.nUsed] = (unsigned char)Len;
  Names.nUsed++;
  for (i=0; i < Len; i++) {
    Names.Chars[Names.nUsed] = (unsigned char)Name[i];
    Names.nUsed++;
  }
  ChannelCount++;
}

static void Wr8bimAlphaChannelNames (void)
{
  size_t i;
  int NeedPadByte = (Names.nUsed % 2 == 1);
  fputs ("8BIM", stdout);
  fputc (0x03, stdout);
  fputc (0xEE, stdout);
  fputc (0x00, stdout);
  fputc (0x00, stdout);
  /* Write the length of the names as 4 bytes, MSB order.*/
  fputc (0x00, stdout);
  fputc (0x00, stdout);
  fputc ((int)(Names.nUsed / 256), stdout);
  fputc ((int)(Names.nUsed % 256), stdout);
  /* Write the names. */
  for (i=0; i < Names.nUsed; i++) {
    fputc (Names.Chars[i], stdout);
  }
  if (NeedPadByte) {
    fputc (0x00, stdout);
  }
}


static void Wr8bimDisplayInfo (void)
{
  int i;
  /* Each channel has a 14-byte structure:
     Bytes 0-1: Color space (2 bytes)
     Bytes 2-9: Color data (8 bytes)
     Byte 10-11: Opacity (0-100)
     Byte 12: Kind/Type (0=Selected Areas, 1=Masked Areas, 2=Spot Color)
  */
  size_t DataLen = ChannelCount * 13 + 4;
  int NeedPadByte = (DataLen % 2 == 1);
  
  fputs ("8BIM", stdout);
  fputc (0x04, stdout);  /* 0x0435 high byte */
  fputc (0x35, stdout);  /* 0x0435 low byte */
  fputc (0x00, stdout);
  fputc (0x00, stdout);
  
  /* Write the length of the data as 4 bytes, MSB order */
  fputc (0x00, stdout);
  fputc (0x00, stdout);
  fputc ((int)(DataLen / 256), stdout);
  fputc ((int)(DataLen % 256), stdout);

  // ?????????????
  fputc (0x00, stdout); // 0
  fputc (0x00, stdout); // 1
  fputc (0x00, stdout); // 2
  fputc (0x00, stdout); // 3
  
  /* Write 13 bytes for each channel */
  for (i = 0; i < ChannelCount; i++) {
    /* Bytes 0-3: Color space (0 = RGB) */

    
    /* Bytes 4-11: Color data (8 bytes, zeros for now) */

    // Color space
    fputc (0x00, stdout); // 0
    fputc (0x00, stdout); // 1

    // Color data
    // R
    fputc (0x00, stdout); // 2
    fputc (0xFF, stdout); // 3 - 255
    // G
    fputc (0x00, stdout); // 4
    fputc (0xFF, stdout); // 5 - 255
    // B
    fputc (0x00, stdout); // 6
    fputc (0xFF, stdout); // 7 - 255
    // A
    fputc (0x00, stdout); // 8
    fputc (0x00, stdout); // 9

    // Opacity
    fputc (0x00, stdout); // 10
    fputc (0x64, stdout); // 11 - 100%

    // Channel type
    fputc (0x02, stdout); // 12 - Spot Color
  }
  
  if (NeedPadByte) {
    fputc (0x00, stdout);
  }
}


int main (void)
{
  Names.nUsed = 0;

  AddName ("Branco");
  AddName ("Branco");
  Wr8bimAlphaChannelNames ();
  Wr8bimDisplayInfo ();

  return 0;
}

snibgo · 2025-12-05T21:08:49Z

snibgo
Dec 5, 2025

My mistake. The magick command I showed, and the output x.tiff, creates only 3 meta channels.

0 replies

snibgo · 2025-12-06T12:56:28Z

snibgo
Dec 6, 2025

I wrote:

Beware: the 8BIM profile is used for many purposes, and if it already exists, this process will entirely replace it with just the AlphaChannelsNames.

However, we can simply concatenate the AlphaChannelsNames 8BIM profile to an existing 8BIM profile. Suppose p.tiff contains a 8BIM profile. Extract it to p1.bin:

magick p.tiff 8bim:p1.bin

Make an AlphaChannelsNames 8BIM profile:

wrAlpChNm >p2.bin

Concatenate the two profiles (Windows command):

copy /B p1.bin+p2.bin p3.bin

The equivalent bash command is:

cat p1.bin p2.bin >p3.bin

Apply this concatenated profile:

magick p.tiff -profile p3.bin p2.tiff

What happens if p1.bin already contains a AlphaChannelsNames? Ideally, we would remove it, so the concatenated profile wouldn't contain AlphaChannelsNames twice. Perhaps Photoshop and other programs will ignore the first AlphaChannelsNames.

IM doesn't contain code to parse an 8BIM profile. But it could append AlphaChannelsNames to an existing profile.

This would all be simpler if exiftool could add or update AlphaChannelsNames. But it can't.

0 replies

snibgo · 2025-12-07T13:29:40Z

snibgo
Dec 7, 2025

As a test of my previous post, here is p4.zip which contains p4.tiff, which has RGB channels and one meta channel, and a large 8BIM profile. That profile contains a AlphaChannelsNames with value "AlphaMyMask", and a second AlphaChannelsNames with value "snibgo".

p4.zip

Those AlphaChannelsNames can be seen with:

magick p4.tiff 8BIMTEXT:

See the lines that begin "8BIM#1006=""

My hope is that Photoshop will overwrite the first AlphaChannelsNames with the second, so the alpha channel is named "snibgo".

1 reply

fmw42 Dec 7, 2025
Collaborator

snibgo, here is what my PS shows.

snibgo · 2025-12-07T18:39:55Z

snibgo
Dec 7, 2025

Oh, that's a shame. Photoshop is ignoring the second AlphaChannelsNames. (exiftool ignores the first.) So to do it properly, software needs to remove the first AlphaChannelsNames.

5 replies

fmw42 Dec 7, 2025
Collaborator

I don't know if this is worthwhile, but you could try adding two and see if the second is added. Perhaps you did that already?

arturo32 Dec 8, 2025
Author

In my case I have an image (flower_before.tiff) with no 8BIM profile, just an ICC one. It has a metachannel created by IM.

When I run ./magick identify -verbose flower_before.tiff an alpha AND meta channel are listed. This alpha is not visible on GIMP nor Photoshop, only the metachannel is.

When I run the ./magick flower_before.tiff -profile 8bim.bin flowe_after.tiff command with 1 AddName() call, nothing changes in Photoshop. When I associate a 8BIM profile generated with 2 AddName() calls, finally Photoshop associates the second name with the metachannel, showing the name "preto" (I added the name "branco" then "preto" in the C code).

This "hacky" behaviour is already very useful for me, so thank you very much!!

The zip bellow contains both flower_before.tiff and flowe_after.tiff files.

flower-alpha-test.zip

fmw42 Dec 8, 2025
Collaborator

Your before image has an alpha channel (alpha2), but your after shows only the meta (preto) for me in my PS. How did you create the meta channel in IM? What command line? Did you use -channel-fx to convert the alpha to a meta?

arturo32 Dec 9, 2025
Author

The "alpha 2" is already a metachannel, it just has a misleading name. This name is how PS shows the "meta0" name created by imagemagick.

arturo32 Dec 9, 2025
Author

I think I may have complicated things unnecessarily and went out of the scope of this discussion.
Here is what I understand:

The image flower.before.tiff does show its alpha channel in GIMP. Sorry for that;
Photoshop doesn't show "true alphas" in their channels tab by default. Even when opening the original PNG image that I used. It shows only metachannels (that confused me a little);
The C code from @snibgo try to rename any alpha/metachannel. So this explains why I had to call AddName two times to "reach" the metachannel;
The command that I use to create the metachannel is ./magick input.tiff \( +clone -colorspace LAB -channel R -separate \) -channel-fx "| gray=>meta0" output.tiff.

snibgo · 2025-12-09T00:16:29Z

snibgo
Dec 9, 2025

exiftool confirms that both files have one image with 5 channels, of which 3 are RGB.

"magick flower_before.tiff -verbose info:" says the two extra channels are alpha (unassociated) and meta0.

Gimp v3.0.2 says it has 5 channels: red, green, blue, alpha and "Tiff Channel".

This alpha is not visible on GIMP nor Photoshop, only the metachannel is.

Not so, for Gimp, for me. Gimp shows the alpha channel, as chequerboard in the image, and in the channel list.

0 replies

fmw42 · 2025-12-09T00:29:36Z

fmw42
Dec 9, 2025
Collaborator

For me PS only shows one extra channel for flower_before.tiff

0 replies

snibgo · 2025-12-09T13:55:24Z

snibgo
Dec 9, 2025

We can extract the 5 channels from flower_before.tiff and view them like this:

magick flower_before.tiff -channel RGBA,meta0 -separate -resize 600 +append +repage x.jpg

I resize and write to JPG to reduce network bandwidth.

I notice that in fmw42's screenshot, the alpha channel is shown as a chequerboard background, though it isn't listed as a channel. I don't know why it isn't listed.

0 replies

fmw42 · 2025-12-09T16:30:47Z

fmw42
Dec 9, 2025
Collaborator

Note that Photoshop has two kinds of alpha channels: background and extra channels. I suppose it depends upon what kind of alpha channel the OP created in his before image.

2 replies

arturo32 Dec 10, 2025
Author

Yes, I called the transparency/background alpha channel "true alpha". The flower image was a PNG with transparency and I converted it to a TIFF file, also with transparency. It is indeed strange that Photoshop doesn't show the background alpha in the channels section.

fmw42 Dec 10, 2025
Collaborator

What type of transparency did you assign when converting PNG to TIFF? TIFF has several types: associated, unassociated,unspecified. See tiff defines at https://imagemagick.org/script/defines.php. Did you use Imagemagick to convert from PNG to TIFF?

Uh oh!

feat: write meta channels in PSD files #8393

Uh oh!

ImageMagick version

Operating system, version and so on

Description

Replies: 17 comments · 23 replies

Uh oh!

Uh oh!

arturo32 Oct 9, 2025 Author

Uh oh!

arturo32 Oct 9, 2025 Author

Uh oh!

Uh oh!

arturo32 Oct 9, 2025 Author

Uh oh!

Uh oh!

arturo32 Oct 9, 2025 Author

Uh oh!

arturo32 Nov 10, 2025 Author

Uh oh!

dlemstra Nov 10, 2025 Maintainer

Uh oh!

arturo32 Nov 11, 2025 Author

Uh oh!

arturo32 Dec 3, 2025 Author

Uh oh!

fmw42 Dec 3, 2025 Collaborator

Uh oh!

arturo32 Dec 4, 2025 Author

Uh oh!

fmw42 Dec 4, 2025 Collaborator

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fmw42 Dec 5, 2025 Collaborator

Uh oh!

Uh oh!

Uh oh!

fmw42 Dec 5, 2025 Collaborator

Uh oh!

fmw42 Dec 5, 2025 Collaborator

Uh oh!

Uh oh!

fmw42 Dec 5, 2025 Collaborator

Uh oh!

Uh oh!

Uh oh!

fmw42 Dec 5, 2025 Collaborator

Uh oh!

Uh oh!

arturo32 Feb 13, 2026 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fmw42 Dec 7, 2025 Collaborator

Uh oh!

Replies: 17 comments 23 replies

arturo32 Oct 9, 2025
Author

arturo32 Oct 9, 2025
Author

arturo32
Oct 9, 2025
Author

arturo32
Oct 9, 2025
Author

arturo32
Nov 10, 2025
Author

dlemstra
Nov 10, 2025
Maintainer

arturo32 Nov 11, 2025
Author

arturo32 Dec 3, 2025
Author

fmw42 Dec 3, 2025
Collaborator

arturo32 Dec 4, 2025
Author

fmw42 Dec 4, 2025
Collaborator

fmw42 Dec 5, 2025
Collaborator

fmw42 Dec 5, 2025
Collaborator

fmw42
Dec 5, 2025
Collaborator

fmw42 Dec 5, 2025
Collaborator

fmw42 Dec 5, 2025
Collaborator

arturo32 Feb 13, 2026
Author

fmw42 Dec 7, 2025
Collaborator